List Products: 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
Limit limit	string	Optional	—
Page page	string	Optional	—

Sample request

{
  "limit": "{{trigger.limit}}",
  "page": "{{trigger.page}}"
}

Returns

{
  "data": [
    {
      "id": 123,
      "sku": "TEE-1",
      "name": "Tee",
      "price": 19.99
    }
  ],
  "meta": {
    "pagination": {
      "total": 1
    }
  }
}

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

FAQ

Questions about List Products.

What does the List Products action do in BigCommerce?

Paginated products with filters by category, brand, visibility, recently-modified time. For full-catalog syncs to a search index or external storefront, use the recently-modified filter to incrementally pull only changed products.

What inputs does List Products require?

List Products 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 Products support batch operations?

Yes. Run List Products 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