Short answer: Drop the "BigCommerce → Update Product" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Product ID product_id | string | Required | The Product ID assigned by Bigcommerce. Find via the corresponding list/search operation in this app. Use the exact ID, not a name or label. |
Name name | string | Optional | — |
Price price | string | Optional | — |
Inventory Level inventory_level | string | Optional | — |
Description description | string | Optional | — |
{"product_id": "{{trigger.product_id}}","name": "{{trigger.name}}","price": "{{trigger.price}}","inventory_level": "{{trigger.inventory_level}}","description": "{{trigger.description}}"}
{"data": {"id": 123,"name": "Tee","price": 19.99}}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.