To integrate n8n with WhatsApp, first configure the required Meta business assets, then create WhatsApp Business Cloud credentials in n8n. Use the WhatsApp Trigger for inbound messages and account events, and the WhatsApp Business Cloud node for replies, templates, and media.
Antihost offers VPS plans with one-click n8n, NVMe storage and a 14-day free trial.
The most common setup failures are caused by registering the wrong webhook URL, leaving test and production workflows active at the same time, using the wrong credential method, or sending template parameters in the wrong order or type.
As an Amazon Associate I earn from qualifying purchases.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWhat the n8n–WhatsApp integration does
n8n connects WhatsApp Business Cloud events to visual workflows. A WhatsApp message or account event enters through a trigger, n8n can filter it, look up data, call another service, run business logic, and then send a response through the WhatsApp Business Cloud node.
The connection is not created by n8n alone. You need Meta’s developer and business assets, a WhatsApp-enabled business app, and credentials that n8n can use. Once those are ready, the integration has two distinct parts:
- Inbound automation: the WhatsApp Trigger receives messages and supported account-level notifications.
- Outbound automation: the WhatsApp Business Cloud node sends messages, templates, and media, or waits for a response.
Prerequisites in Meta
Prepare these items before opening n8n:
- A Meta developer account.
- A Meta business portfolio.
- A Meta business app configured with WhatsApp.
- A WhatsApp Business Account (WABA) associated with that app.
- A privacy-policy URL and terms URL for the app configuration.
- An access token and the WhatsApp Business Account ID for API-key authentication, or the Meta App ID and App Secret for the WhatsApp Trigger’s OAuth2 authentication.
The exact labels can change as Meta updates its developer console, but the required sequence is to create or select the app, add WhatsApp, select the business portfolio, provide the privacy-policy and terms URLs, and switch the app to Live when the integration is ready for real traffic.
Configure the Meta app step by step
1. Create or select the developer account and portfolio
- Sign in to the Meta developer area with the account that owns or administers the business assets.
- Create a business portfolio or select the existing portfolio that should own the WhatsApp Business Account.
- Create a business app and choose WhatsApp during app setup.
- Enter the privacy-policy and terms URLs requested by the app settings.
2. Add and configure WhatsApp
Complete the WhatsApp product setup inside the app. Confirm that the phone number and WABA you intend to automate belong to the selected business portfolio. Keep the app in development mode while building if your Meta account requires that for testing; switch it to Live when you are ready to handle production traffic.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
3. Record the values n8n needs
For API-key authentication, open Meta’s WhatsApp API Setup area, generate an access token, and copy the WhatsApp Business Account ID. Store both values securely; you will enter them in an n8n credential.
For OAuth2 authentication used by the WhatsApp Trigger, copy the Meta App ID and App Secret. In n8n, the App ID becomes the OAuth2 client ID and the App Secret becomes the client secret.
Create WhatsApp credentials in n8n
In n8n, add the credential type used by the node you plan to configure. Do not assume that one authentication method replaces the other: outbound actions and the trigger expose different credential choices.
| n8n use | Credential values | Best fit | Important detail |
|---|---|---|---|
| WhatsApp Business Cloud actions | Meta access token and WhatsApp Business Account ID | API-key authentication | Generate the token in Meta’s WhatsApp API Setup area and copy the WABA ID exactly. |
| WhatsApp Trigger | Meta App ID and App Secret | OAuth2 authentication | Use the App ID as client ID and App Secret as client secret. |
API-key credential for outbound operations
- In n8n, open Credentials and create the WhatsApp Business Cloud credential.
- Paste the access token generated in Meta’s WhatsApp API Setup area.
- Paste the WhatsApp Business Account ID.
- Save the credential and select it later in each WhatsApp Business Cloud node.
OAuth2 credential for the trigger
- Create or select the OAuth2 credential required by the WhatsApp Trigger.
- Enter the Meta App ID as the client ID.
- Enter the Meta App Secret as the client secret.
- Complete n8n’s authorization flow and confirm that Meta grants the requested access.
If a trigger credential authorizes successfully but no events arrive, check the app subscription and webhook URL separately. Authentication and event delivery are different configuration layers.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Receive WhatsApp messages with the WhatsApp Trigger
1. Add the trigger
- Create a new n8n workflow.
- Add the WhatsApp Trigger node.
- Select the OAuth2 credential you configured.
- Choose the event family you need.
The trigger documents these event families:
- Account review and account updates.
- Business capability updates.
- Message-template quality and status updates.
- Messages.
- Phone-number name and quality updates.
- Security events.
- Template-category updates.
For a chatbot or support workflow, select the message event. For operational monitoring, choose the account, capability, phone-number, security, or template event that matches the process you want to automate.
2. Subscribe the app under the WhatsApp Business Account
Inbound account webhooks require the app to be subscribed under the relevant WhatsApp Business Account. An app that has merely been created or authenticated is not necessarily subscribed for notifications.
There is also an important restriction in the documentation: apps shared with a business cannot receive those webhook notifications. If the app is shared rather than owned in the required relationship, move the configuration to an app that can receive the WABA subscription events.
3. Add business logic after the trigger
Place the processing nodes after the trigger. Typical steps include:
- Filtering by message type, sender, or event field.
- Looking up a customer or order in a database.
- Calling an external service with an HTTP Request node.
- Running an AI or classification step.
- Formatting a response or selecting a template.
Keep the inbound portion separate from outbound formatting where possible. That makes it easier to inspect the original event and replace the reply logic without changing the webhook entry point.
Send replies and templates with WhatsApp Business Cloud
Send a normal message
- Add a WhatsApp Business Cloud node after the trigger or processing step.
- Select the Send operation.
- Choose the outbound credential.
- Map the recipient and message content from the trigger data or a field created by your workflow.
- Execute the node and inspect the returned message identifier and response payload.
Log the message ID and the returned payload during testing. Those values give you a concrete reference when a send appears successful in n8n but a downstream process reports a problem.
Use “Send and Wait for Response”
The WhatsApp Business Cloud node includes Send and Wait for Response. Use it when a workflow should pause after sending a message and continue only after the recipient responds. This is useful for a confirmation, a choice between options, or a short data-collection step. Design the workflow so that a missing or late response has an explicit handling path rather than leaving the process without a visible outcome.
Send an approved template
- Add the WhatsApp Business Cloud node.
- Select Send Template.
- Select the template configured for the WhatsApp Business Account.
- Map every parameter in the exact order expected by that template.
- Ensure each expression resolves to a value of the data type the template expects.
- Execute a controlled test before publishing the workflow.
Template sends can return a bad-request response when n8n values do not match the template’s parameter order or types. A template that expects a text value in parameter one will not accept a differently typed or misplaced value merely because the expression itself is syntactically valid.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →When input data is optional or inconsistent, insert a Set or Edit Fields step before the send. Use that step to create correctly formatted fallback values and to make the final parameter mapping obvious.
Work with images, audio, and documents
The WhatsApp Business Cloud node supports non-text media, including images, audio, and documents. Media workflows require an n8n input-data field that contains the binary file.
Map the binary field correctly
- Obtain or create the binary data in an earlier node.
- Confirm the exact input-data field name shown by the previous node.
- In the media operation, enter the field name itself, such as
data. - Do not enter an expression that points into a nested object when the node is asking for the binary input field name.
- Execute the node and inspect the upload or send response.
For example, if the binary property is named data, enter data in the media configuration. Supplying a nested expression instead can leave the node unable to locate the file even though the workflow contains binary data.
Available media operations
The node documents Upload, Download, and Delete operations in addition to media-capable sending. Choose the operation based on where the file currently exists and whether the workflow needs to retain or remove the uploaded media.
Webhook testing: test URL versus production URL
WhatsApp permits one registered webhook URL per app. n8n’s test and production URLs are therefore mutually exclusive at the Meta app level: when you register one, WhatsApp overwrites the previously registered URL.
Safe testing sequence
- Unpublish the production workflow before testing a different workflow URL.
- Put the intended n8n workflow into test mode and register its test webhook URL with the Meta app.
- Send a controlled WhatsApp message or generate the selected account event.
- Confirm that the test workflow receives the event and that the outbound node returns the expected response.
- Stop the test run and remove the test URL from contention.
- Publish the production workflow and register or verify its production webhook URL.
If both a published workflow and a test workflow appear ready, only one receives events because Meta stores one active URL for the app. This explains the common symptom of a test execution that works once and then stops, or a production workflow that suddenly receives nothing after a test URL was registered.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Implementation routes and trade-offs
The same node capabilities can be used with different deployment and authentication choices. Select the route that matches your hosting and operational requirements.
| Decision | Option | What changes | When it fits |
|---|---|---|---|
| n8n hosting | Self-hosted n8n | You operate the n8n instance, workflow availability, and webhook reachability. | Teams that need control of the runtime and deployment. |
| n8n hosting | n8n Cloud | n8n hosts the workflow runtime; you still configure Meta assets and credentials. | Teams that prefer managed hosting. |
| Authentication | API key | Uses an access token and WABA ID for WhatsApp Business Cloud actions. | Outbound sends, templates, and media operations. |
| Authentication | OAuth2 | Uses the Meta App ID and App Secret in the trigger credential. | WhatsApp Trigger event subscriptions. |
| Message type | Plain text | Maps message content directly from workflow data. | Replies and notifications that do not require a template. |
| Message type | Template | Requires the correct template and ordered, correctly typed parameters. | Template-based messages governed by the WhatsApp Business Account. |
| Payload | Text only | No binary field mapping is required. | Simple conversational flows. |
| Payload | Media | Requires the correct n8n binary input field, such as data. |
Images, audio, and documents. |
A complete first workflow
This pattern receives an inbound message, performs a lookup, and sends a response:
Recommended Free Tools
- Configure the Meta app, WABA, token, and app credentials.
- Create the corresponding n8n credentials.
- Add a WhatsApp Trigger for the Messages event.
- Add a filter that keeps only the message types your process supports.
- Use a database lookup, HTTP Request, or AI step to determine the response.
- Add a Set or Edit Fields node to normalize the recipient and response values.
- Add WhatsApp Business Cloud with Send, Send Template, or a media operation.
- Log the incoming event identifier, outbound message ID, template result, and any error payload.
- Test while production is unpublished, then restore the production webhook and publish the workflow.
For a question-and-answer process, replace the final send operation with Send and Wait for Response, then add the next decision step after the response is received.
Troubleshoot the most common failures
The webhook does not fire
- Check that the Meta app has the intended n8n URL registered. A later test registration may have overwritten the production URL.
- Confirm that the workflow receiving the URL is the one currently published or in test mode.
- Verify that the WhatsApp Trigger uses the correct OAuth2 credential.
- Confirm that the app is subscribed under the relevant WhatsApp Business Account.
- Check whether the app is shared with a business; shared apps cannot receive the documented account webhook notifications.
A test workflow works but production does not
Registering the test URL replaces the production URL. Unpublish production while testing, then publish production and verify its URL again when testing is complete.
A template send returns a bad request
- Compare the n8n parameter order with the template definition.
- Check that each expression resolves to a valid value.
- Check the expected data type for every parameter.
- Insert a Set or Edit Fields node to provide normalized values or fallbacks.
- Confirm that the selected template belongs to the WhatsApp Business Account used by the credential.
A media message contains no file
- Inspect the previous node and confirm that binary data exists.
- Use the binary input field name itself, such as
data, in the media configuration. - Remove nested-object expressions from the field-name setting.
- Run the upload or send operation again and inspect its response payload.
The outbound node cannot authenticate
For WhatsApp Business Cloud actions, recheck the access token and WABA ID. For the WhatsApp Trigger, recheck the Meta App ID and App Secret in the OAuth2 credential. A valid trigger credential does not automatically supply the API-key values required by the outbound node.
Quick Recap
Operations and maintenance checklist
- Keep the access token, App Secret, and WABA ID in n8n credentials rather than hard-coding them in expressions.
- Use separate test and production workflows deliberately, remembering that Meta stores only one webhook URL per app.
- Record message IDs, template responses, and error payloads so failed sends can be traced.
- Review template quality and status events if your process depends on approved templates.
- Monitor phone-number name and quality events when sender identity or number quality affects delivery operations.
- Keep media mappings explicit and document the binary field name used by each workflow.
- Switch the Meta app to Live only when the business assets, credentials, webhook, and workflow have been verified for real traffic.
Final verification before publishing
- The Meta developer account, business portfolio, WhatsApp app, and WABA are associated correctly.
- The app has its privacy-policy and terms URLs and is Live when appropriate.
- The outbound n8n credential contains the access token and WABA ID.
- The trigger credential contains the Meta App ID and App Secret.
- The WhatsApp Trigger is subscribed to the intended event.
- The app is subscribed under the WABA for inbound account webhooks.
- Only the intended test or production webhook URL is registered.
- Template parameters match the configured order and data types.
- Media operations reference the actual binary field name.
- Logging captures message IDs, template responses, and errors.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
