Skip to content
ActionBigCommerceUpdated May 2026

What categories exist in BigCommerce?

Short answer: Drop the "BigCommerceList Categories" action anywhere in your workflow, map the inputs from upstream nodes, and publish.

Inputs

The fields this action accepts.

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

FieldTypeRequiredDescription
Limit
limit
stringOptional
Sample request
{
"limit": "{{trigger.limit}}"
}
Returns
{
"data": [
{
"id": 1,
"name": "Apparel"
}
]
}

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

Triggered by

Apps that pair well as the trigger for List Categories.

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

FAQ

Questions about List Categories.

What does the List Categories action do in BigCommerce?
Returns the category tree — each category's name, parent, child count, visibility. Useful for resolving category IDs in product-create workflows or for "audit which categories have stale activity" maintenance.
What inputs does List Categories require?
List Categories has no required inputs. Sensible defaults are applied if you leave fields blank.
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 List Categories support batch operations?
Yes. Run List Categories 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

Other BigCommerce actions.

Send list categories from your workflows.

Triggered by anything in the catalog. Free tier available. No credit card.