Appearance
Adobe Commerce (Magento)
undefined
| Detail | Value |
|---|---|
| Category | E-commerce |
| Base URL | https://{store}.magento.cloud/rest/V1 |
| Authentication | Bearer Token |
| Endpoints | 7 |
| Connector key | magento |
Using Adobe Commerce (Magento) in a workflow
- Go to Connections and click New Connection.
- Pick Adobe Commerce (Magento) 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 |
GET | Orders |
GET | Customers |
GET | Inventory |
GET | Categories |
GET | Invoices |
GET | Cart |
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
- Add an API Call node to your workflow.
- Pick your Adobe Commerce (Magento) connection from the Connection dropdown.
- In the Operation dropdown, select
products_0. - 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 Adobe Commerce (Magento) API reference.
GET
Orders
| Detail | Value |
|---|---|
| Operation ID | orders_1 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Adobe Commerce (Magento) connection from the Connection dropdown.
- In the Operation dropdown, select
orders_1. - 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 Adobe Commerce (Magento) API reference.
GET
Customers
| Detail | Value |
|---|---|
| Operation ID | customers_2 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Adobe Commerce (Magento) connection from the Connection dropdown.
- In the Operation dropdown, select
customers_2. - 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 Adobe Commerce (Magento) API reference.
GET
Inventory
| Detail | Value |
|---|---|
| Operation ID | inventory_3 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Adobe Commerce (Magento) connection from the Connection dropdown.
- In the Operation dropdown, select
inventory_3. - 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 Adobe Commerce (Magento) API reference.
GET
Categories
| Detail | Value |
|---|---|
| Operation ID | categories_4 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Adobe Commerce (Magento) connection from the Connection dropdown.
- In the Operation dropdown, select
categories_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 Adobe Commerce (Magento) API reference.
GET
Invoices
| Detail | Value |
|---|---|
| Operation ID | invoices_5 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Adobe Commerce (Magento) connection from the Connection dropdown.
- In the Operation dropdown, select
invoices_5. - 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 Adobe Commerce (Magento) API reference.
GET
Cart
| Detail | Value |
|---|---|
| Operation ID | cart_6 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Adobe Commerce (Magento) connection from the Connection dropdown.
- In the Operation dropdown, select
cart_6. - 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 Adobe Commerce (Magento) API reference.