Short answer: Drop the "Stripe → Create Refund" 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 |
|---|---|---|---|
Charge ID charge | string | Optional | The charge ID to refund (e.g. ch_xxx). Provide this or Payment Intent ID. |
Payment Intent ID payment_intent | string | Optional | The payment intent to refund (e.g. pi_xxx). Provide this or Charge ID. |
Amount (cents) amount | string | Optional | Amount in the currency's smallest unit (cents for USD/EUR, no decimals). |
Reason reason | options | Optional | Reason for the refund (shown to the customer) |
{"charge": "ch_1234567890","payment_intent": "pi_1234567890","amount": "e.g. 500 for $5.00","reason": "{{trigger.reason}}"}
{"id": "re_abc123","amount": 500,"charge": "ch_1234567890","object": "refund","status": "succeeded","created": 1700000000,"currency": "usd"}
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.