Appearance
WooCommerce
Manage products, orders, and customers on WooCommerce stores.
| Detail | Value |
|---|---|
| Category | E-commerce |
| Base URL | https://{store_url}/wp-json/wc/v3 |
| Authentication | Bearer Token |
| Endpoints | 6 |
| Connector key | woocommerce |
Using WooCommerce in a workflow
- Go to Connections and click New Connection.
- Pick WooCommerce from the marketplace.
- Enter your credentials (see Authentication above for what's expected).
- In a workflow, drop an API Call node and select this connection.
- Pick the operation you need from the Operation dropdown — the full list is below.
Available endpoints
| Endpoint | Summary |
|---|---|
GET /products | List products |
POST /products | Create a product |
GET /products/{id} | Get a product |
GET /orders | List orders |
GET /orders/{id} | Get an order |
GET /customers | List customers |
Each endpoint is documented in full below. Use the outline on the right to jump to one.
GET /products
List products
| Detail | Value |
|---|---|
| Operation ID | ecommerce.listProducts |
| Method | GET |
| Path | /products |
Parameters
| Name | Location | Type | Required |
|---|---|---|---|
per_page | query | integer | No |
page | query | integer | No |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your WooCommerce connection from the Connection dropdown.
- In the Operation dropdown, select
ecommerce.listProducts. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream WooCommerce API reference.
POST /products
Create a product
| Detail | Value |
|---|---|
| Operation ID | ecommerce.createProduct |
| Method | POST |
| Path | /products |
Parameters
No parameters.
Request Body
| Field | Type |
|---|---|
name | string |
regular_price | string |
type | string |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your WooCommerce connection from the Connection dropdown.
- In the Operation dropdown, select
ecommerce.createProduct. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
Required fields are marked — fill them or the call will fail at runtime.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream WooCommerce API reference.
GET /products/{id}
Get a product
| Detail | Value |
|---|---|
| Operation ID | ecommerce.getProduct |
| Method | GET |
| Path | /products/{id} |
Parameters
| Name | Location | Type | Required |
|---|---|---|---|
id | path | string | Yes |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your WooCommerce connection from the Connection dropdown.
- In the Operation dropdown, select
ecommerce.getProduct. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
Required fields are marked — fill them or the call will fail at runtime.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream WooCommerce API reference.
GET /orders
List orders
| Detail | Value |
|---|---|
| Operation ID | ecommerce.listOrders |
| Method | GET |
| Path | /orders |
Parameters
| Name | Location | Type | Required |
|---|---|---|---|
per_page | query | integer | No |
status | query | string | No |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your WooCommerce connection from the Connection dropdown.
- In the Operation dropdown, select
ecommerce.listOrders. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream WooCommerce API reference.
GET /orders/{id}
Get an order
| Detail | Value |
|---|---|
| Operation ID | ecommerce.getOrder |
| Method | GET |
| Path | /orders/{id} |
Parameters
| Name | Location | Type | Required |
|---|---|---|---|
id | path | string | Yes |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your WooCommerce connection from the Connection dropdown.
- In the Operation dropdown, select
ecommerce.getOrder. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
Required fields are marked — fill them or the call will fail at runtime.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream WooCommerce API reference.
GET /customers
List customers
| Detail | Value |
|---|---|
| Operation ID | ecommerce.listCustomers |
| Method | GET |
| Path | /customers |
Parameters
| Name | Location | Type | Required |
|---|---|---|---|
per_page | query | integer | No |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your WooCommerce connection from the Connection dropdown.
- In the Operation dropdown, select
ecommerce.listCustomers. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream WooCommerce API reference.