Make (Integromat) Complete Guide for Indian Businesses: Setup, Pricing, and Best Workflows (2026)
Make is 6–8× cheaper than Zapier at 10K ops. Free plan gives 1,000 ops/month. Native Razorpay, WhatsApp, and Zoho integrations. 8 ready-to-build automation scenarios for Indian SMBs.
- Make is 6–8× cheaper than Zapier at 10K ops. Free plan gives 1,000 ops/month. Native Razorpay, WhatsApp, and Zoho integrations. 8 ready-to-build automation scenarios for Indian SMBs.
- Use this as an automation tools checklist for make complete guide for indian businesses, not as a substitute for checking current official or platform rules.
- Confirm API limits, authentication, webhook payloads, pricing, and compliance rules against the source links before filing, buying software, changing campaigns, or changing a workflow.
Most Indian SMB owners automating their business right now are either on Zapier, paying far too much, or stuck on manual processes waiting for a tool they can actually afford. Make (formerly Integromat) is the platform that sits between those two outcomes. It connects 3,000+ apps including Razorpay and WhatsApp Cloud API, costs 6-8x less than Zapier at comparable volume (YouStable, 2026), and its free plan gives 1,000 operations per month - enough to run two or three automations indefinitely. This guide walks you through exactly what Make does, what it costs in rupees, how to set it up, and eight specific workflows built for Indian businesses.
If you're still comparing tools, our guide to workflow automation tools for India covers the full market before you commit to any platform.
- Make's free plan covers 1,000 operations/month - enough for 2-3 light automations at no cost. (Make.com, 2026)
- Make Core at ₹750/month handles most Indian SMBs with 5-10 workflows. That's cheaper than a single day of data entry work.
- Each module in a scenario counts as one operation per run. An 8-step scenario running on 100 events/month uses 800 operations.
- Make connects natively to Razorpay, Zoho CRM, Zoho Books, WhatsApp Cloud API, and Google Sheets - the core Indian SMB stack.
What is Make and how does it work?
Make is a visual automation platform with 500,000+ teams using it globally and 3,000+ app integrations built natively (Make.com, 2026). You build "scenarios" - workflows that connect apps using a drag-and-drop canvas. Each scenario has a trigger (something that starts the workflow) and one or more actions (things Make does in response). No code required for most use cases.
The central concept in Make is the operation. Every module in a scenario counts as one operation each time it runs. A scenario with five modules processes five operations per trigger event. So a 5-module scenario running on 200 events per month uses exactly 1,000 operations - which is precisely the free plan limit. That's the maths you need to watch.
Make scenarios are more powerful than basic Zapier Zaps. They support loops (repeat an action for each item in a list), iterators (split an array into individual items), routers (branch a workflow based on conditions), and error handlers (define what happens when a module fails). A Zapier Zap is linear: trigger, then steps, in sequence. A Make scenario can branch, loop, and recover from failures. That flexibility matters once your workflows get real.
Who is Make built for? Teams comfortable clicking and configuring settings in a browser. You don't need to write code. You do need to understand what data you're moving and why. If you can fill out a form and read a JSON payload without panicking, you can build useful Make scenarios within a few hours.
Make pricing for Indian businesses - what you actually pay
Make bills in USD, but at current exchange rates the Core plan at $9/month works out to roughly ₹750/month. That's less than a single day of minimum-wage data entry work in most Indian cities, and it gives you 10,000 operations per month. Most Indian SMBs running 5-10 workflows stay on Core indefinitely (Make.com, 2026).
| Plan | Monthly cost (approx.) | Operations/month | Min. trigger interval | Best for |
|---|---|---|---|---|
| Free | ₹0 | 1,000 | 15 minutes | Testing, 1-2 light automations |
| Core | ~₹750 ($9) | 10,000 | 5 minutes | Most Indian SMBs: 5-10 workflows |
| Pro | ~₹1,350 ($16) | 10,000 | 1 minute | Time-sensitive workflows, unlimited active scenarios |
| Teams | ~₹2,400 ($29) | 10,000 | 1 minute | Multi-member teams needing shared access |
[UNIQUE INSIGHT] The jump from Core to Pro doesn't give you more operations - both include 10,000 per month. The real differences are: Pro drops the minimum trigger interval from 5 minutes to 1 minute (critical for real-time WhatsApp confirmations or payment alerts), and Pro removes limits on active scenarios. Core restricts how many scenarios can be "on" simultaneously. If you're running more than a handful of concurrent automations, Pro at ₹1,350 is the right choice, not Core.
One practical note: Make accepts Indian credit and debit cards for billing. International transaction fees from your bank (typically 1.5-3.5%) will apply since Make charges in USD. Factor that into your actual monthly cost. At $9, you're looking at roughly ₹750-780 total depending on your bank.
Setting up Make - first 30 minutes
84% of enterprises are already using or planning no-code automation tools like Make (Gartner via Quixy, 2026). Getting started takes less than 30 minutes if you follow these steps in order. The most common first mistake - not setting your timezone - causes scheduled scenarios to fire at wrong times, often at 3 AM instead of 9 AM. Fix this before you build anything.
- Create your account at make.com. Email signup is free, no credit card required. The free plan starts immediately.
- Set your timezone to Asia/Kolkata. Go to your profile icon in the top right, then Settings, then the General tab. Change timezone to Asia/Kolkata. This is critical. Without it, any scheduled scenario uses UTC by default, which is 5 hours 30 minutes behind IST.
- Connect your first app. Google Sheets is the best first connection for testing. Go to the Connections tab in the left sidebar, click Add, search for Google Sheets, and authenticate with your Google account. Make stores this connection securely for all future scenarios.
- Create your first scenario. Click Scenarios in the left sidebar, then Create a new scenario. In the canvas, click the large + circle, search for Google Sheets, select the "Watch Rows" trigger, and choose your connected spreadsheet. Add a second module: search for Gmail, select "Send an Email", and map the row fields to the email body. You've just built your first automation: "When a new row is added to this sheet, send an email."
- Test with a real trigger. Click the Run once button at the bottom of the canvas. Make will wait for you to add a row to your Google Sheet. Add one. Watch Make process it in real time. The visual execution trace shows you exactly which modules ran and what data passed through each one.
- Schedule the scenario. Click the clock icon next to the trigger module to set how often Make checks for new rows. On the free plan, the minimum is 15 minutes. On Core and above, you can go to 5 minutes. Toggle the scenario on using the switch at the bottom of the canvas. It's now live.
That's it. You've gone from signup to a live, running automation in under 30 minutes. The same pattern - connect apps, map data, test, schedule - applies to every scenario you'll build in Make.
8 Make automation scenarios for Indian SMBs
88% of SMBs say automation helps them compete with larger companies (Gitnux, 2026). The eight scenarios below are built around the Indian business stack: Razorpay, Zoho, WhatsApp, Google Sheets, and common e-commerce setups. Each includes the ops count so you can budget your plan before building.
Lead form to WhatsApp message
What it does: When someone submits your contact or enquiry form (on Typeform or JotForm), Make immediately sends them a WhatsApp message acknowledging their enquiry. Leads get a response in seconds, not hours.
Modules: Typeform or JotForm (watch new submission) + WhatsApp Cloud API (send message). Ops per run: 2. At 200 leads/month, that's 400 operations. Comfortably inside the free plan. Build time: 1 hour. The WhatsApp Cloud API module requires a Meta Business account and a verified phone number - set that up first, it takes 15-30 minutes separately.
Razorpay payment to Zoho Books invoice and WhatsApp confirmation
What it does: When Razorpay captures a payment, Make creates the corresponding invoice in Zoho Books and sends the customer a WhatsApp message with the invoice details. Replaces a manual step that most finance teams do at end of day.
Modules: Razorpay (webhook: payment.captured) + Zoho Books (create invoice) + WhatsApp Cloud API (send message). Ops per run: 3. At 300 payments/month, that's 900 operations - still inside the free plan. Build time: 3-4 hours. The Razorpay webhook configuration needs to be done inside your Razorpay dashboard as well. Allow time for that.
New Zoho CRM lead to salesperson WhatsApp alert
What it does: When a new lead enters Zoho CRM (from any source: web form, manual entry, ad lead gen), Make immediately sends a WhatsApp message to the assigned salesperson with the lead's name, number, and source. Response times drop from hours to minutes.
Modules: Zoho CRM (watch new leads) + WhatsApp Cloud API (send message). Ops per run: 2. Build time: 1 hour. You'll use Make's text formatter module to compose the WhatsApp message nicely - that adds 1 more op per run, so budget 3 total.
Weekly revenue report to WhatsApp
What it does: Every Monday at 9 AM, Make reads your revenue data from Google Sheets, formats a summary, and sends it to your WhatsApp (or a team WhatsApp group via the API). Founders get their weekly number without opening any dashboard.
Modules: Schedule trigger + Google Sheets (read rows) + Text formatter + WhatsApp Cloud API (send message). Ops per run: 3-4. Runs once a week, so 12-16 operations per month. This easily fits the free plan alongside other scenarios. Build time: 2-3 hours.
For a deeper look at this specific pattern, our guide to automating business reports via WhatsApp covers the full setup including formatting and group message routing.
GST deadline reminder
What it does: On the 8th and 17th of each month, Make sends a WhatsApp reminder to the business owner (and optionally the accountant) about upcoming GST filing deadlines. Simple but eliminates a common source of late fees.
Modules: Schedule trigger (run on specific dates) + WhatsApp Cloud API (send message). Ops per run: 2. Runs twice a month, so 4 operations monthly. Practically free. Build time: 30 minutes. The date-based schedule trigger in Make lets you specify exact days of the month.
Low inventory alert from Google Sheets
What it does: Make watches a Google Sheet where you track inventory levels. When a product's quantity column drops below a threshold you define, Make sends a WhatsApp alert with the product name and current stock count. Works for any business managing stock in a spreadsheet.
Modules: Google Sheets (watch rows) + Filter (check threshold condition) + WhatsApp Cloud API (send message). Ops per run: 3 (the filter doesn't add ops if it prevents the next module from running). Build time: 1-2 hours. Make's filter module is the key here: it checks whether the quantity is below your number and only continues the scenario if it is.
Order shipped to customer WhatsApp notification
What it does: When Shiprocket marks an order as shipped and fires a webhook, Make catches it and sends the customer a WhatsApp message with the order ID, courier name, and tracking link. Reduces "where is my order?" support queries immediately.
Modules: Webhooks (custom webhook to receive Shiprocket event) + HTTP module (optional: fetch tracking details) + WhatsApp Cloud API (send message). Ops per run: 2-3. Build time: 2 hours. Shiprocket's webhook configuration is inside your Shiprocket dashboard under Settings - Webhooks. Add the Make webhook URL there.
New contact in Google Sheets to Zoho CRM
What it does: When someone adds a new row to a designated Google Sheet (useful when your sales team logs contacts from calls or events), Make automatically creates a matching contact record in Zoho CRM. Eliminates double data entry.
Modules: Google Sheets (watch new rows) + Zoho CRM (create contact). Ops per run: 2. Build time: 45 minutes. Map the sheet columns to Zoho CRM fields inside Make's interface. It's a straightforward field-mapping exercise with no code.
Make vs Zapier - the India cost comparison
At 10,000 operations per month, Zapier's Professional plan costs approximately $49/month (around ₹4,100), while Make Core costs $9/month (around ₹750). That's a 6-8x cost gap for the same volume, a difference that compounds quickly as your workflow count grows (YouStable, 2026).
The comparison gets even more dramatic as volume grows. Zapier's pricing scales steeply past 10,000 tasks, while Make's per-operation costs stay low. For Indian businesses that are already on Zapier and wondering why their automation bill keeps climbing, the answer is usually that a switch to Make Core pays for itself within the first month.
One nuance worth noting: Zapier counts tasks the same way Make counts operations - each step in a Zap uses one task. So the comparison is apples to apples on volume. The only genuine Zapier advantage is a larger native app library and a longer market history. For Indian SMBs, Make's 3,000+ integrations cover everything in the standard business stack.
Where Make falls short
60% of automation users recover full ROI within 12 months (Forrester via Quixy, 2026), but that outcome assumes you've picked the right tool for your volume and complexity. Make has real limitations that trip up Indian businesses who adopt it without understanding the trade-offs. Here's what to watch for.
Operation counting gets expensive at scale
A complex 20-module scenario uses 20 operations per trigger event. At 2,000 events per month, that's 40,000 operations - four times the Core plan's monthly limit. You'd need to buy additional operation bundles or upgrade. This is the most common "shock moment" for Make users who build sophisticated workflows without budgeting ops first. Always multiply your module count by your expected monthly trigger volume before choosing a plan.
UI complexity at scale
Scenarios with 20+ modules become hard to read and debug in Make's canvas. The visual flow becomes cluttered. Error tracing requires clicking through each module individually. n8n's canvas handles large workflow complexity better, with cleaner node grouping and sub-workflow capabilities. For straightforward 5-10 module scenarios, Make's UI is excellent. Beyond 15 modules, it's worth evaluating alternatives.
EU data residency - a DPDP Act consideration
Make processes workflow data on servers in Frankfurt and Ireland (Make.com, 2026). That means every payload your Make scenarios handle - customer names, phone numbers, order details, payment references - passes through EU servers. India's Digital Personal Data Protection Act 2023 is not yet fully enforced, but for businesses handling sensitive customer PII at scale, this is a real consideration. If your legal team asks where customer data goes during automation, the honest answer with Make is "EU servers."
For businesses where data residency matters - healthcare, fintech, lending, insurance, or any sector with regulatory sensitivity - n8n self-hosted on an AWS Mumbai or DigitalOcean Bangalore server is the cleaner compliance answer.
Free plan trigger interval
The 15-minute minimum trigger interval on the free plan means Make isn't checking for new data more than once every 15 minutes. For a GST deadline reminder or a weekly report, that's irrelevant. For a lead form that's supposed to send an instant WhatsApp reply, it means leads could wait up to 15 minutes. Core's 5-minute interval and Pro's 1-minute interval are much better for customer-facing automations. Factor this in when deciding whether to stay on the free plan.
[PERSONAL EXPERIENCE] For businesses processing 50,000+ operations per month, Make's per-operation pricing adds up faster than most founders expect. We've seen Indian SMBs hit ₹6,000-8,000/month on Make once they've built 15-20 workflows at moderate volume. That's the point where n8n self-hosted on a ₹1,500/month VPS becomes the rational choice. The migration takes time, but the payback is usually within 2-3 months.
Make vs n8n - which one for your stage?
n8n has 230,000+ active users globally and growing mid-market adoption, particularly among technical teams who need data residency control (Flowlyn, 2026). Make dominates among non-technical SMBs who want to be running in a day. The right choice depends on where your business sits right now - not where you aspire to be.
| Your situation | Pick |
|---|---|
| Starting out, non-technical team | Make (free plan) |
| 10-20 workflows, moderate volume (under 10K ops/month) | Make Core (~₹750/mo) |
| Time-sensitive workflows, need 1-min trigger interval | Make Pro (~₹1,350/mo) |
| Sensitive customer PII, data must stay in India | n8n self-hosted |
| More than 50,000 complex operations/month | n8n self-hosted |
| Developer available, want full infrastructure control | n8n self-hosted |
If you're weighing n8n seriously, our full n8n vs Make comparison for India breaks down the operation-counting difference, pricing crossover points, and DPDP Act compliance implications in detail.
FAQ: Make automation for Indian businesses
Is Make free to use?
Yes. Make's free plan includes 1,000 operations per month, unlimited scenarios, and access to all 3,000+ integrations. The only restrictions are the 15-minute minimum trigger interval and limits on active (switched-on) scenarios. For testing and light automations - 2-3 simple workflows running on low volume - the free plan is genuinely sufficient indefinitely. (Make.com, 2026)
Does Make work with Razorpay in India?
Yes. Make has a native Razorpay integration that supports webhook triggers (including payment.captured, payment.failed, and refund events) and action modules for fetching payment details. You configure the webhook URL inside your Razorpay dashboard under Settings - Webhooks, then use that URL as the trigger endpoint in your Make scenario. The most common Indian use case is payment to invoice creation in Zoho Books, which typically takes 3-4 hours to build and test.
How is Make different from Zapier?
Make is 6-8x cheaper than Zapier at comparable operation volumes (YouStable, 2026), and its scenario builder is more powerful. Make supports loops, iterators, routers, and error handlers that Zapier's basic Zap structure doesn't offer. Zapier has a slightly larger app library and a simpler interface for absolute beginners. For Indian SMBs who've outgrown Zapier's pricing, Make is the standard next step before n8n self-hosted.
Can Make send WhatsApp messages automatically?
Yes, via the WhatsApp Cloud API integration. Make connects to Meta's WhatsApp Business Platform API natively. You need a verified Meta Business Account and a WhatsApp Business phone number with API access - setup takes 15-30 minutes on Meta's end. Once connected, Make can send template-based WhatsApp messages triggered by any event: form submissions, Razorpay payments, CRM updates, schedule triggers, or incoming webhooks from any app.
Where to go from here
Make is the most practical starting point for Indian SMBs who want to automate without hiring a developer or committing to server management. The free plan gives you real room to experiment. The Core plan at ₹750/month handles serious workflow volume. The limitations around EU data residency and operation counting at scale are real, but they only become pressing once you've built a mature automation stack.
Start with one of the eight scenarios above. The lead form to WhatsApp message takes an hour to build and delivers immediate, visible impact. Once that's running, add the Razorpay to Zoho Books scenario. By the time you've built three or four workflows, you'll have a clear picture of your monthly operation count and whether Core or Pro is the right plan.
If you'd rather have someone build and maintain these workflows for you, our workflow automation service covers Make, n8n, and WhatsApp automation setups for Indian businesses. You can also read our full comparison of automation tools for India if you're not yet decided on Make.
What should you verify before using this Automation Tools guide?
Before acting on make complete guide for indian businesses, verify the current rules or platform behavior with the n8n Docs. The practical answer depends on your business model, state, turnover, documents, software stack, and whether the decision affects tax, customer data, paid media spend, or a production workflow.
Use this article as a working checklist, then confirm API limits, authentication, webhook payloads, retries, error handling, and hosting requirements. In our audits, most expensive mistakes do not come from ignoring the whole process. They come from one stale assumption, one mismatched address, one missing event, or one automation path that nobody tested after launch.
| Checkpoint | Why it matters | Where to confirm |
|---|---|---|
| Current rule or platform status | Limits, forms, policies, and APIs can change after a blog update. | n8n Docs |
| Your exact business case | A local shop, freelancer, D2C store, agency, and SaaS team rarely need the same next step. | Documents, invoices, campaign data, analytics setup, or workflow logs |
| Implementation evidence | The safest workflow decision is backed by proof, not memory or screenshots from an old setup. | Portal acknowledgement, dashboard export, invoice sample, test lead, or error log |
How do we apply this in real business work?
We start with the smallest decision that can be verified. For compliance work, that means matching PAN, address, bank, invoices, and portal status before filing. For websites, marketing, analytics, and automation, it means testing the real user path from first click to final record. The boring checks catch the costly failures.
A useful rule: if a claim changes money, tax, reporting, or customer communication, keep evidence for it. Save the acknowledgement, export the report, test the form, and note the date you verified the source. That gives you a clean trail when a client, officer, platform, or internal team asks why the setup was done that way.
When should you get expert review?
Get expert review when the next action can create tax exposure, lost reporting data, ad waste, broken customer communication, or production downtime. A simple self-check is enough for low-risk learning. A filed return, new registration, tracking migration, paid campaign restructure, or live automation deserves a second set of eyes before it affects customers or records.
How often should this be rechecked?
Recheck the decision whenever your turnover, state, product mix, campaign budget, website stack, analytics property, or workflow ownership changes. Also recheck it after major portal updates, platform policy changes, annual filing deadlines, and vendor migrations. The guide is useful today only if the facts behind it still match your business.
What is the fastest safe way to decide?
Write the decision in one sentence, list the proof needed for that sentence, and verify only those items first. This keeps the work focused. If the proof confirms the decision, proceed. If one item is unclear, pause and resolve that point before changing filings, campaigns, tracking, website code, or automation logic.
What can go wrong if you skip verification?
The usual failure is not dramatic at first. It looks like a rejected application, a wrong tax invoice, a missing conversion, a duplicate lead, a broken report, or a workflow that silently stops. Those small failures become expensive when nobody notices them until month-end reporting, filing day, or a customer escalation.
What evidence should you keep after making the change?
Keep enough evidence to reconstruct the decision later. For a compliance topic, that usually means the application reference number, registration certificate, invoice sample, return acknowledgement, payment challan, notice reply, or source link checked on the day of filing. For a website, campaign, analytics setup, or automation, keep the before-and-after screenshot, test submission, dashboard export, webhook log, and the exact setting that changed.
This matters because most business fixes are revisited months later, when nobody remembers the original reason. A short evidence trail makes audits faster, handovers cleaner, and vendor conversations more precise. It also keeps the advice in this guide tied to your real operating context instead of becoming a generic checklist that gets copied without review.
- Date checked: record when the official source, dashboard, or portal screen was reviewed.
- Business context: note the entity, state, product, campaign, property, or workflow affected.
- Proof of action: save the acknowledgement, report export, test result, or live URL.
- Owner: assign one person to re-check the item when rules, tools, or business volume change.
Which next step should you take after reading this?
Turn the article into one action list. Mark what is already true, what needs proof, and what needs expert review. If you want to go deeper, compare this guide with Workflow Automation, and Chatbot Integration. Then update the decision only after the official source and your own records agree.
Frequently asked questions
Is Make free to use?
Yes. Make offers a free plan with 1,000 operations per month, unlimited scenarios, and access to all 3,000+ integrations. The free plan triggers every 15 minutes minimum, which works fine for non-time-sensitive automations like weekly reports or daily summaries. The Core plan at $9/month (≈₹750) upgrades to 10,000 operations and 5-minute trigger intervals.
Does Make work with Razorpay in India?
Yes. Make has a native Razorpay module. You can trigger scenarios on payment events (payment captured, payment failed, refund created) using Razorpay webhooks. The most common Indian SMB setup is Razorpay payment → Make → Zoho Books invoice + WhatsApp confirmation, which handles the full post-payment workflow automatically.
How is Make different from Zapier?
Make is 6–8× cheaper at equivalent volume and handles more complex workflows — loops, iterators, error handlers, and conditional routing that Zapier's linear Zap structure can't match. Zapier connects 8,000+ apps vs Make's 3,000+, making Zapier better for niche app integrations. For Indian SMBs running multi-step workflows with Razorpay, Zoho, and WhatsApp, Make's price-to-power ratio wins clearly.
Can Make send WhatsApp messages automatically?
Yes. Make has a native WhatsApp Cloud API module. Connect your Meta Business account, create approved message templates, and Make can send WhatsApp messages triggered by any event in your other apps — form submissions, payment confirmations, overdue invoices, or scheduled reports. The WhatsApp Cloud API charges approximately ₹0.35–0.58 per business-initiated conversation in India.
Let's talk about your business.
Tell us what you're working on and where you want to go. We'll put together a plan. No obligation, no sales pitch.
- Free 30-minute call
- A plan built around your goals
- No obligation, no pressure
- Your own account manager