Skip to content
Per-pair page

Connect RazorPay to Gmail in two minutes.

Real-time triggers from RazorPay, ready-made actions in Gmail. Filter, transform, and route without writing a line of code.

Trigger app
RazorPay as the trigger

Workflows fire when something happens in RazorPay.

Action app
Gmail as the action

Workflows do something in Gmail, instantly.

See all 27 actions →
Both directions

Pick the way that fits your stack.

Pair pages are mirrored. Each direction gets its own dedicated page.

RazorPayGmail

When something happens in RazorPay, do it in Gmail.

3 RazorPay triggers wired to 27 Gmail actions. Most-used pairing: RazorPay Payment CapturedAdd Labels to Message.

GmailRazorPay

Or fire it the other way around.

1 Gmail triggers wired to 4 RazorPay actions downstream.

See GmailRazorPay
Popular pairings

Common RazorPay → Gmail workflows.

Pick a pairing to set it up in two minutes. Each one is a fully editable recipe.

Showing 9 of 81 combinations
When razorpay payment captured in RazorPay, add labels to message in Gmail.

Fires when a payment auth-and-captures successfully. Payload includes amount, method (UPI/card/netbanking), customer, notes. The revenue-event hook for India-focused commerce workflows.

When razorpay payment captured in RazorPay, create draft in Gmail.

Fires when a payment auth-and-captures successfully. Payload includes amount, method (UPI/card/netbanking), customer, notes. The revenue-event hook for India-focused commerce workflows.

When razorpay payment captured in RazorPay, create label in Gmail.

Fires when a payment auth-and-captures successfully. Payload includes amount, method (UPI/card/netbanking), customer, notes. The revenue-event hook for India-focused commerce workflows.

When razorpay payment captured in RazorPay, delete draft in Gmail.

Fires when a payment auth-and-captures successfully. Payload includes amount, method (UPI/card/netbanking), customer, notes. The revenue-event hook for India-focused commerce workflows.

When razorpay payment failed in RazorPay, add labels to message in Gmail.

Fires when a payment fails. Payload includes reason code and human-readable message. For dunning workflows that branch on failure reason (soft decline → retry email, hard decline → payment-method update prompt).

When razorpay payment failed in RazorPay, create draft in Gmail.

Fires when a payment fails. Payload includes reason code and human-readable message. For dunning workflows that branch on failure reason (soft decline → retry email, hard decline → payment-method update prompt).

When razorpay payment failed in RazorPay, create label in Gmail.

Fires when a payment fails. Payload includes reason code and human-readable message. For dunning workflows that branch on failure reason (soft decline → retry email, hard decline → payment-method update prompt).

When razorpay payment failed in RazorPay, delete draft in Gmail.

Fires when a payment fails. Payload includes reason code and human-readable message. For dunning workflows that branch on failure reason (soft decline → retry email, hard decline → payment-method update prompt).

When razorpay refund processed in RazorPay, add labels to message in Gmail.

Fires when a refund clears (UPI is sub-minute, cards can take days). For "refund processed → revoke product access, update customer record, log to refund tracking" workflows.

How it works

Connect RazorPay and Gmail in five steps.

No code, no glue, no half-day setup. Each step is one click.

  1. 1
    Connect
    Authorize RazorPay and Gmail

    Open Tiny Command, authorize RazorPay and Gmail once each. Both connections are available to every workflow on your account.

  2. 2
    Trigger
    Pick a RazorPay trigger

    Drop the RazorPay → RazorPay Payment Captured trigger onto the canvas. Tiny Command auto-registers the webhook.

    POST /v1/webhooks/razorpay.trigger-payment-captured
  3. 3
    Transform
    Add a filter or AI step

    Optionally add a Filter node ("subject contains URGENT") or an AI step ("classify intent") between trigger and action.

  4. 4
    Action
    Add the Gmail action

    Drop the Gmail → Add Labels to Message action below it. Map fields from the RazorPay payload into the Gmail inputs.

    google-gmail.add-labels
  5. 5
    Publish
    Publish and forget

    Hit Publish. Tiny Command runs it in production from second one. Watch the run-log fill up.

FAQ

Questions about RazorPay + Gmail.

How long does it take to connect RazorPay and Gmail on Tiny Command?
Under two minutes. Authorize RazorPay and Gmail once each, drop the RazorPay trigger and Gmail action onto a workflow canvas, map a couple of fields, and publish. No code, no glue.
Is the RazorPay ↔ Gmail integration real-time?
Yes. Both RazorPay and Gmail expose webhooks, so events from one fire workflows in the other within seconds rather than on a polling interval.
Can I filter or transform data between RazorPay and Gmail?
Yes. Add a Filter node to only pass through matching events, a Switch node to branch by value, or an AI / Code node to transform payloads before they hit Gmail.
What RazorPay events can trigger a Gmail workflow?
Any of the 3 RazorPay triggers, including "RazorPay Payment Captured". Each fires in real time when the matching event happens in RazorPay.
Do I need a paid plan to use RazorPay with Gmail?
No. There's a free tier that covers most RazorPay+Gmail use cases without a credit card. Paid plans unlock higher run volumes and team features when you outgrow it.
What if I want Gmail → RazorPay instead?
Build it the same way, in reverse. There's a dedicated /integrations/google-gmail/with/razorpay page with the reverse-direction triggers and actions.
Related

Other apps that pair well with RazorPay.


Wire RazorPay to Gmail in 2 minutes.

Free tier available. No credit card. No onboarding call.