Short answer: Drop the "Etsy → Create 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 |
|---|---|---|---|
Receipt ID receipt_id | string | Required | The Receipt ID assigned by Etsy. Find via the corresponding list/search operation in this app. Use the exact ID, not a name or label. |
Tracking Code tracking_code | string | Required | — |
Carrier Name carrier_name | string | Required | USPS, UPS, FedEx |
Send BCC to seller send_bcc | options | Optional | — |
{"receipt_id": "{{trigger.receipt_id}}","tracking_code": "{{trigger.tracking_code}}","carrier_name": "USPS, UPS, FedEx","send_bcc": "{{trigger.send_bcc}}"}
{"receipt_id": 789,"was_shipped": true}
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.