Free tools Windows power users keep installed
One-click scans. No signup required.
To integrate n8n with WhatsApp, create and configure the required Meta business assets, add WhatsApp Business Cloud credentials in n8n, use a WhatsApp Trigger for inbound events, and use the WhatsApp Business Cloud node for replies, templates, and media. The most common failures come from an unregistered or overwritten webhook, an app that is not subscribed to the WhatsApp Business Account, or template and media fields that do not match what WhatsApp expects.
Antihost offers VPS plans with one-click n8n, NVMe storage and a 14-day free trial.
This guide walks through the setup from Meta configuration to a production workflow, including authentication choices, testing behavior, template validation, media mapping, and troubleshooting.
As an Amazon Associate I earn from qualifying purchases.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →What the n8n–WhatsApp integration does
The integration connects WhatsApp Business events to n8n workflows. A message or account event enters n8n through the WhatsApp Trigger. Your workflow can then filter the event, look up data, call an HTTP endpoint, run an AI or business-logic step, and send a result through the WhatsApp Business Cloud node.
There are two distinct directions:
- Inbound: WhatsApp sends webhook events to the WhatsApp Trigger.
- Outbound: n8n calls WhatsApp Business Cloud to send text, send an approved template, or upload, download, or delete media.
n8n does not create the WhatsApp Business connection by itself. You need a Meta developer account, a Meta business portfolio, and a Meta business app with WhatsApp configured before n8n can authenticate.
#1 Best Overall
- YOUR CONTENT, SUPER SMOOTH: The ultra-clear 6.7" FHD+ Super AMOLED display of Galaxy A17 5G helps bring your content to life, whether you're scrolling through recipes or video chatting with loved ones.¹
- LIVE FAST. CHARGE FASTER: Focus more on the moment and less on your battery percentage with Galaxy A17 5G. Super Fast Charging powers up your battery so you can get back to life sooner.²
- MEMORIES MADE PICTURE PERFECT: Capture every angle in stunning clarity, from wide family photos to close-ups of friends, with the triple-lens camera on Galaxy A17 5G.
- NEED MORE STORAGE? WE HAVE YOU COVERED: With an improved 2TB of expandable storage, Galaxy A17 5G makes it easy to keep cherished photos, videos and important files readily accessible whenever you need them.³
- BUILT TO LAST: With an improved IP54 rating, Galaxy A17 5G is even more durable than before.⁴ It’s built to resist splashes and dust and comes with a stronger yet slimmer Gorilla Glass Victus front and Glass Fiber Reinforced Polymer back.
Prerequisites and Meta setup
Create the required Meta assets
The official n8n credential setup sequence starts in Meta’s developer tools. Complete these steps before creating credentials in n8n:
- Sign in to or create a Meta developer account.
- Create or select a Meta business portfolio.
- Create a business app and add WhatsApp as a product.
- When Meta asks for company information, provide working privacy-policy and terms URLs.
- Choose the correct business portfolio when prompted so the app is associated with the WhatsApp Business Account you intend to automate.
- Keep the app in development while configuring and testing. Switch it to Live when the production setup is ready and your access requirements are satisfied.
Use the same business portfolio and WhatsApp Business Account throughout the setup. Mixing an app from one portfolio with a phone number or account from another is a common source of confusing authentication and subscription errors.
Collect the identifiers and token n8n needs
In Meta’s WhatsApp API Setup area, generate an access token for API-key authentication and copy the WhatsApp Business Account ID. Keep the values in a password manager; they are credentials, not ordinary workflow data.
For an OAuth2-based WhatsApp Trigger, also record the Meta App ID and App Secret. The App ID becomes the OAuth2 client ID in n8n, and the App Secret becomes the client secret.
| Value | Where it is used | Why it matters |
|---|---|---|
| Access token | WhatsApp Business Cloud API-key credential | Authorizes outbound WhatsApp API operations. |
| WhatsApp Business Account ID | WhatsApp Business Cloud credential | Identifies the business account whose phone numbers, templates, and media are used. |
| Meta App ID | WhatsApp Trigger OAuth2 client ID | Identifies the Meta app during trigger authorization. |
| App Secret | WhatsApp Trigger OAuth2 client secret | Proves that the OAuth2 request belongs to your Meta app. |
Add WhatsApp credentials in n8n
n8n uses different credential patterns for outbound actions and the trigger. Decide which direction you are configuring instead of assuming one credential works for every node.
API-key authentication for outbound actions
- In n8n, open Credentials and choose the credential type for WhatsApp Business Cloud.
- Paste the Meta access token into the API-key or access-token field.
- Enter the WhatsApp Business Account ID exactly as shown in Meta.
- Save the credential and select it in a WhatsApp Business Cloud node.
This credential is the usual choice for sending messages, sending templates, and performing media operations.
Recommended Free Tools
Rank #2
- Carrier: This phone is locked to Tracfone, which means this device can only be used on the Tracfone wireless network. Tracfone plan required, activating is easy, just 3 steps.
- DISPLAY: Immersive viewing on a 6.7-inch super-bright 120Hz display with powerful stereo speakers and Bass Boost for cinematic entertainment.
- CAMERA SYSTEM: Advanced 50MP Quad Pixel camera captures sharp, detailed photos and videos in any lighting condition
- PERFORMANCE: Lightning-fast 5G connectivity paired with a powerful processor and RAM Boost for smooth multitasking.
- BATTERY LIFE: Long-lasting 5000mAh battery with TurboPower charging technology delivers hours of power in minutes.
OAuth2 authentication for the WhatsApp Trigger
- Create or open a WhatsApp Trigger node.
- Select its OAuth2 authentication option and create a new credential.
- Set the OAuth2 client ID to the Meta App ID.
- Set the OAuth2 client secret to the Meta App Secret.
- Complete the authorization flow and grant the requested WhatsApp permissions.
Keep the two credential types clearly named, for example “WhatsApp outbound” and “WhatsApp trigger,” so a later workflow edit does not accidentally use the wrong authentication method.
Receive WhatsApp events with WhatsApp Trigger
Add a WhatsApp Trigger as the first node when a workflow should start from WhatsApp. The trigger exposes several event families, not just messages:
- Account review and account updates
- Business capability updates
- Message-template quality and status updates
- Incoming messages
- Phone-number name and quality updates
- Security events
- Template-category updates
For a conversational workflow, select the message event. For an operational workflow, choose the account, phone-number, security, or template event that matches the state change you need to monitor.
Subscribe the app to the WhatsApp Business Account
Creating a trigger node is not enough. The Meta app must be subscribed under the relevant WhatsApp Business Account so that inbound notifications are delivered. Meta’s documentation also warns that an app shared with a business cannot receive those WhatsApp webhook notifications. If events never arrive, verify both the subscription and the app-sharing status before changing n8n expressions.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Understand the one-webhook rule
WhatsApp permits only one registered webhook URL per Meta app. n8n exposes separate test and production webhook URLs, but registering one replaces the other at Meta. Therefore, a published workflow and a test workflow cannot receive events simultaneously when they use the same Meta app.
During testing, unpublish the production workflow, register or activate the test URL, and send a message. When testing is complete, stop the test listener, publish the production workflow, and verify that the production URL is the one registered in Meta. Treat the webhook URL as an app-wide setting, not a per-workflow setting.
Rank #3
- YOUR CONTENT, SUPER SMOOTH: The ultra-clear 6.7" FHD+ Super AMOLED display of Galaxy A17 5G helps bring your content to life, whether you're scrolling through recipes or video chatting with loved ones.¹
- LIVE FAST. CHARGE FASTER: Focus more on the moment and less on your battery percentage with Galaxy A17 5G. Super Fast Charging powers up your battery so you can get back to life sooner.²
- MEMORIES MADE PICTURE PERFECT: Capture every angle in stunning clarity, from wide family photos to close-ups of friends, with the triple-lens camera on Galaxy A17 5G.
- NEED MORE STORAGE? WE HAVE YOU COVERED: With an improved 2TB of expandable storage, Galaxy A17 5G makes it easy to keep cherished photos, videos and important files readily accessible whenever you need them.³
- BUILT TO LAST: With an improved IP54 rating, Galaxy A17 5G is even more durable than before.⁴ It’s built to resist splashes and dust and comes with a stronger yet slimmer Gorilla Glass Victus front and Glass Fiber Reinforced Polymer back.
Send messages and media with WhatsApp Business Cloud
Use a WhatsApp Business Cloud node after your business logic. The documented operations are:
| Operation | Use it for | Typical position in a workflow |
|---|---|---|
| Send | Sending a standard outbound message. | After a trigger, filter, lookup, or transformation. |
| Send and Wait for Response | Sending a message and pausing for a reply before continuing. | Interactive steps that require the recipient’s next response. |
| Send Template | Sending an approved WhatsApp template with parameters. | Structured notifications or messages that require template formatting. |
| Upload | Making media available through the WhatsApp API. | Before sending a file or image that is not yet uploaded. |
| Download | Retrieving media received from WhatsApp. | After an inbound message contains media. |
| Delete | Removing previously uploaded media. | Cleanup after the workflow no longer needs the file. |
These operations let one workflow receive a message, transform or route it, and send a reply or template. The node also supports non-text media, including images, audio, and documents.
Build a first inbound-to-outbound workflow
The following sequence is a reliable baseline for a support, notification, or chatbot workflow.
- Create a new workflow and add a WhatsApp Trigger.
- Choose the event that should start the workflow. Select the message event for incoming customer messages.
- Activate test listening in n8n and make sure the production workflow using the same app is unpublished.
- Send a test WhatsApp message and inspect the trigger output. Confirm that the event contains the sender and message data you expect before building expressions around it.
- Add business logic. Use filters to discard irrelevant events, a database lookup to retrieve customer context, an HTTP Request node to call another service, or an AI step to classify and draft a response.
- Add WhatsApp Business Cloud. Select the outbound credential and choose Send, Send and Wait for Response, Send Template, or a media operation.
- Map the recipient and content fields. Use the values from the trigger output for the destination and response text. For a template, map each parameter in the exact order defined by the template.
- Test the complete path with a controlled message. Inspect both the trigger data and the outbound node response, including any returned message identifier.
- Publish the workflow. Re-register or verify the production webhook URL in Meta after publishing, then send another message to confirm that production receives it.
Keep the workflow resilient
Put a filter immediately after the trigger when only certain messages should be processed. This prevents account updates or unrelated event types from reaching a node that expects message text. If a lookup or external API can fail, branch the workflow so the customer receives a useful fallback instead of an empty or malformed WhatsApp request.
Record the inbound event identifier, outbound message ID, selected template, and error payload in your normal logging system. These values let you distinguish a webhook-delivery problem from a rejected outbound request.
Template messages: parameter order and data types
Template sends are stricter than ordinary text sends. A bad-request response commonly means that the values supplied by n8n do not match the WhatsApp template definition.
Rank #4
- PRIVACY DISPLAY: Automatically hide your screen from those beside you. The built-in privacy display can be preset¹ to turn on when receiving notifications, typing passwords, or using specific apps
- TYPE IT IN. TRANSFORM IT FAST: Enhance any shot in seconds on your smartphone by using Photo Assist² with Galaxy AI.³ Add objects, restore details, or apply new styles by simply typing or tapping
- NIGHTS, CAPTURED CLEARLY: From gigs to city lights, record and capture moments after dark with clarity using Nightography so your photos and videos stay crisp and clear on your Samsung Galaxy
- MAKE IT. EDIT IT. SHARE IT: Turn everyday moments into something personal with creative tools built right into your mobile phone, whether it’s a special contact photo, custom wallpaper, an invitation or more⁴
- HELP THAT KEEPS UP: Stay in the moment while Now Nudge with Galaxy AI helps you respond faster and stay organized with smart suggestions⁵ that appear exactly when you need them on your phone
Validate every template parameter
- Open the exact template version and note the order of its variables.
- Map n8n expressions to that order; do not rely on the order in which fields happen to appear in a previous node.
- Ensure each expression resolves to a valid value at run time.
- Match the expected data type and formatting for every parameter.
- Test with real sample data rather than leaving a field undefined.
A Set or Edit Fields node is useful for creating correctly formatted fallback values before the Send Template node. It also makes the mapping visible and easier to debug than embedding many complex expressions directly in the template configuration.
Diagnose a rejected template request
- Read the complete error payload from the WhatsApp Business Cloud node.
- Compare the number and order of mapped parameters with the approved template.
- Check for an expression that resolves to an empty value, an object instead of text, or another unexpected type.
- Insert a Set or Edit Fields node, normalize the values there, and map those fields to the template.
- Run the workflow again and retain the successful message ID with the execution log.
Handle images, audio, and documents
The WhatsApp Business Cloud node supports media as well as text. Media workflows have an additional n8n-specific mapping detail: in the documented media configuration, enter the input-data field name itself, such as data. Do not enter an expression that points into a nested object.
A dependable media path looks like this:
- Receive or create the binary file in an earlier node.
- Confirm the binary property name in the execution data, for example
data. - In the Upload, Send, Download, or Delete operation, set the input-data field to that property name.
- Run a test and verify that the node sees binary data rather than an empty JSON value.
- Log the media response and retain the associated message or media identifier for later troubleshooting.
If a media request fails while text messages work, inspect the binary property first. A nested expression can look correct in the editor but still provide the node with no usable file.
Testing and production cutover
Safe test procedure
- Leave the production workflow unpublished.
- Start the WhatsApp Trigger in test mode.
- Ensure the Meta app points to the test webhook URL.
- Send an inbound message and inspect the trigger payload.
- Test the outbound node separately, then test the complete workflow.
Move to production
- Stop test listening and save the tested workflow.
- Publish the workflow.
- Confirm that n8n displays the production webhook URL.
- Register or verify that URL in Meta, remembering that it replaces the test URL.
- Send a production test message and confirm both the trigger execution and outbound response.
Do not leave a second test workflow active with the same app. Because WhatsApp stores one webhook URL per app, switching URLs can make a healthy workflow appear broken when another workflow has taken over event delivery.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallCommon failures and fixes
| Symptom | Likely cause | Fix |
|---|---|---|
| The trigger never fires. | The wrong webhook URL is registered, or a test and production workflow are competing. | Unpublish the competing workflow, register the intended URL, and send a new message. |
| Account events are absent. | The app is not subscribed under the WhatsApp Business Account. | Check the WhatsApp Business Account subscription and confirm that the app is eligible to receive notifications. |
| Meta rejects webhook delivery. | The app is shared with a business in a way that prevents those notifications. | Review the app-sharing arrangement and use an app configuration that can receive the account’s webhook events. |
| Outbound authentication fails. | The access token or WhatsApp Business Account ID is wrong, incomplete, or attached to another business asset. | Copy both values again from Meta’s WhatsApp API Setup area and update the WhatsApp Business Cloud credential. |
| The OAuth2 trigger cannot authorize. | The App ID and App Secret were entered in the wrong credential fields. | Use the Meta App ID as client ID and the App Secret as client secret, then authorize again. |
| A template send returns a bad request. | Parameter order, value, or data type differs from the approved template. | Inspect the template definition, normalize values in Set or Edit Fields, and remap every parameter. |
| Text works but media fails. | The media node received a nested expression instead of the binary input-data field name. | Provide the property name itself, such as data, and verify that binary data exists before the media operation. |
| A workflow reacts to the wrong event. | The trigger is configured for an account or template event instead of messages. | Select the message event, or add an explicit filter for the intended event family. |
Choose an implementation route
The core WhatsApp configuration is the same, but the operational choices differ. Decide these axes before building a large workflow.
| Decision | Option 1 | Option 2 | What changes |
|---|---|---|---|
| n8n hosting | Self-hosted n8n | n8n Cloud | Where you operate the n8n instance and manage its availability, updates, and access. |
| Outbound authentication | API key | Not applicable to the outbound node’s documented setup | Use the Meta access token and WhatsApp Business Account ID for WhatsApp Business Cloud actions. |
| Trigger authentication | OAuth2 | Credential-specific configuration | Use the Meta App ID and App Secret when the WhatsApp Trigger requests OAuth2. |
| Message format | Plain text | Approved template | Templates require exact parameter order and data types; plain text does not use template parameters. |
| Content type | Text-only | Media-capable | Media workflows require binary input mapping and may include upload, download, or delete operations. |
The table describes configuration differences, not a claim that one hosting route is universally better. Select the route that fits your team’s control, maintenance, and deployment requirements, then apply the same webhook discipline in either environment.
Best Value
- Carrier: This phone is locked to Tracfone, which means this device can only be used on the Tracfone wireless network. Activating is easy, just 3 steps.
- ACTIVATION Promotion: Includes 1500 min, 1500 texts & 1500 MB Data + add more as you need it
- CAMERA SYSTEM: 50MP Quad Pixel camera. Capture sharper, more vibrant photos day or night with 4x the light sensitivity.
- PERFORMANCE: Blazing-fast Qualcomm performance. Get the speed you need for great entertainment with a Snapdragon 680 processor and 4GB of RAM.
- 64GB built-in storage. Get plenty of room for photos, movies, songs, and apps. Made for US
Practical workflow patterns
Inbound support triage
Start with a message trigger, classify the incoming text, look up the customer record, and route the event. Send an immediate acknowledgement through Send, then branch complex cases to a queue or human process. Keep the acknowledgement path short so a slow external lookup does not prevent the customer from receiving a response.
Template-based status notification
Use a business event from a database or HTTP Request node, normalize customer and status fields in Set or Edit Fields, and send an approved template. Before publishing, test every parameter combination that can occur in production, especially optional values that might otherwise resolve to empty data.
Media intake
Trigger on an inbound message containing an image, audio file, or document. Pass the binary property name to the media operation, download the file when the workflow needs a local copy, process it, and delete the uploaded media when retention is no longer required. Log the media identifier alongside the workflow execution.
Two-way interaction
Use Send and Wait for Response when the workflow should pause after asking a question. Define the expected response path, add a timeout or fallback branch appropriate to your process, and ensure that unrelated account events cannot enter the waiting step.
Security, maintenance, and observability
- Store access tokens and App Secrets in n8n credentials, not in ordinary text fields or message bodies.
- Limit workflow access to people who need to change Meta credentials or webhook settings.
- Keep the Meta app, WhatsApp Business Account, and n8n credential names aligned so operators can identify the correct environment.
- Log message IDs, template responses, media IDs, and complete error payloads without exposing unnecessary customer content.
- Document which Meta app owns the production webhook URL and who is allowed to switch it during testing.
- After any template revision, retest parameter order and data types before enabling the workflow again.
- After any change to media handling, inspect the binary property name in a real execution.
These practices make failures diagnosable: a missing trigger points to subscription or webhook ownership, while a rejected send points to credentials, template values, or media mapping.
What a finished setup should look like
A complete integration has a Meta business portfolio, a WhatsApp-enabled business app, a WhatsApp Business Account subscription, and the required identifiers and credentials in n8n. The inbound side uses one deliberately selected WhatsApp Trigger event and one active webhook URL. The outbound side uses WhatsApp Business Cloud for messages, templates, and media, with template parameters and binary fields validated before production.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Repair Windows errors before they cause bigger problems3Scan for outdated or missing drivers - takes under a minuteBuild and test with production unpublished, switch deliberately to the production URL, and keep execution logs that connect each inbound event to its outbound result. That sequence prevents the two most expensive mistakes: silently replacing the production webhook while testing and sending malformed template or media requests.
Quick Recap
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.
