How to Connect WhatsApp to n8n, Link, Use & Trigger it Easily 2026

From your n8n Overview screen, click Create workflow to open a blank canvas. Two options sit in the center of the empty editor: Add first step manually, or let n8n's Build with AI assistant scaffold something for you. For a WhatsApp integration where you want full control over credentials and trigger behavior, adding the first step manually is the more predictable route.

Click Add first step and type "whatsapp" into the trigger search. n8n surfaces the official WhatsApp Business Cloud trigger at the top of the list, followed by community-built alternatives, Z-API, SyncMate, AllSign, YCloud, Hyperflow, GREEN-API, and others, each with its own setup and pricing outside of n8n. Unless you have a specific reason to use one of the third-party options, the official WhatsApp Business Cloud node is the one to pick, since it talks directly to Meta's API instead of through an intermediary service.

Once it's on the canvas, open the WhatsApp Trigger node's parameters. Trigger On defaults to Messages, which fires the workflow whenever a new inbound chat arrives; n8n also lists nine other event types here (Account Update, Account Review Update, Business Capability Update, Message Template Status Update, Message Template Quality Update, Phone Number Name Update, Phone Number Quality Update, Security, and Template Category Update), useful for reacting to template approvals or account changes instead of chat messages. The node also flags a real constraint: WhatsApp only allows one registered webhook per connected Meta app. n8n's own docs note that activating a test workflow and a production workflow on the same app overwrites each other's webhook registration, so plan for one trigger per app instead of discovering the conflict mid-build.

Click Set up credential to open the WhatsApp OAuth account dialog. This trigger credential needs a Client ID and Client Secret, not a simple API key: both come from your Meta app's App settings > Basic page, where the App ID becomes the Client ID and the App Secret becomes the Client Secret.

That app needs to already exist and be configured on Meta's side before this step will work. Enterprise-plan users can pull these from an external vault instead of pasting them directly.

With the trigger catching inbound messages, add a separate WhatsApp Business Cloud node further down the canvas to send messages back out, either a pre-approved template for the first contact with a customer, or a free-text reply within the window Meta allows after they've messaged you. This node takes a different credential type from the trigger: an API Key built from an Access Token and a Business Account ID, generated in the Meta app under WhatsApp > API Setup > Generate access token.

That's not the Client ID and Secret the trigger uses, so the two credentials can't be swapped for each other. Map dynamic fields, like a customer's name or order number, into the message body so replies read as personal instead of canned.

Save the workflow, activate it, and send a test message from your own phone to the connected WhatsApp Business number. Confirm the trigger fires with the data you expect, then confirm any outbound message arrives. Because production and test workflows fight over the same webhook, n8n suggests unpublishing the production workflow while you test with the test webhook URL, then republishing once you're done, instead of running both at once.