Connect n8n with WhatsApp Business API: Step-by-Step 2026

Everyone searches for "connect n8n with WhatsApp" and then gets lost in the Meta for Developers maze. Connecting n8n with the WhatsApp Business API takes four steps: create an app in Meta for Developers with the WhatsApp product, get the Phone Number ID and a permanent token (via a System User), load those credentials into n8n's WhatsApp Business Cloud node, and set up the WhatsApp Trigger as the webhook in Meta to receive messages. n8n ships native nodes for both directions, so you don't need to write code or run a middleware server. This is the real 2026 walkthrough, including the exact spots where everyone gets stuck: the token that expires, the webhook that won't verify, and the 24-hour window.

What you need before you start

Don't dive into Meta for Developers without these ready, or you'll quit halfway:

1. A verified (or verifiable) Facebook Business account (Meta Business Suite).
2. A phone number that is NOT in use on the regular WhatsApp app or WhatsApp Business. It can be a virtual number or a physical one you'll "migrate."
3. An n8n instance with a public HTTPS URL. n8n Cloud includes it; if you self-host, you need a domain with SSL. If you don't have n8n running yet, sort out self-hosting with Docker first or get n8n Cloud.
4. 30-45 minutes the first time. The second integration takes 10.

Important: always use Meta's official Cloud API, never the unofficial solutions that emulate WhatsApp Web. Meta bans those numbers without warning or support, and losing a years-old business line is unrecoverable.

Step 1: Create the app in Meta for Developers

Go to developers.facebook.com, log in, and open My Apps → Create App. Choose the Business type. Give it an internal name (the customer never sees it) and link it to your Meta Business account.

Once created, find Add products in the dashboard and pick WhatsApp → Set up. This automatically gives you:

• A Meta test number (to test without your real number).
• A Phone Number ID and a WhatsApp Business Account ID (WABA ID).
• A temporary access token that lasts 24 hours (this is the one that will betray you later).

Save the Phone Number ID handy: you'll need it in n8n.

Step 2: The permanent token (where everyone gets stuck)

The test token expires every 24 hours. If you use it in production, your workflow "mysteriously stops working" every single day. The fix is a permanent token via a System User:

1. Go to Meta Business Settings (business.facebook.com/settings).
2. Users → System users → Add. Create an Admin-type user.
3. Assign your WhatsApp app to it with full control.
4. Click Generate new token, select the app, and check the whatsapp_business_messaging and whatsapp_business_management permissions.
5. Copy that token and store it safely: it won't be shown again and it never expires.

This is the only token you should ever use in production n8n.

Step 3: Load the credentials into n8n

In n8n, create a new credential of type WhatsApp API (or WhatsApp Business Cloud, depending on the version):

Field	Where it comes from
Access Token	The permanent System User token (Step 2)
Business Account ID	The WABA ID from the WhatsApp dashboard in Meta

Then add the WhatsApp Business Cloud node to your workflow. For a quick test:

• Resource: Message → Operation: Send
• Phone Number ID: the one from Step 1
• To: your personal number (international format, e.g. 5491155551234)
• Message Type: Text → write "Hello from n8n"

Run the node. If the message lands on your WhatsApp, half the work is done: you can already send. Now to receive.

Stuck on the permanent token or a webhook that won't verify? We'll set it up with you in one session and leave the first workflow running. Book an intro call and skip the two hours of trial and error.

Step 4: Receive messages with the WhatsApp Trigger

For n8n to react to inbound messages you need the WhatsApp Trigger node. When you add it, n8n generates a webhook URL and a Verify Token (a string you make up).

Now go back to Meta for Developers:

1. In the WhatsApp dashboard → Configuration → Webhook → Edit.
2. Paste the Callback URL that n8n's WhatsApp Trigger gave you.
3. Paste the Verify Token (it must match the one in n8n exactly).
4. Meta makes a verification call: if your n8n is public over HTTPS, it returns OK and shows Verified.
5. Under Webhook fields, subscribe to the messages field.

This is where people on localhost fail: Meta can't reach a local URL. You need a public domain with valid SSL, or a tunnel like ngrok for testing. For production, a VPS running your n8n instance is the right call.

Test it: send a WhatsApp to the test number (or your production number). The WhatsApp Trigger should fire in n8n with the inbound message JSON. You now have both directions working.

Your first useful workflow: auto-reply + lead into CRM

Sending and receiving is the foundation. The value shows up when you connect them. A minimal, profitable workflow:

1. WhatsApp Trigger receives the message.
2. An IF / Switch node classifies it: pricing question, support, or a new lead?
3. An HTTP Request node (or your CRM node) creates/updates the contact with the conversation.
4. A WhatsApp Business Cloud node replies inside the 24-hour window (no template cost).

This pattern is the base of any AI WhatsApp chatbot: you swap the IF for a model node (GPT, Claude) that understands intent and replies in natural language using your business data. If you also want it to trigger actions —book, quote, generate an invoice— that's where a custom AI automation comes in.

The golden rule: the 24-hour window

This defines what you can do and what it costs:

Situation	Allowed?	Cost
Customer messages you and you reply (within 24h)	Yes, free	Free or a service conversation
You start a new conversation (outside 24h)	Only with an approved template	Marketing/utility conversation
Unsolicited bulk messages	No	Ban risk

Translation: replying is always fine; initiating requires an approved template and consent. Breaking this rule is the number-one cause of legitimate bans.

When connecting n8n to WhatsApp does NOT make sense

Let's be honest: it isn't always worth it.

• Tiny volume. If you get 5 messages a day and answer them yourself in 2 minutes, setting up Meta for Developers + webhook + workflow is over-engineering. Use WhatsApp Business by hand.
• You only need simple notifications (e.g. "your order shipped"). Many e-commerce platforms already have native integrations; check before building ecommerce automations from scratch.
• No one will maintain the instance. Self-hosted n8n needs updates, backups and webhook monitoring. If nobody will look after it, n8n Cloud or a managed service keeps your replies from dying the day the SSL expires.
• Your case needs complex, multichannel logic (WhatsApp + web + app + payments with states). Here n8n can fall short and a custom software build with WhatsApp as one channel makes more sense.

The practical rule: if automating saves you several hours a week or lets you reply faster than the competition, it's worth it. If it's a technical vanity project for 5 daily messages, it isn't.

In short

Connecting n8n to the WhatsApp Business API is four steps: app in Meta for Developers, permanent token via System User, credentials + send node in n8n, and the WhatsApp Trigger as webhook. The three spots where everyone gets stuck are the 24-hour token, the webhook that won't verify without public HTTPS, and the 24-hour window for free replies. Solve those and you have a solid base for auto-replies, leads into your CRM, and AI chatbots.

Want your WhatsApp replying on its own, wired to your CRM, with a chatbot that actually understands your customers? At Deepyze we build the full integration on the official API with the right practices so your number never gets banned. Start your project with us and have your first production workflow running within a week.