List Orders: 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	—
Status ID filter status_id	string	Optional	11=Awaiting Fulfillment, 2=Shipped, 5=Cancelled
Min Date Created min_date_created	string	Optional	Tue, 01 May 2026 00:00:00 GMT

Sample request

{
  "limit": "{{trigger.limit}}",
  "status_id": "{{trigger.status_id}}",
  "min_date_created": "Tue, 01 May 2026 00:00:00 GMT"
}

Returns

[
  {
    "id": 100,
    "status": "Shipped",
    "customer_id": 42,
    "total_inc_tax": "29.99"
  }
]

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

FAQ

Questions about List Orders.

What does the List Orders action do in BigCommerce?

Paginated orders with filters by status, customer, date range, total. The base query for "this morning, list yesterday's orders" daily-summary digests and for backfill workflows that catch orders missed during webhook downtime.

What inputs does List Orders require?

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

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