Short answer: Drop the "Square → Create Square Invoice" 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 |
|---|---|---|---|
Location ID location_id | string | Required | The Location ID assigned by Square. Find via the corresponding list/search operation in this app. Use the exact ID, not a name or label. |
Order ID order_id | string | Required | The Order ID assigned by Square. Find via the corresponding list/search operation in this app. Use the exact ID, not a name or label. |
Customer ID primary_recipient_customer_id | string | Required | — |
Title title | string | Optional | May 2026 Subscription |
Delivery delivery_method | options | Optional | — |
{"location_id": "{{trigger.location_id}}","order_id": "{{trigger.order_id}}","primary_recipient_customer_id": "{{trigger.primary_recipient_customer_id}}","title": "May 2026 Subscription","delivery_method": "{{trigger.delivery_method}}"}
{"invoice": {"id": "inv_abc","status": "DRAFT","public_url": "","invoice_number": "1"}}
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.