ActionShopifyUpdated September 2026

How do I count Shopify orders matching a filter?

Short answer: You can count orders in Shopify by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Shopify Count Orders action to a workflow, map its 4 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

Count Orders in Shopify — start free All 16 Shopify actions

Count Orders in Shopify — 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
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.

Triggered by

Apps that pair well as the trigger for Count Orders.

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

Google Sheets → Shopify

2 Google Sheets triggers

HubSpot → Shopify

18 HubSpot triggers

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 run history shows the failed step with its input and the error message Shopify 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 Count Orders support batch operations?

Run Count Orders 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 Shopify's rate limits.

More actions