Short answer: Drop the "PayPal → PayPal 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 |
|---|---|---|---|
Amount amount | number | Required | Amount. e.g. "99.99" |
Currency currency | options | Required | Currency. Options: USD, EUR, GBP, CAD, AUD |
Description description | string | Optional | Description. e.g. "Payment for order #123" |
Return URL returnUrl | url | Required | Return URL. e.g. "https://example.com/success" |
Cancel URL cancelUrl | url | Required | Cancel URL. e.g. "https://example.com/cancel" |
{"amount": "99.99","currency": "{{trigger.currency}}","description": "Payment for order #123","returnUrl": "https://example.com/success","cancelUrl": "https://example.com/cancel"}
{"id": "ORDER-123","links": [{"rel": "approve","href": "https://www.paypal.com/checkoutnow?token=ORDER-123"}],"status": "CREATED"}
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.