Short answer: Drop the "Magento → Create Magento Shipment" 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 | The Order ID assigned by Magento. Find via the corresponding list/search operation in this app. Use the exact ID, not a name or label. |
Tracking Number track_number | string | Optional | — |
Carrier Code carrier_code | string | Optional | ups, fedex, usps |
Carrier Title title | string | Optional | United Parcel Service |
{"order_id": "{{trigger.order_id}}","track_number": "{{trigger.track_number}}","carrier_code": "ups, fedex, usps","title": "United Parcel Service"}
12345
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.