n8n WhatsApp Integration: Automate WhatsApp Business Cloud with n8n
n8n ships a built-in WhatsApp Business Cloud node and a WhatsApp Trigger. Wire them into any workflow to fire template messages from a trigger, catch replies, and route them across your stack, self-hosted or on n8n Cloud. Here is how it works and where it stops.
Both n8n and WaBulkSend run on Meta's official WhatsApp Cloud API.
An n8n workflow, simplified
Cloud APIShort answer: n8n integrates with WhatsApp through a built-in WhatsApp Business Cloud node and a separate WhatsApp Trigger node, both maintained by n8n and both connecting to Meta's Cloud API. You add your access token and Business Account ID once as a credential, then use the node to send template, text, and media messages as steps in a workflow, and the trigger to react to incoming messages. It is a strong fit for event-driven automation you host yourself: send a message when a webhook fires, a record changes, or an order ships, and route replies onward with code-level control. It is not a bulk campaign tool. n8n sends messages one workflow run at a time and has no contact list, template manager, or campaign analytics, so for sending one approved template to a whole audience and tracking delivery, a dedicated bulk sender is the better fit. Both run on the same Meta Cloud API, so you can use each for what it does best.
Last updated July 2026. n8n is a trademark of its respective owner. WaBulkSend is built on Meta's official WhatsApp Cloud API and is not affiliated with n8n or Meta Platforms, Inc.
How the WhatsApp Business Cloud node in n8n works
n8n is a workflow automation platform you can self-host or run on n8n Cloud. You build "workflows," visual graphs where a trigger sets off a chain of nodes. The WhatsApp Business Cloud node is n8n's official connector to Meta's Cloud API, so WhatsApp becomes a node you can drop into any workflow. Connect it once with a WhatsApp API credential (your access token and Business Account ID), and add a phone number ID when you send. Because n8n is open source and can run on your own server, the message data and tokens stay on infrastructure you control, which is the main reason technical teams pick it over a hosted-only tool.
There are two pieces: the WhatsApp Business Cloud node for actions, and the WhatsApp Trigger node for reacting to events. Together they cover both directions of a conversation:
| Node or operation | Type | What it does |
|---|---|---|
| WhatsApp Trigger | Trigger | Fires the workflow on account, message, and phone number events, so a new incoming message or a status change starts your flow. |
| Message: Send (template) | Action | Sends an approved template. This is how you start a new conversation, since only templates can open the window. |
| Message: Send (text) | Action | Sends a free-form text message, allowed only inside the 24-hour window after the customer last messaged you. |
| Message: Send and Wait for Response | Action | Sends a message and pauses the workflow until the person replies or confirms, useful for approvals and simple two-way flows. |
| Media: Upload / Download / Delete | Action | Handles images, documents, and other media you attach to a message or pull from an incoming one. |
| HTTP Request node | Action | A raw call to graph.facebook.com for anything the prebuilt operations do not cover. |
The 24-hour window rule is built into which operation you can use. To message someone who has not written to you, send a template. Only after they reply can you send free-form text, and only for the next 24 hours. This is Meta's rule, and it is the same in every tool built on the Cloud API, n8n included.
Connect WhatsApp to n8n in four steps
You need a WhatsApp Business Account on Meta's Cloud API before you start.
Set up the Cloud API
Register your number on the WhatsApp Business Platform and get your access token, Business Account ID, and phone number ID from Meta.
Add the credential
In n8n, create a WhatsApp API credential with your access token and Business Account ID. It is reused by the node and the trigger.
Pick a trigger
Start the workflow from any node: a webhook, a schedule, a database change, a form, or the WhatsApp Trigger for incoming messages.
Add the send node
Drop in the WhatsApp Business Cloud node, choose Send, map your template fields, and run. Add the WhatsApp Trigger to catch replies.
What you can automate with n8n and WhatsApp
n8n shines at triggered, one-at-a-time messages with logic, code, and AI in between.
Order and shipping updates
Fire a utility template when a webhook from your store reports an order paid or shipped, with fields mapped from the payload.
Appointment reminders
Send a reminder template a day before, triggered by a schedule node reading your booking database.
Lead notifications
When a form or ad lead lands, message the lead and alert your sales rep in the same workflow.
AI agent replies
Route an incoming message through an LLM node to draft a reply, then send it inside the 24-hour window.
Reply routing
Catch replies with the WhatsApp Trigger and log them to a CRM, database, or help desk with branching logic.
Two-way OTP and approvals
Send an authentication code or an approval prompt and process the response with Send and Wait for Response.
n8n vs a dedicated WhatsApp bulk sender
They solve different problems. Use both, or pick by the job in front of you.
| Job | n8n | Dedicated bulk sender |
|---|---|---|
| Event-driven single messages | Excellent, this is its core job | Possible, but overkill for one-off triggers |
| Send a campaign to a whole list | Awkward: you loop over items with no audience concept | Built for it: upload a list and send one template to all |
| Contact and audience management | None, you bring your own data source | Segments, tags, and opt-in status included |
| Template management | You reference a template by name; no editor | Create, submit, and track templates in-app |
| Campaign analytics | Only what you log yourself | Delivery, read, and reply rates per campaign |
| Custom logic, code, and AI steps | Excellent, code nodes and LLM nodes built in | Limited to the app's own features |
| Self-hosting and data control | Yes, run it on your own server | Hosted service |
The clean split: use n8n for automation that reacts to events in your other tools and needs custom logic, and use a dedicated WhatsApp bulk sender when you need to send one message to an audience and see who received it. Many teams run both on the same number. If you want a no-code trigger without hosting anything, Make connects to WhatsApp and so does Zapier, the same way.
One rule that applies no matter the tool
Whether you send through n8n, a bulk sender, or the raw API, marketing-category templates do not reach US phone numbers. Meta stopped delivering them on April 1, 2025, and they fail with error 131049, with no resume date as of July 2026. This is a Meta policy, not an n8n limitation.
Utility templates, authentication templates, and replies inside the 24-hour window still reach US numbers, so the order updates, reminders, and OTP flows above all work. Just keep US promotional blasts off WhatsApp for now. The bulk messaging rules page covers what is allowed in full.
n8n WhatsApp integration: common questions
Does n8n integrate with WhatsApp? +
Yes. n8n has a built-in WhatsApp Business Cloud node and a separate WhatsApp Trigger node, both maintained by n8n and both connecting to Meta's Cloud API. Add a WhatsApp API credential with your access token and Business Account ID, then send template, text, and media messages from the node and react to incoming messages with the trigger.
Can n8n send bulk WhatsApp campaigns? +
Not really. n8n sends messages one workflow run at a time and has no audience, template manager, or campaign analytics. You can loop over a list of items to message many people, but it is clumsy and gives you no delivery reporting. For sending one approved template to a whole audience and tracking who received it, a dedicated WhatsApp bulk sender is the better tool. Many teams use n8n for triggers and a bulk sender for campaigns.
How do I connect WhatsApp to n8n? +
First set up a WhatsApp Business Account on Meta's Cloud API and get your access token, Business Account ID, and phone number ID. In n8n, create a WhatsApp API credential with the token and Business Account ID. Then pick a trigger, add the WhatsApp Business Cloud node, choose the Send operation, map your template fields, and run the workflow. Add the WhatsApp Trigger node to catch replies.
Is the n8n WhatsApp node free? +
The node itself is part of n8n, which is open source and free to self-host, or available on paid n8n Cloud plans. Meta still bills you per delivered template message on your own WhatsApp Business account, by category and country, whichever tool you send through. So n8n adds no per-message fee, but Meta's message charges still apply.
Can I build a WhatsApp AI agent in n8n? +
Yes. A common pattern is to catch an incoming message with the WhatsApp Trigger, pass it to an LLM or AI agent node to draft a reply, then send that reply with the WhatsApp Business Cloud node. Just remember free-form replies only work inside the 24-hour window; outside it you must send an approved template.
Does n8n let me send WhatsApp marketing to US numbers? +
No tool does. Since April 1, 2025 Meta has not delivered marketing-category templates to US phone numbers, and they fail with error 131049 in n8n just as everywhere else. Utility and authentication templates, and replies inside the 24-hour window, do reach US numbers, so transactional automations still work.
Automate the triggers, campaign the rest
Use n8n for event-driven messages and custom logic, and WaBulkSend when you need to send one approved template to a whole audience and track every delivery. Both run on Meta's official Cloud API. Free for your first 500 messages a month, no card required.
Start Free