ActionBigCommerceUpdated September 2026

How do I add a product to BigCommerce?

Short answer: You can create product in BigCommerce by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the BigCommerce Create Product action to a workflow, map its 7 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

Create Product in BigCommerce — start free All 10 BigCommerce actions

Create Product in BigCommerce — start free

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.

Triggered by

Apps that pair well as the trigger for Create Product.

Any of these apps can fire this action as part of a workflow.

Google Sheets → BigCommerce

2 Google Sheets triggers

HubSpot → BigCommerce

18 HubSpot triggers

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 run history shows the failed step with its input and the error message BigCommerce returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.

Does Create Product support batch operations?

Run Create Product inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within BigCommerce's rate limits.

More actions