Resources · Make integration

Razorpay Make integrationAutomate Razorpay with Make.

Every paid invoice or failed payment in Razorpay can start an automation. The Razorpay Make integration gives you 7 instant triggers and 1 action. This guide shows how to link your account and build your first scenario.

Try the Razorpay integration on MakeSee the 8 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Razorpay Make integration do?

The Razorpay Make integration lets Razorpay tell Make the moment money moves: an invoice paid in full or in part, a payment captured or failed, a payment link or payment page paid. Make then runs a scenario, the automation you build in Make, a chain of bricks called modules that pass the data along.

Reconcile paid invoices. Watch Invoice Paid starts the scenario when an invoice is settled in full, so your accounting sheet or your CRM gets the update without anyone copying numbers. Pair it with Watch Invoice Partially Paid if your clients often pay in installments.

Chase failed payments while the customer still cares. Watch Payment Failed hands you each failed attempt, which you can route to your support tool or to a follow-up email. The customer hears from you while the purchase is still on their mind.

Follow link and page sales. Watch Payment Link Paid and Watch Payment Page Paid cover the sales you collect outside a classic checkout, handy for freelancers and small shops.

What Make does not give you here: ready-made modules to create invoices, refunds or links. There is only one action, Make an API Call, which reaches any endpoint of the Razorpay API with the same connection. Make's own doc page for Razorpay is also flagged as AI-generated, so check important details against Razorpay's documentation. The same app often has an n8n node too; the n8n vs Make comparison lays out both tools. New to the editor? The Make training starts from zero, and the Make pricing page explains how operations are counted.

Connect

How do you connect Razorpay to Make?

  1. 01

    Add a Razorpay module

    You need an active Razorpay account with API keys generated. In your scenario, add a Razorpay module and click Create a connection. A connection is your Razorpay account linked to Make once, then reused by every Razorpay module.

  2. 02

    Name the connection

    The Connection name field is optional, but a clear name saves you trouble later, especially once you manage more than one Razorpay account in Make. The business name is usually enough.

  3. 03

    Paste your credentials

    Enter the credentials you copied from your Razorpay account, or follow the instructions on screen. For OAuth, create an application in the Razorpay Partner Dashboard, use https://www.integromat.com/oauth/cb/razorpay3 as the callback URI, then copy the Client ID and Client secret.

First scenario

Your first Razorpay scenario in Make

GoalWhen a payment fails in Razorpay, Make receives it and calls the Razorpay API endpoint you pick, with the same connection.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the big + to place the first module. Search for Razorpay by name.

  2. 02

    Pick Watch Payment Failed

    Choose Watch Payment Failed, click Create a webhook, then Create a connection and link your Razorpay account as described above.

  3. 03

    Add Make an API Call

    Click the + to the right of the trigger and add Razorpay's Make an API Call. Point it at the endpoint you need from Razorpay's API docs and map values from the failed payment.

  4. 04

    Test with Run once

    Click Run once, then let a payment fail on the Razorpay side. Each module shows the bundles it received, so you can check what the trigger actually sends before going further.

  5. 05

    Switch it on

    Happy with the test? Save and switch the scenario on. Being instant, it now reacts each time Razorpay reports a failed payment, with no polling interval to wait for.

Triggers

Razorpay triggers in Make

7 modules start a scenario when something happens in Razorpay. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Razorpay as soon as it happens.

Razorpay1Watch Invoice Paid

Watch Invoice Paid

Instant trigger

In Make“Triggers when an invoice is fully paid.”

Starts your scenario the moment a Razorpay invoice is settled in full, so the rest of your stack learns it without anyone checking the dashboard. Each paid invoice arrives as one bundle, one item flowing to the next module.

How it fires
instant, Razorpay calls Make through a webhook as soon as the invoice is paid.
When to use it
to mark a deal as won in your CRM or unlock a service once the client has paid everything.
Watch out
a partial payment does not fire this trigger; that event belongs to Watch Invoice Partially Paid.
Razorpay2Watch Invoice Partially Paid

Watch Invoice Partially Paid

Instant trigger

In Make“Triggers when a partial payment is made against an invoice.”

Catches each installment paid against an invoice that is not yet closed, which gives you a clean trail of partial amounts instead of a single final event.

How it fires
instant, Razorpay notifies Make through a webhook as soon as the partial payment lands.
When to use it
for clients who pay a deposit first, when your team wants to see progress on the invoice or send a thank-you with the remaining balance.
Watch out
one invoice can fire this trigger several times, so plan the next modules to update a record rather than create a new one each time.
Razorpay3Watch Payment Captured

Watch Payment Captured

Instant trigger

In Make“Triggers when a new payment is successfully captured.”

Hands Make every new payment Razorpay captures successfully, the broadest signal that money actually came in, whatever the source.

How it fires
instant, the app warns Make through a webhook once the capture succeeds.
When to use it
to log every sale in a spreadsheet, send an order to fulfilment or post a message in your team chat.
Watch out
since it covers all captured payments, it can overlap with the invoice, link and page triggers; pick one family per scenario to avoid handling the same sale twice and spending extra operations, the executions Make counts on your plan.
Razorpay4Watch Payment Failed

Watch Payment Failed

Instant trigger

In Make“Triggers when a new payment fails.”

Brings each failed payment into Make, which turns a silent loss into something your team can act on while the buyer is still around.

How it fires
instant, Razorpay pings Make through a webhook as soon as the payment fails.
When to use it
to open a support ticket, alert the account manager or send the customer a polite nudge with another way to pay.
Watch out
a buyer may retry and succeed a moment later, so check for a captured payment before sending a reminder that feels awkward.
Razorpay5Watch Payment Link Paid

Watch Payment Link Paid

Instant trigger

In Make“Triggers when a Payment Link is paid.”

Tells Make when someone pays one of your Razorpay Payment Links, useful for sales you close by chat, email or social media rather than through a store.

How it fires
instant, Razorpay sends the event to Make through a webhook right after the link is paid.
When to use it
a consultant who sends links after each call can create the client folder or the booking automatically once the money arrives.
Watch out
links paid in several parts have their own trigger, Watch Payment Link Partially Paid, so choose the one that matches how you bill.
Razorpay6Watch Payment Link Partially Paid

Watch Payment Link Partially Paid

Instant trigger

In Make“Triggers when a partial payment is made on a Standard Payment Link.”

Follows partial payments made on a Standard Payment Link, so you can track what is left to collect without opening Razorpay.

How it fires
instant, Razorpay calls Make through a webhook each time a partial payment comes in.
When to use it
for training fees or large orders split into several transfers, when the customer should receive a receipt after each one.
Watch out
the trigger is described for Standard Payment Links only; if you use another link type, test with Run once before relying on it.
Razorpay7Watch Payment Page Paid

Watch Payment Page Paid

Instant trigger

In Make“Triggers when a payment page is paid.”

Fires when a buyer completes a payment on one of your Razorpay payment pages, the hosted pages you share for donations, events or simple product sales.

How it fires
instant, the app alerts Make through a webhook as soon as the page payment is done.
When to use it
an event organizer can add each buyer to the guest list or a mailing list the moment they pay.
Watch out
payments made through links or invoices do not go through this trigger, so a scenario built on it only sees page sales.
Modules

What the Razorpay app can do in Make

Razorpay gives you 1 module. For each one: what it does for you, when to reach for it, and what to watch out for.

Razorpay1

Make an API Call

Action

In Make“Performs an arbitrary authorized API call”

Opens the whole Razorpay API from your scenario, using the connection you already set up, so any request the listed triggers do not cover stays within reach.

When to use it
it is the only Razorpay action in Make, so you pick it whenever the scenario must write to or read from Razorpay after a trigger fires.
Watch out
you choose the endpoint and the fields yourself from Razorpay's API documentation, so test each call with Run once first.
Need help

Need help automating Razorpay with Make?

A person reads every message.

FAQ

Razorpay and Make: common questions

01Is the Razorpay Make integration free?
Yes, on the Make side. Razorpay is a standard app, available from the Free plan. That plan allows 2 active scenarios, 15 minutes minimum between scheduled runs, 5 minutes per execution and files up to 5 MB. Paid plans (Core, Pro, Teams, Enterprise) lower the interval to 1 minute and count usage in operations per month. Razorpay itself has its own pricing, which you check on the Razorpay side; this page gives no figure for it.
02What do you need to connect Razorpay to Make?
An active Razorpay account and API keys generated in it. In Make, add a Razorpay module, click Create a connection, optionally name it, then paste the credentials you copied from Razorpay or follow the on-screen instructions. For an instant module, click Create a webhook first. If you go the OAuth route, create an application in the Razorpay Partner Dashboard and copy its Client ID and Client secret into Make. Once saved, the same connection serves every Razorpay module you add later.
03Do Razorpay triggers in Make fire in real time?
Yes. All 7 Razorpay triggers are instant: Razorpay calls Make through a webhook as soon as the event happens, whether an invoice is paid, a payment is captured or fails, or a link or page is paid. Make does not have to poll Razorpay on the scenario's schedule, which is what a scheduled trigger does. You still need to switch the scenario on for the webhook to be heard. Each event then reaches the next module as one bundle.
04What if a Razorpay module is missing in Make?
Use Make an API Call. It is the only action in the Razorpay app, and it can call any endpoint of the Razorpay API with the connection you already have. You build the request from Razorpay's API documentation, then test it with Run once. Keep in mind that Make's doc page for Razorpay is marked as AI-generated, so confirm important details with Razorpay directly. Run once shows the bundle the module received back, which tells you whether the request needs adjusting.
05Should you use Make or n8n for Razorpay?
It depends on what your team already runs. In Make, Razorpay offers 7 instant triggers on payments, invoices, links and pages, plus Make an API Call for everything else, and it works from the Free plan. The same app often has an n8n node as well. Compare the modules each tool lists for Razorpay against the events you need, and pick the tool where your other automations already live. Testing each option on one real event is the surest way to decide.
Same platform

Other docs you might need on this stack.

Browse all integrations