Count Orders: Shopify 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
Status status	options	Optional	Status. Options: Any, Open, Closed, Cancelled
Financial Status financial_status	options	Optional	Financial Status. Options: Any, Paid, Pending, Refunded
Created After created_at_min	string	Optional	ISO 8601 date
Created Before created_at_max	string	Optional	ISO 8601 date

Sample request

{
  "status": "{{trigger.status}}",
  "financial_status": "{{trigger.financial_status}}",
  "created_at_min": "e.g. 2025-01-01T00:00:00Z",
  "created_at_max": "e.g. 2025-12-31T23:59:59Z"
}

Returns

{
  "count": 247
}

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

FAQ

Questions about Count Orders.

What does the Count Orders action do in Shopify?

Returns a count of orders matching the specified filters (status, fulfillment_status, financial_status, date range). Used for dashboards without fetching every record.

What inputs does Count Orders require?

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

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

More actions