Apps › Payments

Razorpay automation with Bizomate

Every Razorpay payment sets off work: a receipt, a row in the accounts sheet, a message when one fails. Bizomate starts that work the moment Razorpay reports the payment, and makes payment links, orders, invoices and customers for you. Steps that move money are marked, and every run leaves a record you can read.

Start free

On every plan, Free included.

At a glance

Label	Value
Plans	Every plan
Connect	Key ID and key secret
Starts runs	Instantly
Kind	Connected app · Payments

What can start a workflow

Payment captured
When a payment is captured into your account

Razorpay sends events only to addresses set in its Dashboard, so you paste the trigger's webhook address and secret into Account & Settings › Webhooks once, in the same mode as the key, and tick the event. Bizomate checks every event against the secret.

Payment failed
When a customer's payment fails

Payment link paid
When a payment link is paid in full

Order paid
When an order is paid

Refund processed
When a refund reaches the customer

Subscription charged
When a subscription's payment is taken

What a workflow can do with it

Create a payment link
A link the customer pays by — UPI, card or netbanking

A link the customer pays by UPI, card or netbanking. Razorpay can text or email it, and a Reference of your own is refused if used twice.

Create an order
An order for Razorpay Checkout to take payment against

Fetch a payment
A payment's status, amount and method

Capture a payment
Takes an authorised payment into your account

Moves money: takes an authorised payment, for its full amount, into your account.

Refund a payment
Sends money back for a payment — all of it, or part

Moves money: all of a payment, or part. A retry of the step sends the same idempotency key, so the customer is refunded once.

Create a customer
A customer in Razorpay, or the one already there with that email or phone

Or gives back the one already there with that email or phone.

Create an invoice
An invoice with line items, sent to the customer to pay

Cancel a payment link
Stops a payment link from taking payment

How you connect it

Paste the Key ID and Key secret of a Razorpay API key from the Razorpay Dashboard, under Account & Settings › API Keys. A test key (rzp_test_) never moves real money, and a connection with one shows a Test mode pill wherever it is used. Before a test run with a live key in a step that moves money, Bizomate asks first. Bizomate tests the key before saving it, and Test answers "Reached Razorpay · test mode" or "Reached Razorpay · live". Razorpay charges its own fees on each payment.

The secret is encrypted before it is saved, used only when a step runs or a test calls Razorpay, and never shown again — not to you, your colleagues or Bizomate support. It belongs to one workspace, the Code step cannot read it, and revoking the connection wipes it at once.

In the help centre: Connect Razorpay, Create a Razorpay payment link or order, Start a workflow from Razorpay payment events, Refund a Razorpay payment and Steps that move money.

Questions about Razorpay

Why do I paste a webhook into Razorpay myself?

Razorpay sends events only to addresses set in its own Dashboard. The trigger shows its address and a secret once; paste both into Account & Settings › Webhooks, tick the event, and Bizomate checks every event against the secret.

Can I build with a test key and go live later?

Yes. A rzp_test_ key only ever moves test money. Most people keep two connections, one test and one live, and switch the steps to the live one before publishing. Test and live mode each need their own webhook in Razorpay.

Can a refund be paid twice by mistake?

A retry of the same step sends the same idempotency key, so Razorpay refunds once. Run again, Test run and Run this step start a new run with a new key, which is why a test run with a live key asks first.