A community node maintained by the 360Dialog team connects n8n to the WhatsApp Business API with automatic webhook registration, text, media, and template messaging, all from inside your workflows. The node handles the full webhook lifecycle: it registers a new URL on activation and restores the previous one when you deactivate it. That means no manual API calls to configure message routing. If you self-host n8n and want code-level control over your WhatsApp automation, this integration connects your workflows directly to a production WhatsApp number.
Key Takeaways
- A 360Dialog-maintained community node connects n8n to the WhatsApp Business API with automatic webhook registration and deregistration.
- The node is maintained by a 360Dialog team and licensed under MIT, giving you full visibility into the source code.
- Setup requires three steps: install the community node, add your 360Dialog API credential, and build a workflow with the trigger and action nodes.
- The trigger node filters outbound echo messages and deduplicates inbound messages within a 24-hour window, keeping 500 message IDs in memory.
- Delivery status updates are acknowledged but do not trigger workflows, so status-based routing requires a separate mechanism.
Why Connect WhatsApp to n8n?
n8n is an open-source, self-hostable workflow automation tool. Connecting WhatsApp to n8n means your messaging runs on infrastructure you own, with no vendor lock-in between your workflows and the WhatsApp Business API.
n8n does not include a native WhatsApp integration, but the 360Dialog community node wraps the API endpoints into n8n’s node format, so you can trigger workflows on inbound messages and send outbound messages as part of any automation chain. For teams already running n8n for CRM updates or data pipelines, adding WhatsApp means one fewer tool outside the stack.
What Does an n8n WhatsApp Integration Give You?
The integration provides two node types: a trigger node for inbound messages and an action node for outbound operations. Together they cover the core messaging loop, including sending text, media, and template messages, plus receiving and routing inbound conversations.[1]
Action Node Operations
The action node (Dialog360) supports four operations:
- Send Text: Sends a plain text message to a WhatsApp number.
- Send Media: Sends an image, video, document, or audio file via a public HTTPS URL.
- Send Template: Fetches your approved templates from the API in a live dropdown, then auto-generates input fields matching each template’s variable definitions.
- Get Health Status: Checks your WhatsApp Account (formerly WhatsApp Business Account, or WABA) health status directly from the workflow.
Trigger Node Behavior
The trigger node (Dialog360Trigger) manages the webhook configuration automatically:
- Auto-registration: On activation, the node sends a POST request to
/v1/configs/webhookto register its URL as the active webhook for your number.[2] - Restoration: On deactivation, it restores the previous webhook URL, so your other systems are not left disconnected.
- Outbound echo filtering: The node ignores messages sent by the account itself, preventing infinite loops in workflows that both send and receive.
- Deduplication: A 24-hour window with 500 message IDs in memory prevents duplicate processing of the same inbound message.
- Status updates: Delivery receipts (sent, delivered, read) are acknowledged with a 200 OK response but do not trigger the workflow.
If you need to route workflows based on delivery status, you will need to handle that outside the trigger node.
Should You Connect WhatsApp to n8n?
Connecting WhatsApp to n8n makes sense if you self-host n8n (or plan to), if your team includes developers comfortable reading TypeScript, and you want full visibility into how your WhatsApp messages are processed. The MIT license means you can inspect, fork, and modify every line of the node’s code.[1]
For non-technical teams who need a visual builder with pre-built templates, consider Zapier with the native 360Dialog app or explore the 360Dialog Marketplace.
What Is the Difference Between Automation and Live Chat?
Automation tools like n8n handle events and data flows: routing messages, updating databases, sending notifications, and triggering template sends based on conditions you define. They do not handle conversations. When a customer replies with a question that requires a human answer, automation alone leaves that message unread.
360Dialog solves this with a multi-webhook setup. Your n8n workflows and a team inbox can run on the same WhatsApp number simultaneously.[2] Automation handles the event-driven work, while your team handles live conversations in a shared inbox view. The two systems coexist because 360Dialog supports multiple webhook endpoints per number via the /multi_webhook API.
The core WhatsApp automation principle applies here: automate what is predictable, keep humans available for what is not.
How Do You Connect Your Account in 3 Steps?
Three steps: install the community node, add your 360Dialog credentials, and build your first workflow.
Step 1: Install the community node. In your n8n instance, go to Settings, then Community Nodes. Enter @pmartino/n8n-nodes-360dialog and install. The package adds two nodes (Dialog360 and Dialog360Trigger) and one credential type (Dialog360Api).
Step 2: Add your 360Dialog credential. Create a new credential of type Dialog360Api. Paste your API key in the credential form. This is the same key you use for direct API calls, with the header name D360-API-KEY.
Step 3: Build your workflow. Add a Dialog360Trigger node as the entry point for inbound messages. Connect it to an HTTP Request node for CRM updates, a Slack node for internal alerts, or a Dialog360 action node for automated replies. For outbound-only workflows, use the Dialog360 action node directly.
Caution: Activating the trigger node registers a new webhook URL with the 360Dialog API, replacing any existing webhook on that number. Deactivating restores the previous URL. Test this behavior in a non-production environment first. For concurrent webhook consumers on one number, use 360Dialog’s multi-webhook configuration via /multi_webhook.
To get started with your API key, get API access and install the community node in your n8n instance.
What Do People Automate With n8n and WhatsApp?
Four patterns appear frequently across n8n’s 400+ integrations.
Inbound message routing. Connect the Dialog360Trigger to a Switch node that routes messages by keyword, sender number, or message type. Support requests go to one branch, order inquiries to another.
CRM update on new conversation. Pull the sender’s number from the trigger payload, look it up in your CRM via HTTP Request, and update the contact record.
Automated template send on event. Use a webhook or schedule trigger to fire a Dialog360 Send Template action when an order ships, a payment arrives, or an appointment is confirmed.
Internal Slack notification. Connect the Dialog360Trigger to a Slack node. Every inbound WhatsApp message posts a formatted alert with the sender number and message text.
Want Your Team in One Shared View?
Automation handles the structured, event-driven side of WhatsApp messaging. Live conversations with customers who need a human response require a different tool. 360Dialog offers a team inbox that runs on the same WhatsApp number as your n8n workflows, with assignment, tagging, and multi-agent collaboration. Because 360Dialog supports multiple webhooks per number, your automated workflows and your team inbox receive messages simultaneously.
Why 360Dialog?
360Dialog is an Official Meta Solution Partner providing WhatsApp Business API infrastructure to over 100,000 businesses.[3] The platform offers transparent pricing with no markup on Meta fees, starting at €49 per month.[3] Support runs 24/7 in seven languages. The community node for n8n is maintained by the 360Dialog team.
For teams evaluating workflow automation with WhatsApp, the choice of API provider determines your ceiling. To connect your n8n instance to a production WhatsApp number, get API access and follow the three-step setup above.
Frequently Asked Questions
Is the n8n WhatsApp Node an Official n8n Integration?
The 360Dialog community node is installable through n8n’s Community Nodes settings. It follows n8n’s community node packaging format (using the n8n-community-node-package keyword on npm) and is maintained by the 360Dialog team under the MIT license.
Does the Trigger Node Handle Delivery Status Updates?
The trigger node acknowledges delivery status updates (sent, delivered, read) with a 200 OK response, but these events do not trigger the workflow. Only inbound messages activate the trigger. To act on delivery statuses, configure a separate webhook endpoint or polling mechanism outside this node.
What Happens to My Existing Webhook When I Activate the Node?
Activating the Dialog360Trigger node registers a new webhook URL with the 360Dialog API, replacing whatever URL was previously configured for that number. Deactivating restores the previous webhook URL. For multiple webhook consumers on the same number, 360Dialog supports multi-webhook configuration via the /multi_webhook endpoint.
Do I Need to Self-Host n8n to Use This Integration?
The community node can be installed on n8n Cloud instances that support community nodes. However, full control over data and execution aligns most closely with self-hosted deployments. Check n8n’s cloud plan documentation for community node support on your tier.
What Version of the 360Dialog API Does the Node Use?
The node communicates with the 360Dialog messaging API at https://waba-v2.360dialog.io/messages using the D360-API-KEY header for authentication. It uses the v1 webhook configuration endpoint at /v1/configs/webhook for automatic webhook registration. The 360Dialog messaging API version is 1.49.6 as of the latest documentation.
Sources
[1] npm registry, “@pmartino/n8n-nodes-360dialog,” version 0.3.0, https://registry.npmjs.org/@pmartino/n8n-nodes-360dialog. Accessed September 9, 2026.
[2] 360Dialog, “Webhooks API Reference,” https://docs.360dialog.com/docs/messaging-api/api-reference/webhooks. Accessed September 9, 2026.
[3] 360Dialog, “WhatsApp Business Platform Pricing,” https://360dialog.com/pricing. Accessed September 9, 2026.
