E-commerce Workflow Automation for Indian Businesses: Razorpay → Invoice → WhatsApp → CRM (2026)

Every order on your Indian e-commerce store triggers at least five manual tasks: create an invoice, email it to the customer, send a WhatsApp confirmation, update your CRM, and log the payment in a spreadsheet. At 50 orders a day, that's 250 tasks. This post shows you how to automate the entire chain - from Razorpay payment capture to WhatsApp delivery - using Make or n8n, with no custom code required. The same chain handles GST-compliant invoicing via Zoho Books.

What do you need before building this automation?

Workflow automation cuts 500 hours per year from finance teams that previously handled payment reconciliation manually, according to Forrester via Quixy (2025). Before you see any of those savings, four accounts need to be active and configured correctly. Getting this setup right the first time saves hours of debugging later.

Accounts and tools you need

• Razorpay account with webhooks enabled (Settings → Webhooks in your Razorpay dashboard)
• Zoho Books account with at least one GST-configured item/service (plans from ₹749/month)
• Make account - Core plan at ₹750/month covers this chain comfortably, or n8n self-hosted at ₹500–2,000/month
• Meta Business account with WhatsApp Cloud API access and at least one approved message template
• Google Sheets with a log sheet pre-created (columns: Date, Customer, Amount, Order ID, Invoice No, Payment Method)

Technical prerequisites

• Razorpay webhook URL field - you'll paste your Make webhook URL here after creating the scenario
• Meta Business Manager access to create and submit WhatsApp message templates for approval (approval takes 1–4 hours)
• Zoho Books OAuth credentials - Make's Zoho Books module walks you through this on first connection
• Your GSTIN and the HSN/SAC codes for your product categories - needed for Zoho Books line items

Cost estimate and time to build

Monthly running cost: Make Core ₹750/month, WhatsApp Cloud API approximately ₹0.12 per utility conversation (order confirmations are utility category), and Zoho Books from ₹749/month. The full five-step main chain takes 4–8 hours to build and test for someone setting it up for the first time. Secondary chains (inventory, failed payments, shipping) add 1–2 hours each.

The main automation chain: step-by-step tutorial

Businesses that implement workflow automation report a 30–40% productivity increase in year one, according to Grand View Research via Quixy (2025). The chain below is the core of that productivity gain for e-commerce: one Razorpay payment captured triggers five downstream actions with zero manual input.

The Make module sequence is: Webhooks (Custom webhook) → Zoho Books (Create Invoice) → WhatsApp Cloud API (Send Message) → Zoho CRM (Create/Update Contact) → Google Sheets (Add Row). Each step is described below.

Step 1: Trigger - Razorpay payment webhook

In Make, create a new scenario and add a Webhooks → Custom webhook module as the trigger. Copy the generated webhook URL. In your Razorpay dashboard, go to Settings → Webhooks → Add New Webhook, paste the URL, and select thepayment.captured event. Set a webhook secret (you'll verify this in Make later).

After saving, click "Send test webhook" in Razorpay or make a ₹1 test payment. Make will capture the payload and auto-detect the data structure. Fields you need from the payload:payload.payment.entity.id (payment ID),payload.payment.entity.amount (in paise - divide by 100 for rupees),payload.payment.entity.contact (phone),payload.payment.entity.email,payload.payment.entity.notes.name or notes.customer_name, and payload.payment.entity.order_id.

Error handling for Step 1: add a Filter after the webhook module that checkspayload.event = "payment.captured". This prevents the scenario from running on other event types if you ever add more Razorpay webhook events to the same endpoint.

Step 2: Create invoice in Zoho Books

Add a Zoho Books → Create Invoice module. Map the fields from the Razorpay payload: Customer Name from notes.customer_name, Customer Email fromemail, and the line item description from your order notes or a fixed product name. Set the line item rate to the payment amount (paise divided by 100). Set GST rate based on your product's HSN/SAC code - map this from your order notes if you pass a product category in Razorpay's notes field.

Enable "Send Invoice" inside the Zoho Books module so the invoice is emailed to the customer automatically. Zoho Books generates a PDF and a shareable invoice link - save both as Make variables for the next step.

Error handling for Step 2: add a Make error handler on this module set to "Resume". If the customer email is missing from the Razorpay payload, set a fallback email (your support inbox) so the invoice is still created and you can forward it manually. Log missing-email events to a separate Google Sheet tab for follow-up.

Step 3: Send WhatsApp confirmation

WhatsApp messages achieve a 98% open rate compared to 20% for email (industry benchmark, 2025). Add a WhatsApp Cloud API → Send a Text Message module. Connect your Meta Business account. Select your pre-approved template. A working template for order confirmation:

"Hi {{1}}, your payment of ₹{{2}} is confirmed. Invoice: {{3}}. Order ID: {{4}}. Our team will be in touch within 24 hours. - [Your Brand]"

Map the variables: {{1}} = customer name, {{2}} = amount in rupees, {{3}} = Zoho Books invoice link from Step 2,{{4}} = Razorpay order ID. The phone number field should use thecontact field from Razorpay - Make sure it includes the country code (Razorpay stores it as +91XXXXXXXXXX format which WhatsApp Cloud API accepts directly).

Error handling for Step 3: if the phone number is missing, route to a fallback branch that logs the failure and skips WhatsApp without stopping the chain. The invoice email from Step 2 still reaches the customer.

Step 4: Update CRM

Add a Zoho CRM → Create/Update a Contact module. Search by email first to avoid duplicates. Map customer name, email, phone, and add the custom fields: Tag = "paid", Last Order Value = payment amount, Product Category = from order notes. Add a conditional branch: if payment amount is above your threshold (say ₹10,000), also create a CRM task assigned to your account manager to follow up within 48 hours.

If you use Google Sheets as your CRM instead of Zoho CRM, skip this module and handle everything in Step 5. The chain works the same way.

Step 5: Log to Google Sheets

Add a Google Sheets → Add a Row module. Map columns: Date (use Make'snow function formatted as DD/MM/YYYY), Customer Name, Amount (rupees), Order ID, Invoice Number from Step 2, Payment Method from Razorpay payload (payload.payment.entity.method: UPI / card / netbanking / wallet). This sheet becomes your daily/weekly revenue report source. A second Make scenario scheduled weekly can read this sheet and send a summary WhatsApp to the founder - covered in Chain 5 below.

Automation flow diagram

Chain 2: Low inventory alert via WhatsApp

Manual stock checks fail silently. Products go out of stock during peak hours, orders pile up, and the team finds out the next morning. An automated inventory alert catches the threshold drop the moment it happens and puts a WhatsApp message in the purchase manager's hands within seconds.

Build this in Make using a Google Sheets → Watch Rows trigger module set to poll every 15 minutes. Add a Filter: only continue if the "Current Qty" column value is less than or equal to your reorder threshold (e.g., 10 units). Then add aWhatsApp Cloud API → Send Message module with a pre-approved template:

"Low stock alert: {{1}} has {{2}} units remaining. Suggested reorder qty: {{3}}. - Inventory Bot"

Map {{1}} from the item name column, {{2}} from current qty, and {{3}} from a "Reorder Qty" column you pre-fill in the sheet. Send to the purchase manager's WhatsApp number stored in a config tab of the same sheet. This chain runs without any Razorpay dependency and costs roughly 1–2 Make operations per trigger check.

Chain 3: Failed payment follow-up

Leads responded to within 5 minutes convert 21 times better than those contacted after 30 minutes (industry benchmark, 2025). A failed payment is a warm lead - the customer intended to buy. A timely, helpful WhatsApp message can recover a significant share of those orders.

In Razorpay, add a second webhook event: payment.failed. You can use the same Make scenario webhook URL and use a Router module to split the flow based onpayload.event. The failed payment branch:

1. Route 1 for payment.captured: main chain (Steps 1–5 above)
2. Route 2 for payment.failed: add a Sleep module set to 30 minutes, then send a WhatsApp message

Approved template for failed payment: "Hi {{1}}, looks like your payment of ₹{{2}} didn't go through. No worries - you can retry here: {{3}}. This link is valid for 24 hours."

Get the payment retry link from Razorpay's API using an HTTP module: GET /v1/payment_links/{id}with your Razorpay key. Important: only send one follow-up per failed payment. Add a Google Sheets log step that records the payment ID and check against it before sending - this prevents double-messaging if the webhook fires twice.

Never send unsolicited promotional messages over WhatsApp. This chain only works because the customer explicitly attempted a transaction - that's the consent context. TRAI regulations prohibit spam, and Meta will restrict your WhatsApp number if message quality scores drop.

Chain 4: Order shipped - send tracking via WhatsApp

Customers in India check their shipment status an average of 4–6 times after placing an order. Sending the AWB (Air Waybill) number and tracking link proactively over WhatsApp eliminates most of those "where is my order?" support queries and reduces inbound support volume.

Both Shiprocket and Delhivery have native Make integrations and webhook support. When a shipment is created in Shiprocket, a webhook fires to Make with the AWB number, carrier name, and estimated delivery date. Build this chain:

1. Shiprocket webhook (shipment.created) → Make webhook trigger
2. HTTP module: GET tracking link from Shiprocket's tracking API using AWB number
3. WhatsApp Cloud API: send approved template with customer name, AWB, carrier, and tracking link
4. Google Sheets: log dispatch date, AWB, and carrier against order ID

Template: "Hi {{1}}, your order {{2}} has been shipped via {{3}}! Track it here: {{4}}. Estimated delivery: {{5}}."

For Delhivery, use their Push API to configure webhook events. The Make HTTP module handles both Shiprocket and Delhivery webhook payloads - the field names differ slightly but the AWB number and customer phone are present in both. Check the carrier's developer documentation for the exact field paths.

Chain 5: Monthly revenue report to founder via WhatsApp

Finance teams recover 500 hours per year when payment reconciliation is automated, according to Forrester via Quixy (2025). A scheduled monthly summary WhatsApp is the simplest version of that: one message on the first of each month, with all the numbers the founder needs in 30 seconds.

In Make, create a separate scenario with a Clock (Scheduled) trigger set to the 1st of each month at 8:00 AM. The chain:

1. Zoho Books → List Invoices: filter by last month's date range, status = "paid"
2. Make aggregator module: sum total revenue, count invoices sent, calculate outstanding amount (status = "sent" but not paid)
3. WhatsApp Cloud API: send approved template to founder's number

Template: "Monthly report - {{1}}: Revenue ₹{{2}} | Invoices sent: {{3}} | Received: {{4}} | Outstanding: ₹{{5}}. Full report in Zoho Books."

You can also pull from your Google Sheets revenue log (from Step 5 of the main chain) if you prefer a simpler data source than the Zoho Books API. The Sheets approach works fine for businesses under 500 orders per month. Above that, the Zoho Books API gives more accurate data including partial payments and credit notes.

Make vs n8n for this stack: which should you use?

88% of SMBs report that automation lets them compete with larger companies, according to Gitnux (2025). The tool you pick determines how quickly you get there and what it costs at scale. Both Make and n8n support every integration in the chains above: Razorpay, Zoho Books, WhatsApp Cloud API, Google Sheets, and Shiprocket.

[UNIQUE INSIGHT] n8n self-hosted becomes the clearly better economic choice at roughly 5,000+ orders per month. Here's the maths: the main chain in this post has 5 Make modules. Each order run consumes 5 Make operations. At 5,000 orders per month, that's 25,000 Make operations - already pushing into the ₹3,000–4,000/month tier. On n8n self-hosted, 5,000 orders per month = 5,000 executions, and executions are unlimited on a self-hosted instance. Your cost stays flat at the VPS price regardless of order volume. For a D2C brand crossing ₹50L per month in revenue, the savings easily justify hiring someone to manage the n8n server.

For DPDP Act compliance, self-hosted n8n on an Indian server is the only option that keeps customer PII (names, phone numbers, transaction data) fully within India. Make processes data on EU and US servers. If your legal team or a data protection officer asks where customer data goes during automation, n8n self-hosted on AWS Mumbai has the cleaner answer.

Common mistakes and how to avoid them

Most e-commerce automation projects fail not at the concept stage but at three specific technical points. Razorpay webhooks can fire more than once for the same payment event under certain network conditions, which means your automation can run twice and create duplicate invoices. Catching this early prevents a support nightmare.

Duplicate webhook fires from Razorpay

Razorpay may resend a webhook if it doesn't receive a 200 OK response within 5 seconds. Implement idempotency: in your Make scenario, before the Zoho Books module, add aGoogle Sheets → Search Rows step that looks for the payment ID in your log sheet. If found, stop the scenario with a Commit + Break. If not found, proceed and write the payment ID to the log immediately after the webhook trigger. This check adds one Make operation per run but prevents duplicate invoices entirely.

Missing GST rate mapping in Zoho Books

[PERSONAL EXPERIENCE] In our experience, this is the step where most Indian e-commerce automation setups fail. Zoho Books requires an explicit GST rate and HSN/SAC code per line item. If you pass a line item without a tax rate, Zoho Books creates the invoice without GST - which is non-compliant and invisible until your CA flags it at quarter end. The fix: maintain a product-to-HSN mapping table in Google Sheets, and add a Sheets lookup step before the Zoho Books module to retrieve the correct HSN and GST rate based on the product category passed in Razorpay's order notes.

Sending WhatsApp to numbers without consent

TRAI regulations prohibit unsolicited commercial communications. WhatsApp's own policy will restrict or ban your Business number if too many recipients block your messages. For the order confirmation and shipping chains above, the purchase transaction itself is your consent context - these are transactional/utility messages. Do not repurpose these automations for marketing broadcasts to anyone who hasn't explicitly opted in to receive promotional messages from you.

Not testing with a ₹1 test payment before going live

Razorpay's test mode generates fake webhook events, but they don't always mirror production payload structures exactly - especially for UPI vs card payments, which have different field structures. Create a Razorpay payment link for ₹1, make a real payment, and watch the Make scenario execution log. Check every field mapping before activating the scenario for live orders. This one test run catches 80% of field mapping errors.

FAQ: e-commerce automation with Razorpay in India

Does Razorpay support webhooks for automation?

Yes. Razorpay has a built-in webhook system under Settings → Webhooks in your dashboard. You can configure webhook URLs to receive real-time events including payment.captured,payment.failed, order.paid, and refund.created. Each event sends a JSON payload to your URL within seconds. Make, n8n, and Zapier all accept these webhooks natively - no custom server required. See our invoice automation guide for more on what you can do with Razorpay webhooks.

Can I connect Razorpay to Zoho Books automatically?

Yes, and it's one of the most common automation chains for Indian businesses. The connection runs via Make or n8n: Razorpay fires a payment.captured webhook, the automation platform receives it, and creates a GST-compliant invoice in Zoho Books using the Zoho Books API. Zoho Books then emails the invoice to the customer. The entire process takes 10–30 seconds from payment to invoice delivery. Automated invoice processing costs ₹415 per invoice compared to ₹1,040 manually, a 60% reduction (Forrester via Quixy, 2025).

How do I send automated WhatsApp messages after a Razorpay payment?

You need three things: a Meta Business account, WhatsApp Cloud API access, and an approved message template. Once those are set up, add a WhatsApp Cloud API module in Make after your Razorpay webhook trigger. Map the customer's phone number from the Razorpay payload (payload.payment.entity.contact) and fill in your template variables. WhatsApp messages see a 98% open rate vs 20% for email, making this the most effective delivery channel for order confirmations in India. Template approval takes 1–4 hours via Meta Business Manager.

Where to go from here

The five chains in this post cover 90% of the repetitive post-payment work in an Indian e-commerce operation. The main chain alone - Razorpay to Zoho Books to WhatsApp to CRM to Sheets - eliminates roughly 2–3 hours of manual work per 50 orders processed. At 100 orders per day, that's 4–6 hours saved daily, or one full-time data entry role redirected to higher-value work.

Start with the main chain. Build it, test it with a ₹1 payment, and run it live for one week. Once you trust the core flow, add the failed payment chain (Chain 3) - that one often recovers 5–15% of failed transactions within the first month. Then add shipping notifications and the inventory alert as operational stability becomes the priority.

If you want help building any of these chains or need someone to audit your existing automations, our workflow automation service covers Make and n8n setups for Indian e-commerce businesses. You can also read our invoice automation guide for Tally and Zoho for more on the invoicing side, or our WhatsApp marketing guide for building opt-in broadcast campaigns beyond transactional messages.