Contents
- The Short Answer
- All 6 Causes at a Glance
- Cause 1: Your Meta App Is Not Subscribed to the WhatsApp Business Account
- Cause 2: The Test URL Overwrote the Production URL
- Cause 3: Self-Hosted n8n Registers a localhost URL
- Cause 4: The Meta App Is Still in Development Mode
- Cause 5: "The WhatsApp App ID already has a webhook subscription"
- Cause 6: Wrong App Secret, or Messages Not Selected
- Still Broken? A Checklist
- How to Stop It Coming Back
- Once Messages Arrive
- Sources
- FAQ
The Short Answer
The WhatsApp Trigger not receiving messages problem looks like this: Meta's Test button works, outgoing messages work, and real messages from a phone start no execution and log no error.
The n8n WhatsApp Trigger documentation names the main cause: Meta sends webhooks for a WhatsApp Business Account (WABA) only to apps subscribed to it, and publishing registers your webhook URL on the app without subscribing the app to the WABA.
Self-hosted instances have a louder failure when you listen:
Bad request - please check your parameters
WhatsApp Trigger: Invalid parameter
That one almost always means n8n tried to register a localhost:5678 URL. Both are below, with four other causes.
All 6 Causes at a Glance
| Symptom | Cause | Fix | How to confirm |
|---|---|---|---|
| Meta test event arrives, real messages never do, no execution | Your app is not subscribed to the WABA, or an override sends events elsewhere | POST to subscribed_apps | GET subscribed_apps does not list your App ID |
| Works in test, stops in production, or the reverse | One webhook per Meta app; Test and Production URLs overwrite each other | Unpublish to test, publish again after | You listened for a test event on a published workflow |
| "Bad request - please check your parameters", "Invalid parameter" | Webhook URL is localhost or not public HTTPS | Set the public webhook URL environment variable | The node's webhook URL shows localhost or port 5678 |
| Only Meta's test events or a few phones trigger it | App still in Development mode with the test number | Add the phone as a test recipient, or switch App Mode to Live | App settings show Development |
| "The WhatsApp App ID ... already has a webhook subscription" | Another trigger or tool already holds the app's webhook | Unpublish the other workflow or use another Meta app | Another published workflow uses the same credential |
| Meta shows deliveries, n8n starts nothing | Wrong App Secret, or Messages not selected in Trigger On | Correct the credential or the event list | Compare the credential's Client Secret with the app's App Secret |
Cause 1: Your Meta App Is Not Subscribed to the WhatsApp Business Account
This is the cause behind the "WhatsApp Trigger not receiving real messages" thread. Real messages go only to the webhooks of apps subscribed to the WABA. The docs add the confusing part: a test event from the Meta App Dashboard can still reach n8n, so a passing test does not rule this out.
How to confirm it: in the Meta Apps dashboard, open your app, go to WhatsApp > API Setup, and copy the WhatsApp Business Account ID (not the Phone number ID). Get a token for the same app as your n8n credential with the whatsapp_business_management permission, for example from Graph API Explorer. List the subscribed apps:
curl -X GET 'https://graph.facebook.com/<api-version>/<business-account-id>/subscribed_apps' \
-H 'Authorization: Bearer <access-token>'
Each app's ID is in whatsapp_business_api_data.id. Yours is the Client ID in your n8n credential. If data is empty or no ID matches, you are not subscribed.
The fix: subscribe the token's app. No body is needed:
curl -X POST 'https://graph.facebook.com/<api-version>/<business-account-id>/subscribed_apps' \
-H 'Authorization: Bearer <access-token>'
It returns {"success": true}. Run the GET again, then message the number.
Also check your entry for override_callback_uri. If present, Meta sends message webhooks to that URL instead, and an override on the business phone number takes precedence over both. The bodiless POST removes the override from your app's subscription.
A fix that does harm: the docs warn against sending DELETE to subscribed_apps. It unsubscribes your app and Meta stops sending webhooks for that account.
Cause 2: The Test URL Overwrote the Production URL
The docs state that WhatsApp allows a single webhook per app. Each time you switch between the Test URL and the Production URL, WhatsApp overwrites the registered one, and only one of the two receives events.
How to confirm it: production messages stopped right after you tested the published workflow in the editor.
The fix, as the docs give it. Production traffic stops while the workflow is unpublished:
- Open the workflow and select Unpublish.
- Test with the test webhook URL.
- When you finish, select Publish. The production URL is registered again.
To test without touching production, use a second Meta app with its own credential. The general Test versus Production URL rules are in our post on The requested webhook is not registered.
Cause 3: Self-Hosted n8n Registers a localhost URL
This is the "Error in WhatsApp Trigger happening only in local n8n" thread. The credential tests fine, and listening for an event fails with:
Problem running workflow
Bad request - please check your parameters
WhatsApp Trigger: Invalid parameter
The poster found the difference: on n8n Cloud the webhook URLs used their cloud domain, locally localhost:5678. The node sends its webhook URL to Meta as the callback, so Meta must be able to reach it, over HTTPS with a valid certificate. Meta does not accept self-signed ones.
How to confirm it: open the WhatsApp Trigger and look at its webhook URLs. If they start with http://localhost:5678, Meta cannot use them.
The fix: put n8n behind a public HTTPS address (a reverse proxy with a real certificate, or a tunnel while developing) and tell n8n that address. The reverse proxy documentation gives:
N8N_WEBHOOK_URL=https://n8n.example.com/
N8N_PROXY_HOPS=1
N8N_WEBHOOK_URL exists from n8n 2.30.0 and replaces WEBHOOK_URL, deprecated from 2.35.0. On older versions set WEBHOOK_URL instead. Restart n8n, check the node now shows your public URL, and publish again.
A fix that misleads: one reply sets N8N_PORT=443, which changes the port n8n listens on. The next reply reports losing the UI in Docker. Keep n8n on its internal port and set the webhook URL. The guide to the true cost of self-hosting n8n covers what the proxy and certificate add.
Cause 4: The Meta App Is Still in Development Mode
n8n's WhatsApp credentials documentation ends the app setup with three steps people skip: in App settings > Basic, set the Privacy Policy URL and Terms of Service URL, then change the App Mode to Live.
Replies in the forum thread report that a Development mode app on Meta's test number only delivers messages from phones added as test recipients under API Setup. We could not find Meta stating that rule clearly, so treat it as reported behaviour. Both fixes are cheap.
How to confirm it: the app dashboard shows the app in Development, and you are messaging Meta's test number from a phone that is not in its recipient list.
The fix: add your phone as a test recipient, or set the App Mode to Live.
Cause 5: "The WhatsApp App ID already has a webhook subscription"
This message comes from the node's source code, WhatsAppTrigger.node.ts:
The WhatsApp App ID <app-id> already has a webhook subscription. Delete it or use another App before executing the trigger. Due to WhatsApp API limitations, you can have just one trigger per App.
If the app already has a subscription for the same events with a different callback URL, n8n refuses to replace it.
How to confirm it: another published workflow uses a WhatsApp Trigger with the same credential, or the app was connected to another tool or an older n8n instance.
The fix: use one WhatsApp Trigger per Meta app and route inside that workflow with a Switch node. If another workflow holds the subscription, unpublish it: n8n deletes the app's webhook subscription on unpublish. Or use a second Meta app. This error is about the app's webhook, not the WABA, so do not "fix" it with a DELETE on subscribed_apps.
Cause 6: Wrong App Secret, or Messages Not Selected
Two quiet causes, both visible in the source.
The App Secret is wrong. The node signs each incoming body with your credential's Client Secret and compares it with Meta's x-hub-signature-256 header. On a mismatch it starts nothing and logs no failure. A reset App Secret, or one from another app, does this.
How to confirm it: in App settings > Basic, the App ID must equal the credential's Client ID and the App Secret its Client Secret, from the same app.
The fix: paste the current App Secret into the credential, save, and publish again.
Messages is not in Trigger On. The node subscribes only to the events you select. Separately, Options > Receive Message Status Updates controls whether sent, delivered and read notifications start executions. To run the agent only on inbound texts, filter after the trigger:
{{ $json.messages !== undefined }}
Use it in an If node so status updates never reach your AI agent.
Still Broken? A Checklist
- The workflow is published, and the Publish button shows no partial or failed state.
GET /<waba-id>/subscribed_appslists your App ID, with no unexpectedoverride_callback_uri.- The node's Production URL is public HTTPS with a valid certificate, not localhost.
- Nobody has listened for a test event on this workflow since it was last published.
- The credential's Client ID and Client Secret are this app's App ID and App Secret.
- Messages is selected in Trigger On.
- The app is Live, or your phone is a test recipient.
- No other workflow or tool uses a WhatsApp Trigger on this Meta app.
Then send a message and check the Executions list. Production runs do not appear on the canvas.
How to Stop It Coming Back
Keep two Meta apps: one for development, one for production, each with its own n8n credential. One webhook per app then stops being a trap.
Pin the public URL in configuration, so a restart or a new container cannot fall back to localhost.
Add an error workflow in Workflow Settings so failures after the trigger reach you. See error handling.
Once Messages Arrive
Next comes memory per sender: use messages[0].from as the session key, as in our No session ID found post. Our WhatsApp AI agent tutorial walks through a full build, and the n8n review covers the platform.
The n8n AI Agents course covers webhooks and triggers, chat workflows, tools, per-user memory, error handling and human fallback, and deployment on Cloud or your own server, building agents that run on channels like WhatsApp end to end. Start with the free lesson on what n8n is and why it uses nodes.
Sources
Checked against n8n's documentation, source code and community forum on 17 November 2026.
- n8n docs: WhatsApp Trigger common issues - one webhook per app, the WABA subscription check, the subscribed_apps requests and the DELETE warning.
- n8n docs: WhatsApp Business Cloud credentials - Client ID and Client Secret, App Mode Live.
- n8n docs: Configure webhook URLs with reverse proxy - N8N_WEBHOOK_URL, WEBHOOK_URL and version notes.
- n8n source: WhatsAppTrigger.node.ts - the already-subscribed error, signature check and status filter.
- Meta: WhatsApp Cloud API webhooks - HTTPS callback with a valid certificate.
- n8n community: WhatsApp Trigger not receiving real messages and Error in WhatsApp Trigger happening only in local n8n.
FAQ
- Why does the Meta test event reach n8n but real WhatsApp messages do not?
- Real messages go only to apps subscribed to your WhatsApp Business Account, and publishing does not create that subscription. List the WABA's subscribed_apps and POST to add your app if it is missing.
- What does "Bad request - please check your parameters" mean on the WhatsApp Trigger?
- With the detail "WhatsApp Trigger: Invalid parameter", it usually means Meta rejected the callback URL n8n tried to register, most often a localhost address on a self-hosted instance. Set N8N_WEBHOOK_URL, or WEBHOOK_URL before n8n 2.30.0, to a public HTTPS address and restart.
- Why does my WhatsApp workflow stop working after I test it?
- WhatsApp allows one webhook per Meta app. Listening for a test event replaces the production webhook with the test one. Unpublish before testing and publish again afterwards, or use a separate Meta app for development.
- Can I have two WhatsApp Trigger workflows on one Meta app?
- No. The node says you can use one WhatsApp trigger for each Facebook app, and a second one fails with "already has a webhook subscription". Use one trigger and route inside the workflow, or create another Meta app.
- Do I need to set a verify token for the WhatsApp Trigger?
- No. n8n answers Meta's verification challenge itself, using the node's own ID as the verify token. The credential holds only the Client ID and Client Secret.
- Should I delete the WABA subscription to fix a webhook conflict?
- No. n8n's docs warn that DELETE on subscribed_apps unsubscribes your app from the WhatsApp Business Account, after which Meta sends no webhooks for it. The conflict error is about the app's webhook, not the WABA subscription.
If this resonated
Module 02 is the long version of this post.
Eval set, refusal pattern, kill switch. Build it in a weekend.
