There are two ways to connect n8n to WhatsApp. The first is n8n’s built-in WhatsApp Business Cloud node and WhatsApp Trigger, which talk to Meta’s official WhatsApp Business Platform Cloud API. The second is a community node that talks to a WhatsApp gateway service such as WAHA, Evolution API, Z-API or Green API. This guide covers what the built-in nodes do and what they need (from n8n’s documentation), the most used community packages (from our own npm data), and how to choose.
Quick comparison
| Built-in WhatsApp nodes | WhatsApp community nodes | |
|---|---|---|
| Connects to | Meta’s WhatsApp Business Platform Cloud API | The gateway or service the package was written for (WAHA, Evolution API, Z-API, Green API, WhatsAble and others) |
| Comes with n8n | Yes, no install needed | No, installed as a community package |
| Accounts you need | Meta developer account, Meta business portfolio, Meta business app with WhatsApp | Whatever the gateway or service asks for (see the package’s README) |
| n8n Cloud | Available | Only packages that n8n has verified |
| Maintained by | n8n | The package author |
The built-in WhatsApp Business Cloud node
The WhatsApp Business Cloud node (n8n-nodes-base.whatsapp) supports these operations:
- Message: Send, Send and Wait for Response, Send Template
- Media: Upload, Download, Delete
n8n points to Meta’s Cloud API documentation for the details of each operation.
The built-in WhatsApp Trigger
The WhatsApp Trigger node starts a workflow when one of these events happens:
- Account Review Update
- Account Update
- Business Capability Update
- Message Template Quality Update
- Message Template Status Update
- Messages
- Phone Number Name Update
- Phone Number Quality Update
- Security
- Template Category Update
What you need before you start
According to n8n’s WhatsApp Business Cloud credentials page, you need three Meta assets:
- A Meta developer account, to create and manage Meta apps.
- A Meta business portfolio (formerly called a Business Manager account). WhatsApp messaging requires one.
- A Meta business app configured with WhatsApp. In the Meta for Developers Apps dashboard, create an app, select Set up on the WhatsApp tile, pick your business portfolio, set the Privacy Policy URL and Terms of Service URL under App settings > Basic, and change the App Mode to Live.
The two built-in nodes use different credential types.
API key credential (for the WhatsApp Business Cloud node)
You need an Access Token and a Business Account ID:
- Open the Meta for Developers Apps dashboard and select your app.
- In the left menu, go to WhatsApp > API Setup.
- Select Generate access token and confirm the access you want to grant.
- Copy the access token into n8n as the Access Token.
- Copy the WhatsApp Business Account ID into n8n as the Business Account ID.
OAuth2 credential (for the WhatsApp Trigger)
You need a Client ID and a Client Secret:
- In the Apps dashboard, select your app and go to App settings > Basic.
- Copy the App ID into n8n as the Client ID.
- Copy the App Secret into n8n as the Client Secret.
n8n notes that fully verifying and launching your app takes further configuration on Meta’s side, including Meta’s App Review process. Meta classifies people who create WhatsApp business apps as Tech Providers.
Common issues with the built-in nodes
“Bad request – please check your parameters”
WhatsApp rejected the request because of its parameters. n8n says this is common with the Send Template operation when the data doesn’t match the format of your message template. Check each template parameter’s data type and order, and check that every expression resolves to a valid value for every item. An Edit Fields (Set) node or a fallback value helps make sure each parameter has the right format.
Sending images, audio or documents
When an operation has an Input Data Field Name or Property Name parameter, enter the field name itself, such as data, not an expression such as {{ $json.input.data }}.
The trigger only works in testing or only in production
WhatsApp allows only one webhook per app, so switching between the test URL and the production URL overwrites the registered webhook. n8n’s workaround is to unpublish the workflow while you test with the test URL, then publish it again. Note that this stops production traffic while the workflow is unpublished.
The workflow doesn’t run when messages arrive
Meta only sends WhatsApp webhooks to apps that are subscribed to your WhatsApp Business Account (WABA). Publishing a workflow with a WhatsApp Trigger registers your webhook URL on your Meta app, but it doesn’t subscribe the app to your WABA. Messages then never reach n8n, and n8n shows no failed execution. A test event from the Meta App Dashboard can still arrive, so a passing test doesn’t rule this out. n8n’s documentation walks through checking the subscription with a GET request to /<business-account-id>/subscribed_apps and fixing it with a POST to the same endpoint. It also warns: don’t send a DELETE to subscribed_apps to clear an “already has a webhook subscription” error, because that unsubscribes your app and Meta stops sending webhooks for that account.
WhatsApp community nodes
Community nodes for WhatsApp mostly connect to a gateway or messaging service instead of Meta’s API directly. Our WhatsApp hub lists 77 packages that pass our quality rule, with 65,307 npm downloads a week between them. Evolution API has its own hub with 21 packages and 1,747,798 weekly downloads, most of them for n8n-nodes-evolution-api.
The most downloaded packages on the WhatsApp hub, with the description each author gives on npm (weekly npm downloads as of 27 October 2026):
| Package | Weekly downloads | Author’s description |
|---|---|---|
| @devlikeapro/n8n-nodes-waha | 57,719 | n8n to connect with WAHA (Whatsapp HTTP API) |
| n8n-nodes-whatsable | 1,804 | WhatsAble, a platform for automating WhatsApp messages |
| n8n-nodes-repliz | 970 | Repliz API: accounts, comments, chats, content, schedules |
| n8n-nodes-quepasa | 527 | Quepasa (for Quepasa v4 and later) |
| @z-api/n8n-nodes-zapi | 480 | Z-API (WhatsApp messaging) |
| n8n-nodes-sendseven | 432 | SendSeven: WhatsApp Business API, SMS, Telegram, Messenger, Instagram and email |
| n8n-nodes-wafly | 308 | Wafly WhatsApp Bridge API: messages, groups, webhooks |
| @1msg/n8n-nodes-1msg | 198 | The official WhatsApp API through 1MSG |
| @green-api/n8n-nodes-whatsapp-greenapi | 117 | Green-API for WhatsApp |
Each package needs an account or a running instance of the service it was built for. Read the package’s README for its setup steps, and check its node page here for the latest version and release date, and, where it has one, its GitHub repository for open issues. For Evolution API packages, see Best n8n Community Nodes for Evolution API (WhatsApp).
Built-in or community node: how to choose
- Use the built-in nodes if you want Meta’s official API, you can set up a Meta business app, and you want something that n8n maintains and that works on n8n Cloud.
- Use a community node if you already run or pay for a WhatsApp gateway or service, such as WAHA, Evolution API, Z-API or Green API, and want n8n to work with it. You need to install the package yourself.
- On n8n Cloud, you can only install community nodes that n8n has verified. See Verified vs Unverified n8n Community Nodes.
Installing a WhatsApp community node
On a self-hosted n8n instance, an owner or admin can install a package from Settings > Community Nodes by entering its npm package name, for example @devlikeapro/n8n-nodes-waha. The full steps, including installing from the nodes panel, with npm, and in Docker, are in How to Install n8n Community Nodes. If you are new to community nodes, start with What Are n8n Community Nodes?
FAQ
Does n8n have a built-in WhatsApp node?
Yes. The WhatsApp Business Cloud node sends messages and templates and handles media, and the WhatsApp Trigger starts workflows on WhatsApp events. Both use Meta’s WhatsApp Business Platform Cloud API.
Which credentials does each built-in node use?
The WhatsApp Business Cloud node uses an API key credential (Access Token and Business Account ID). The WhatsApp Trigger uses an OAuth2 credential (Client ID and Client Secret, which are your Meta app’s App ID and App Secret).
Why doesn’t my WhatsApp Trigger fire?
The two most common reasons in n8n’s documentation are a webhook overwritten by switching between the test and production URLs, and a Meta app that isn’t subscribed to your WhatsApp Business Account.
What is the most used WhatsApp community node?
On our WhatsApp hub it is @devlikeapro/n8n-nodes-waha with 57,719 weekly npm downloads. Across WhatsApp gateways overall, n8n-nodes-evolution-api has the most, with 1,727,548 a week.
