Ecwid

undefined

Detail	Value
Category	E-commerce
Base URL	https://app.ecwid.com/api/v3/{store_id}
Authentication	Bearer Token
Endpoints	5
Connector key	ecwid

Using Ecwid in a workflow

1. Go to Connections and click New Connection.
2. Pick Ecwid from the marketplace.
3. Enter your credentials (see Authentication above for what's expected).
4. In a workflow, drop an API Call node and select this connection.
5. Pick the operation you need from the Operation dropdown. The full list is below.

Available endpoints

Endpoint	Summary
GET	Products
GET	Orders
GET	Customers
GET	Categories
GET	Coupons

Each endpoint is documented in full below. Use the outline on the right to jump to one.

GET

Products

Detail	Value
Operation ID	products_0
Method	GET
Path	``

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Ecwid connection from the Connection dropdown.
3. In the Operation dropdown, select products_0.
4. 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 Ecwid API reference.

GET

Orders

Detail	Value
Operation ID	orders_1
Method	GET
Path	``

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Ecwid connection from the Connection dropdown.
3. In the Operation dropdown, select orders_1.
4. 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 Ecwid API reference.

GET

Customers

Detail	Value
Operation ID	customers_2
Method	GET
Path	``

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Ecwid connection from the Connection dropdown.
3. In the Operation dropdown, select customers_2.
4. 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 Ecwid API reference.

GET

Categories

Detail	Value
Operation ID	categories_3
Method	GET
Path	``

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Ecwid connection from the Connection dropdown.
3. In the Operation dropdown, select categories_3.
4. 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 Ecwid API reference.

GET

Coupons

Detail	Value
Operation ID	coupons_4
Method	GET
Path	``

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Ecwid connection from the Connection dropdown.
3. In the Operation dropdown, select coupons_4.
4. 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 Ecwid API reference.