Add Razorpay customers to Campaign Monitor as subscribers

Each time Razorpay captures a payment, the payer is added as a subscriber to the Campaign Monitor list you choose, so the people who pay you also hear about updates and offers.

Razorpay

Campaign Monitor

Download this workflow Browse more workflows

2 steps Setup ~5 min Used on 3.1k sites Free to import

The Add Razorpay customers to Campaign Monitor as subscribers workflow on the FlowMattic canvas, with 2 steps across Razorpay, Campaign Monitor — The workflow as it appears in the builder after import. Each step opens for editing.

What this workflow does

Razorpay knows who paid you, but your newsletter list in Campaign Monitor doesn't, unless someone exports customers and imports them again. This workflow closes that gap by adding the payer to a list each time a payment goes through.

The Razorpay Payment Captured trigger fires when a payment is captured on your account and passes the payment details on. Look at a test run to see which contact fields the payment carries, such as the payer's email address and phone number.

The Campaign Monitor step adds a subscriber to a list. It ships unmapped: connect your account, choose the list and map the payer's email, plus a name if the payment includes one. A separate list for paying customers lets you send them their own messages.

The trigger is a payment event, not a new-customer event, so someone who pays you twice starts two runs and is sent to Campaign Monitor each time. Also think about consent: only add payers you are allowed to email under your own privacy terms. Task History shows each payment and Campaign Monitor's response.

Customer-only updates after a purchase

A course seller taking payments by Razorpay keeps buyers on a Campaign Monitor list that gets new lesson announcements.

Donor list for a nonprofit

A charity collecting donations through Razorpay adds each donor to a list for its quarterly impact newsletter.

Service clients for seasonal reminders

A repair shop that bills through Razorpay puts paying clients on a list for service reminders and seasonal offers.

How this workflow runs

What happens at each step once the workflow is on, and what you need before you import it.

Step 1Trigger
Razorpay Payment Captured
Starts the workflow whenever Razorpay captures a payment on your account. FlowMattic hands the payment record to the next step; look at a test run for the email and other contact fields you can map.
Step 2Action
Campaign Monitor Add Subscriber
Adds the payer as a subscriber on a Campaign Monitor list. The template leaves the step unmapped, so connect your account, pick the list and map the email address from the Razorpay payment.

What you need

FlowMatticCore
Razorpay AccountAccount
Campaign Monitor AccountAccount

After importing, map your own data. To keep the template universal, not every step is pre-filled. Open each step in the builder and connect your accounts and fields (channels, lists, sheets, recipients) before you switch the workflow on.

Make it yours

Changes worth making after you import it.

Create a dedicated Campaign Monitor list for Razorpay customers, so their emails can differ from the ones your general subscribers get.
Put a Filter between the Razorpay trigger and the Add Subscriber step that continues only when the payment's email is not empty, so payments without an address stop before Campaign Monitor.
Map the payment amount or description into a Campaign Monitor custom field if you want to segment customers by what they bought.

Questions about this workflow

What happens when a Razorpay customer pays a second time?

Each captured payment starts a new run, so the same person is sent to Campaign Monitor again. Campaign Monitor decides how to treat an address already on the list; check Task History after a repeat payment.

Does the Razorpay payment include the customer's email?

Make a test payment and look at the trigger data in Task History. Map the email field it shows into the Add Subscriber step. If some payments arrive without one, put a Filter between the Razorpay trigger and the Add Subscriber step.

Are failed Razorpay payments added to Campaign Monitor?

No. The workflow uses the Payment Captured event, which fires once a payment is captured. Failed payments are a separate Razorpay event that this template doesn't listen to.