Short answer: Drop the "Square → Refund Square 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 |
|---|---|---|---|
Payment ID payment_id | string | Required | The Payment ID assigned by Square. Find via the corresponding list/search operation in this app. Use the exact ID, not a name or label. |
Amount to refund (cents) amount | string | Required | — |
Currency currency | string | Optional | — |
Idempotency Key idempotency_key | string | Required | — |
Reason reason | string | Optional | — |
{"payment_id": "{{trigger.payment_id}}","amount": "{{trigger.amount}}","currency": "{{trigger.currency}}","idempotency_key": "{{trigger.idempotency_key}}","reason": "{{trigger.reason}}"}
{"refund": {"id": "ref_abc","status": "PENDING","payment_id": "pay_abc","amount_money": {"amount": 500}}}
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.