Short answer: Drop the "Square → Square Create Payment" 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 |
|---|---|---|---|
Source ID (nonce or saved card) source_id | string | Required | — |
Amount (cents) amount | string | Required | 1000 = $10.00 |
Currency currency | string | Optional | — |
Idempotency Key idempotency_key | string | Required | A unique string per request to prevent double charges |
Customer ID customer_id | string | Optional | The Customer ID assigned by Square. Find via the corresponding list/search operation in this app. Use the exact ID, not a name or label. |
Note note | string | Optional | — |
{"source_id": "{{trigger.source_id}}","amount": "1000 = $10.00","currency": "{{trigger.currency}}","idempotency_key": "{{trigger.idempotency_key}}","customer_id": "{{trigger.customer_id}}"}
{"payment": {"id": "pay_abc","status": "COMPLETED","receipt_url": "https://x.com","amount_money": {"amount": 1000}}}
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.