Short answer: Drop the "Shopify → List Orders" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
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, Partially refunded |
Limit limit | string | Optional | Limit. e.g. "50" |
Created After created_at_min | string | Optional | ISO 8601 date to filter orders created after this time |
{"status": "{{trigger.status}}","financial_status": "{{trigger.financial_status}}","limit": "50","created_at_min": "e.g. 2025-01-01T00:00:00Z"}
{"orders": [{"id": 789,"email": "customer@example.com","total_price": "59.98","order_number": 1001,"financial_status": "paid","fulfillment_status": null}]}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.