Short answer: Drop the "RazorPay → Create RazorPay Payment Link" 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 (in paise) amount | string | Required | Amount in paise (e.g. 50000 = INR 500.00) |
Currency currency | string | Optional | Currency code (default: INR) |
Description description | string | Optional | Description of the payment link |
{"amount": "50000","currency": "INR","description": "Payment for Order #123"}
{"id": "plink_abc123def456","amount": 50000,"status": "created","currency": "INR","short_url": "https://rzp.io/i/abc123","created_at": 1714000000,"description": "Payment for Order #123"}
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.