Create Product: BigCommerce action

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
Product Name name	string	Required	—
Type type	options	Optional	—
Weight (required for physical) weight	string	Optional	—
Price price	string	Required	—
Category IDs categories	array	Optional	—
Description description	string	Optional	—
SKU sku	string	Optional	—

Sample request

{
  "name": "{{trigger.name}}",
  "type": "{{trigger.type}}",
  "weight": "{{trigger.weight}}",
  "price": "{{trigger.price}}",
  "categories": "{{trigger.categories}}"
}

Returns

{
  "data": {
    "id": 123,
    "sku": "TEE-1",
    "name": "Tee",
    "price": 19.99
  }
}

Use these fields in downstream nodes for routing, logging, or error handling.

FAQ

Questions about Create Product.

What does the Create Product action do in BigCommerce?

Creates a new product with name, SKU, price, description, categories, weight, dimensions. For high-volume catalog management, prefer the batch endpoint via HTTP action. Optional variants array for products with size/colour options.

What inputs does Create Product require?

Required: Product Name, Price. Every input accepts a static value or a variable from any upstream node in your workflow.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if BigCommerce returns an error?

The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does Create Product support batch operations?

Yes. Run Create Product inside a Loop node to process arrays. Tiny Command handles BigCommerce's rate limits automatically so you don't have to throttle manually.

More actions