Short answer: Drop the "PayPal → PayPal 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 |
|---|---|---|---|
Capture ID captureId | string | Required | Capture ID |
Refund Amount amount | number | Optional | Leave empty for full refund |
Currency currency | string | Optional | Currency |
Reason / Note note | string | Optional | Reason / Note. e.g. "Customer requested refund" |
{"captureId": "{{trigger.captureId}}","amount": "{{trigger.amount}}","currency": "{{trigger.currency}}","note": "Customer requested refund"}
{"id": "REF-123","amount": {"value": "99.99","currency_code": "USD"},"status": "COMPLETED"}
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.