Short answer: Drop the "Shopify → Cancel Order" 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 |
|---|---|---|---|
Order ID order_id | string | Required | Shopify order ID — numeric. Find via List Orders. Not the order name like #1001. |
Reason reason | options | Optional | Reason. Options: Customer changed/cancelled order, Fraudulent order, Items unavailable, Other |
Notify Customer email | options | Optional | Send a cancellation email to the customer |
{"order_id": "e.g. 789012345","reason": "{{trigger.reason}}","email": "{{trigger.email}}"}
{"order": {"id": 789,"cancelled_at": "2025-03-15T10:30:00-04:00","order_number": 1001,"cancel_reason": "customer","financial_status": "refunded"}}
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.