WhatsApp is where Indian customers reply, and a message lands in seconds. The hard part is wiring it to your systems so the right message goes out by itself: an order confirmation when a Sales Order is submitted, a payment reminder when an invoice falls due, a reply when a lead messages at midnight. n8n is a self-hosted automation engine that connects WhatsApp to ERPNext, your database and any API, on infrastructure you own.
Quick answer
Connect n8n to the WhatsApp Business Platform, either Meta's Cloud API directly (n8n has a WhatsApp Business Cloud node) or a provider's API. n8n listens for events (a new order, a due invoice, an inbound message), runs your logic and sends templated or free-form WhatsApp messages. Self-hosted, there is no per-task automation fee; Meta still charges per delivered message: templates by category since 1 July 2025, and replies inside the 24-hour window since 1 October 2026, after a free monthly tier (Meta, checked 14 October 2026). MithTech, a team of Frappe specialists in Bengaluru, builds and runs self-hosted n8n WhatsApp automation wired to ERPNext.
Most businesses start with manual WhatsApp: someone copying details into chats. It does not scale. The fix is automation: events in your systems send WhatsApp messages, and inbound messages trigger actions. n8n is the layer in between, without per-task SaaS fees. Our own tool for this is Polygin, WhatsApp automation logged in ERPNext.
How do the pieces fit together?
WhatsApp automation has three layers:
- The WhatsApp Business Platform. Messages go through Meta's Cloud API, used directly or through a provider such as Gupshup or Twilio, or a platform such as WATI or Interakt that adds its own tools. This is the delivery pipe, with an API to send and receive.
- n8n, the automation engine. n8n decides what to send and when. It listens for events, runs logic (look up a record, check a condition, format a message) and calls the WhatsApp API.
- Your systems. ERPNext, a database, a form or any app that holds the data and produces the events worth a message.
For how n8n compares to hosted automation tools, see n8n vs Zapier vs Make for Indian businesses.
Why self-hosted n8n for WhatsApp?
- Cost at volume. Self-hosted n8n Community Edition has no licence fee and no limit on executions under its Sustainable Use License; you pay for a small server. Per-task automation platforms charge for every step, and WhatsApp flows are multi-step.
- Data control. The automation logic, credentials and execution logs stay on your server, which matters when messages carry customer details, orders or payment links.
- Flexibility. n8n's HTTP Request node talks to any provider and any Indian API; Code nodes handle logic that linear tools cannot.
Which WhatsApp automations are worth building?
| What n8n does | ||
|---|---|---|
| Order confirmation | Sales Order submitted in ERPNext | Look up the order and customer, send a templated confirmation |
| Payment / invoice reminder | Invoice due date reached | Find unpaid invoices, send reminders with the amount and a payment link |
| Appointment / fee reminder | Scheduled time or due date | Send a reminder; optionally collect a reply to confirm |
| Lead capture | Inbound WhatsApp message or web form | Create a lead in ERPNext or your CRM, auto-reply, notify sales |
| Delivery / status update | Status change in your system | Tell the customer at each stage |
| Inbound auto-reply / bot | Customer message received | Match the intent, reply from data, hand over to a person when needed |
The pattern is always the same: an event fires, n8n adds data from your systems, and a WhatsApp message goes out; or an inbound message creates a record and a reply. Most order, payment and delivery updates are utility templates, which Meta prices below marketing templates. Inside an open customer service window they were free until 30 September 2026; since 1 October 2026 Meta charges for them there too (Meta, checked 14 October 2026).
How do you wire n8n to ERPNext?
ERPNext holds the orders, invoices, customers and leads, so it is the system most worth connecting. n8n works with it through webhooks and the REST API:
- ERPNext → n8n: an ERPNext Webhook fires when a document is submitted (a Sales Order, a Payment Entry, a Lead) and posts to an n8n Webhook node, which starts the flow.
- n8n → ERPNext: n8n's ERPNext or HTTP Request node reads or writes any DocType, so an inbound WhatsApp message can create a Lead, log a Communication or update an order.
That two-way link is what turns "send a message" into "send the right message from live business data". The setup steps, authentication and security are in ERPNext n8n integration.
What are the rules on templates and consent?
WhatsApp business messaging has guardrails to design around:
- Template approval. Business-initiated messages (notifications, reminders) use templates Meta has approved. n8n fills the variables at send time; the template must be approved first.
- Service windows. Free-form replies are allowed for 24 hours after a customer messages you; outside that window, you use templates.
- Pricing. Meta charges per delivered message, by category and country: each template message (marketing, utility, authentication) since 1 July 2025, and replies inside the 24-hour window since 1 October 2026, after a free monthly tier. Check Meta's pricing page, updated 30 September 2026 and checked 14 October 2026, for India's current rates; a provider adds its own fees.
- Consent. Send only to customers who have opted in, and honour opt-outs. It is policy and good practice.
How does n8n compare to an all-in-one WhatsApp tool?
| Cost model | Your server + Meta (and provider) message fees | Subscription + message fees |
| Automation depth | Any API, any logic | Within the product's features |
| ERPNext integration | Full, through REST and webhooks | Varies; often limited |
| Where the logic and logs live | Your server | Vendor cloud |
| Setup effort | Higher (engineering) | Lower (turnkey) |
| Suits | Custom, high-volume, system-driven flows | Broadcasts, a shared inbox, simple bots |
If you need broadcasts, a shared team inbox and simple chat flows, a packaged platform is faster to start. If you need automations driven by live ERPNext data, at volume, with the logic on your own server, n8n is the stronger engine. Between the two, Polygin is a WhatsApp platform run by MithTech (a licensed product, not open source): broadcasts, chat flows and a shared inbox on Meta's Cloud API, and an ERPNext app that logs each message on the record that already has that number. It does not create Leads or Sales Orders; that is a job for n8n.
When is this the right approach?
Self-hosted n8n with WhatsApp makes most sense when:
- You run ERPNext, or another system, and want messages driven by real events in it.
- Your volume makes per-task automation fees painful.
- You need custom logic (conditions, lookups, flows across systems), not just broadcasts.
- Control over the customer data in your automations matters.
How does MithTech build it?
We deploy self-hosted n8n on your cloud, connect Meta's Cloud API or your provider, build the flows (order updates, reminders, lead capture, bots) and wire them to ERPNext both ways, with encrypted credentials and monitoring. See marketing automation, or talk to us.
Frequently asked questions
+Do I need the WhatsApp Business API to automate WhatsApp?
For automated, business-initiated messaging, yes: the WhatsApp Business Platform, through Meta's Cloud API directly or a provider such as Gupshup or Twilio. n8n runs the logic and calls that API. The WhatsApp and WhatsApp Business phone apps are not built for programmatic automation, and unofficial tools that drive them risk a ban.
+Is self-hosted n8n really free for WhatsApp automation?
The software is: n8n Community Edition has no licence fee and no execution limit under the Sustainable Use License, for internal business use. You pay for the server and its upkeep. Messages are not free. Meta charges per delivered message, by category: templates since 1 July 2025, and replies inside the 24-hour window since 1 October 2026, after a free monthly tier (Meta, checked 14 October 2026). A provider adds its own fees. n8n removes the per-task automation fee, not the messaging cost.
+Can n8n send WhatsApp messages from ERPNext events?
Yes. An ERPNext Webhook fires when a document is submitted (a Sales Order, Payment Entry or Lead) and starts an n8n workflow, which looks up the data and sends a templated WhatsApp message. n8n can also write back to ERPNext, so inbound messages create or update records.
+Do WhatsApp message templates need approval?
Yes. Business-initiated messages use templates Meta must approve before they can be sent. n8n fills the variables at send time. Free-form replies are allowed within the 24-hour customer service window after a customer messages you.
+Which is better, n8n or a packaged WhatsApp tool?
It depends on the job. A packaged tool is faster for broadcasts, a shared inbox and basic bots. n8n is stronger for automations driven by live ERPNext data, complex logic or high volume, with the logic on your own server. We build custom n8n flows and also run Polygin, and will recommend whichever fits.
+Is WhatsApp automation compliant with data-privacy expectations?
Self-hosting n8n keeps your automation data and logs on infrastructure you control, which helps with the DPDP Act; the message content still passes through Meta under WhatsApp's terms. Send only to opted-in customers, honour opt-outs and follow WhatsApp's policies; we build those into the flows.
Comments & ratings
No comments yet. Start a new discussion.
Manoj · Published on 27 June 2026
Worked with us? Leave a Google review