Short answer: Drop the "Shopify → Update 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. |
Note note | string | Optional | Internal note about the order |
Tags tags | string | Optional | Comma-separated tags (replaces existing) |
Email email | string | Optional | Update the contact email for the order |
{"order_id": "e.g. 789012345","note": "{{trigger.note}}","tags": "e.g. VIP, rush","email": "customer@example.com"}
{"order": {"id": 789,"note": "Rush shipping requested","tags": "VIP, rush","email": "customer@example.com","order_number": 1001}}
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.