# WhatsApp Trigger not receiving any messages always bad parameters **URL:** \ **Category:** Questions\ **Tags:** core, node, bug:unconfirmed\ **Created:** [August 10, 2026, 1:56am UTC](https://community.n8n.io/t/whatsapp-trigger-not-receiving-any-messages-always-bad-parameters/306810 "2026-08-10T01:56:55Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![Myth\_Xenodo](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/myth_xenodo/32/185016_2.png) [@Myth\_Xenodo](https://community.n8n.io/u/Myth_Xenodo)\ **Post date:** [August 10, 2026, 1:56am UTC](https://community.n8n.io/t/whatsapp-trigger-not-receiving-any-messages-always-bad-parameters/306810/1 "2026-08-10T01:56:55Z")
I have problem in my WhatsApp Trigger which always said bad parameters and not receiving anything in my whatsApp at all. ## What is the error message (if any)? It always say Bad Parameters. ![image](https://europe1.discourse-cdn.com/n8n/original/3X/6/8/681d0cb48e00f11de7ed773bbac1f548b78c8f86.png) ## Please share your workflow ```auto And this is the workflow looks like. Just simple and basic but whatsapp trigger ain't working even though the App ID and App Secret is working fine. and also everything in the setup of WhatsApp in 1) Try It Now and 2) Production Setup. ``` ![image](https://europe1.discourse-cdn.com/n8n/original/3X/d/3/d3d7692b5eb9a9d2a3783f3ee1a6fbd6f594fbef.png) ## Share the output returned by the last node I am expectting the output to receive by me or the phone number that is recipient ## Information on your n8n setup - **n8n version: Latest version** - **Database (default: SQLite): Not sure** - **n8n EXECUTIONS\_PROCESS setting (default: own, main): own** - **Running n8n via (Docker, npm, n8n cloud, desktop app): npm** - **Operating system: Windows 11** ---
**Author:** ![n8n](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/n8n/32/196425_2.png) [@n8n](https://community.n8n.io/u/n8n)\ **Post date:** [August 10, 2026, 1:57am UTC](https://community.n8n.io/t/whatsapp-trigger-not-receiving-any-messages-always-bad-parameters/306810/2 "2026-08-10T01:57:42Z")
Hey @Myth_Xenodo, while you wait for a response, here are some things that might help: > **Suggested resources** > > _Automatically matched to your question._ > > **Docs:** > > - [Common issues](https://docs.n8n.io/integrations/builtin/app-nodes/n8n-nodes-base.whatsapp/common-issues) > > **Forum:** > > - [Whatsapp trigger works only with test number, but I can send messages with my own number](https://community.n8n.io/t/234114) > - [Whatsapp trigger not working, all tests are sucsessfull](https://community.n8n.io/t/232867) > - [When I try to execute a whatsapp trigger node, it says this needs to be triggered with access token, but the oauth credentials are taken for connection test, how do I fix this issue?](https://community.n8n.io/t/213760) @edumats, @Leoncsm1, @LogeshwariV - you’ve helped with similar issues before, can you take a look? _Automatically suggested by n8n’s community bot. It’s a pilot - [please share feedback here](https://community.n8n.io/t/pilot-forum-helper-bot/304669)._ ---
**Author:** ![kjooleng](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/kjooleng/32/184045_2.png) [@kjooleng](https://community.n8n.io/u/kjooleng)\ **Post date:** [August 10, 2026, 2:17am UTC](https://community.n8n.io/t/whatsapp-trigger-not-receiving-any-messages-always-bad-parameters/306810/3 "2026-08-10T02:17:16Z")
Hi @Myth_Xenodo Meta needs to know _which_ part of your app should receive the webhook. - Go to your **Meta App Dashboard**. - Look for the **Webhooks** section in the left sidebar. - **Crucial Step:** There is often a dropdown menu to “Select a product” for the webhook. Ensure you have selected **“WhatsApp Business Account”** (or similar WhatsApp-related product) from that dropdown. If you have selected “Facebook Login” or “Instagram” by mistake, the trigger will fail with a “bad parameter” error when n8n tries to register. If you are running n8n on your own computer (`localhost`) or a local server: - **WhatsApp cannot “see” your computer.** For the trigger to work, Meta must be able to send a POST request to your n8n instance. - **Solution:** You must use a tunnel like **ngrok** , **Cloudflare Tunnel** , or a reverse proxy to give your local n8n instance a public `https://` URL. - **Check your `WEBHOOK_URL`:** Ensure your n8n environment variable `WEBHOOK_URL` is set to your public tunnel address (e.g., `https://your-ngrok-id.ngrok-free.app`). Meta requires a secure connection to send webhook events. - If you are self-hosting, ensure your n8n instance is using a valid **SSL certificate** (HTTPS). - Meta will reject connections to sites with self-signed certificates or those that are only accessible via HTTP. Did any of these apply? Please provide the following information: 1. Have you already successfully configured the **Webhook URL** inside your Meta App dashboard? 2. Did the error appear specifically when you tried to **activate** the workflow or when you tried to **test/execute** it? ---
**Author:** ![Myth\_Xenodo](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/myth_xenodo/32/185016_2.png) [@Myth\_Xenodo](https://community.n8n.io/u/Myth_Xenodo)\ **Post date:** [August 10, 2026, 4:04am UTC](https://community.n8n.io/t/whatsapp-trigger-not-receiving-any-messages-always-bad-parameters/306810/4 "2026-08-10T04:04:34Z")
I have tried webhook and it is just really not working at all. I self host for free in ngrok but it doesn’t work at all it gives me frustration that none of webhook and it keeps also interrupting each other webhook which it doesn’t make sense. ---
**Author:** ![Myth\_Xenodo](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/myth_xenodo/32/185016_2.png) [@Myth\_Xenodo](https://community.n8n.io/u/Myth_Xenodo)\ **Post date:** [August 10, 2026, 4:09am UTC](https://community.n8n.io/t/whatsapp-trigger-not-receiving-any-messages-always-bad-parameters/306810/5 "2026-08-10T04:09:30Z")
I followed these tutorial but my problem always end up to bad parameters. [![](https://europe1.discourse-cdn.com/n8n/original/3X/0/9/09203e58f9bc833a210fc687e7d5266916a4bebe.jpeg "n8n WhatsApp Trigger Not Working? Here's the Real Fix (2026)") ](https://www.youtube.com/watch?v=l4ktnGhScfM) when I execute workflow it just doesn’t run. It just exit quickly here is the image. ![image](https://europe1.discourse-cdn.com/n8n/original/3X/3/2/32b8a074db61911400762fd51131858eb7c1f9da.png) ![image](https://europe1.discourse-cdn.com/n8n/original/3X/a/7/a745d1208e34c3ad726a4b5e2da425266aafd33b.png) ![image](https://europe1.discourse-cdn.com/n8n/original/3X/6/0/60a4654338ac2b17645fef2abdf0cbe9445071d9.png) ---
**Author:** ![anon71933009](https://avatars.discourse-cdn.com/v4/letter/a/c6cbf5/32.png) [@anon71933009](https://community.n8n.io/u/anon71933009)\ **Post date:** [August 10, 2026, 4:36am UTC](https://community.n8n.io/t/whatsapp-trigger-not-receiving-any-messages-always-bad-parameters/306810/6 "2026-08-10T04:36:28Z")
Hi @Myth_Xenodo Welcome! A few things that catch people out with this exact setup. Free ngrok hands you a new random URL every time you restart it. So the callback URL sitting in Meta stops matching your n8n as soon as you restart anything, which would explain it feeling like the webhooks interrupt each other. Claim your free static domain in the ngrok dashboard and start ngrok with that instead. You get one per account for free and it survives restarts. Second, in Meta under WhatsApp then Configuration, saving the callback URL isn’t enough on its own. You also have to click Manage next to Webhook fields and tick **messages**. If that box is unticked everything looks correctly set up and nothing ever arrives. Third, worth double checking which credential is on which node. The WhatsApp Trigger uses App ID and App Secret, while the send node uses an access token and phone number ID. They’re two different credential types in n8n and it’s easy to end up with the wrong one attached. Also, the trigger only receives real messages when the workflow is activated, not when you hit Execute. Execute just registers a temporary test webhook and gives up, which matches your screenshot of it exiting straight away. ---
**Author:** ![Myth\_Xenodo](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/myth_xenodo/32/185016_2.png) [@Myth\_Xenodo](https://community.n8n.io/u/Myth_Xenodo)\ **Post date:** [August 10, 2026, 4:45am UTC](https://community.n8n.io/t/whatsapp-trigger-not-receiving-any-messages-always-bad-parameters/306810/7 "2026-08-10T04:45:20Z")
This doesnt make sense at all. I created an ngrok and it needs a backend script in node.js so i feed it a localhost:3000 then translate it to [https://quic](https://quic)…(something like ngrok link) i pass it to callback url and it works with the new tokey key. But when I run it. I run to the same problem. When i publish the workflow or execute workflow. Everything just crash ---
**Author:** ![anon71933009](https://avatars.discourse-cdn.com/v4/letter/a/c6cbf5/32.png) [@anon71933009](https://community.n8n.io/u/anon71933009)\ **Post date:** [August 10, 2026, 4:51am UTC](https://community.n8n.io/t/whatsapp-trigger-not-receiving-any-messages-always-bad-parameters/306810/8 "2026-08-10T04:51:04Z")
Ah, that’s the problem. ngrok doesn’t need a backend script at all. It just takes a port on your machine and gives it a public URL. You’ve pointed it at a Node script on 3000, so Meta is talking to that script instead of to n8n, and n8n never sees anything. Point it straight at n8n instead. n8n runs on 5678, so: ```auto ngrok http 5678 ``` No script, nothing on 3000, just that. Then n8n needs to know its own public address, otherwise it keeps generating localhost URLs. Stop n8n, and in the same terminal (cmd): ```auto set WEBHOOK_URL=https://your-id.ngrok-free.app n8n start ``` Now open the WhatsApp Trigger node. The webhook URL it shows should start with your ngrok address rather than localhost. That exact URL is what goes into Meta as the callback URL, along with the verify token n8n displays right there. Last bit, activate the workflow rather than hitting Execute. Execute only listens briefly and gives up, which is the crashing you’re seeing. ---
**Author:** ![Anshul\_Namdev](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/anshul_namdev/32/178229_2.png) [@Anshul\_Namdev](https://community.n8n.io/u/Anshul_Namdev)\ **Post date:** [August 10, 2026, 5:03am UTC](https://community.n8n.io/t/whatsapp-trigger-not-receiving-any-messages-always-bad-parameters/306810/9 "2026-08-10T05:03:06Z")
Hi @Myth_Xenodo Welcome! n8n registers the Meta webhook subscription itself. The WhatsApp Trigger calls the Graph API with your App ID and App Secret, sends its own callback URL, and uses the trigger node’s internal id as the verify token, which is not a value you can see or type anywhere. A callback URL and token you fill in by hand under WhatsApp \> Configuration can never match that, and the subscription it leaves behind blocks n8n from writing its own, so Meta returns “Invalid parameter”. In Meta, delete the existing webhook subscription and leave the Callback URL and Verify Token fields empty. Then publish the workflow in n8n and let it register them. An app holds only one WhatsApp webhook at a time, and n8n’s test and production URLs overwrite each other, so testing a published workflow silently kills its production traffic. > **[WhatsApp Trigger | Nodes | n8n Docs](https://docs.n8n.io/integrations/builtin/trigger-nodes/n8n-nodes-base.whatsapptrigger)** > > Learn how to use the WhatsApp Trigger node in n8n. Follow technical documentation to integrate WhatsApp Trigger node into your workflows. ---
**Author:** ![Myth\_Xenodo](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/myth_xenodo/32/185016_2.png) [@Myth\_Xenodo](https://community.n8n.io/u/Myth_Xenodo)\ **Post date:** [August 10, 2026, 5:11am UTC](https://community.n8n.io/t/whatsapp-trigger-not-receiving-any-messages-always-bad-parameters/306810/10 "2026-08-10T05:11:57Z")
Okay sir, but first I would tell how I did it. I created the App, I have to subscribe the webhooks in the Production Setup. then go to the Graph API Explorer ![image](https://europe1.discourse-cdn.com/n8n/original/3X/6/8/6885787cf3a300a1fc356a96cc1aa6053f3726af.png) ![image](https://europe1.discourse-cdn.com/n8n/original/3X/f/4/f4fb7092d90e772a8d6bcd8abef5405075649cb4.png) so I really don’t get what you mean publish the workflow in n8n and let it register them??? what’s that like a magic that automatically filled? I published also the workflow and it is just nothing happening. Nothing running at all. I install the latest version of n8n but everything is just not working as anything in documentation or tutorial. I don’t get these documentations cause none of them working on my end either they are outdate or the facebook is updated ---
**Author:** ![anon71933009](https://avatars.discourse-cdn.com/v4/letter/a/c6cbf5/32.png) [@anon71933009](https://community.n8n.io/u/anon71933009)\ **Post date:** [August 10, 2026, 5:19am UTC](https://community.n8n.io/t/whatsapp-trigger-not-receiving-any-messages-always-bad-parameters/306810/11 "2026-08-10T05:19:15Z")
Fair question, let me explain what I meant rather than just telling you to click things. When you activate a workflow with a WhatsApp Trigger, n8n calls Meta’s Graph API itself using the App ID and App Secret in your credential, and asks Meta to subscribe your app to that callback URL. Meta then calls that URL back with a challenge number and expects your n8n to echo it. That handshake is why the node needs App ID and Secret rather than just an access token, and it’s why the error you get is a Meta error code rather than an n8n one. So it isn’t magic, but it does mean n8n and your manual Graph API Explorer setup are both trying to configure the same thing, which can fight each other. Two things that would tell us where this is actually stuck. First, open your ngrok https URL directly in a browser. You should see the n8n editor load. If you see anything else, an ngrok error page, a blank page, or output from that Node script, then the tunnel isn’t reaching n8n and nothing else can work until that’s fixed. This takes ten seconds and rules out half the possibilities. Second, when you get Bad Parameters, click Show Details on the error and paste the full text. That message includes what Meta actually received back from your URL. If it starts with `` then something other than n8n answered the challenge, and that tells us exactly what’s wrong. On nothing happening after you publish, that part is normal. An active WhatsApp trigger sits silent and shows no activity until a real message arrives. It won’t look like it’s doing anything. ---
**Author:** ![Myth\_Xenodo](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/myth_xenodo/32/185016_2.png) [@Myth\_Xenodo](https://community.n8n.io/u/Myth_Xenodo)\ **Post date:** [August 10, 2026, 5:28am UTC](https://community.n8n.io/t/whatsapp-trigger-not-receiving-any-messages-always-bad-parameters/306810/12 "2026-08-10T05:28:24Z")
Okay lemme do it step by step cause I keep running the same error over and over again. So In my Production Setup in CallURL and verify token and webhook subscription. All of them are empty and now turn off. ![image](https://europe1.discourse-cdn.com/n8n/original/3X/0/b/0b1d3fe3593918dc672e41ff4884729849fd4f39.png) You told me that if I just a add the app secret and app id.. then publish work flow it would work… but it is just now?? You can see those two error at the same time? So where is my mistake here that I can’t find? ![image](https://europe1.discourse-cdn.com/n8n/original/3X/3/b/3b28900d4054fc9d3ccc33bbfd3b529ea5754a6f.png) ![image](https://europe1.discourse-cdn.com/n8n/original/3X/c/a/ca1fe565dfb78646b726db9ea5e5c14a6df2177c.png) ---
**Author:** ![anon71933009](https://avatars.discourse-cdn.com/v4/letter/a/c6cbf5/32.png) [@anon71933009](https://community.n8n.io/u/anon71933009)\ **Post date:** [August 10, 2026, 5:31am UTC](https://community.n8n.io/t/whatsapp-trigger-not-receiving-any-messages-always-bad-parameters/306810/13 "2026-08-10T05:31:09Z")
Can you paste the full error from the node? ---
**Author:** ![Myth\_Xenodo](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/myth_xenodo/32/185016_2.png) [@Myth\_Xenodo](https://community.n8n.io/u/Myth_Xenodo)\ **Post date:** [August 10, 2026, 5:31am UTC](https://community.n8n.io/t/whatsapp-trigger-not-receiving-any-messages-always-bad-parameters/306810/14 "2026-08-10T05:31:53Z")
## **Workflow could not be published** Error in node “WhatsApp Trigger”: _Bad request - please check your parameters_ > **Show Details** > > Invalid parameter ---
**Author:** ![anon71933009](https://avatars.discourse-cdn.com/v4/letter/a/c6cbf5/32.png) [@anon71933009](https://community.n8n.io/u/anon71933009)\ **Post date:** [August 10, 2026, 5:38am UTC](https://community.n8n.io/t/whatsapp-trigger-not-receiving-any-messages-always-bad-parameters/306810/15 "2026-08-10T05:38:31Z")
First, one clarification, because I explained it badly. n8n registering the webhook for you doesn’t remove the tunnel. n8n can only give Meta the address it thinks it has. If n8n doesn’t know its own public address, it sends Meta something like `http://localhost:5678/webhook/...`, and Meta rejects that because it can’t reach a localhost address. Meta’s way of saying that is Invalid parameter. So the tunnel is still needed. The difference is you don’t paste anything into Meta yourself, n8n does it during publish. Here’s the check that settles it. Open your WhatsApp Trigger node and look at the webhook URL it shows near the top of the panel. What does it start with? - `http://localhost:5678/...` or `127.0.0.1` → that’s your mistake. n8n is handing Meta an address it can’t reach. - `https://something.ngrok-free.app/...` → then it’s something else and we look further. If it’s showing localhost, the fix is: 1. Run `ngrok http 5678` and copy the https address it gives you 2. Stop n8n 3. Start it with that address, in cmd: `set WEBHOOK_URL=https://your-id.ngrok-free.app` then `n8n start` 4. Reopen the trigger node, the URL should now start with your ngrok address 5. Then publish And leave the Callback URL and Verify token boxes in Meta empty like they are now. That’s correct. n8n fills those in itself when publish succeeds. Tell me what that webhook URL says and we’ll go from there. ---
**Author:** ![Myth\_Xenodo](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/myth_xenodo/32/185016_2.png) [@Myth\_Xenodo](https://community.n8n.io/u/Myth_Xenodo)\ **Post date:** [August 10, 2026, 5:48am UTC](https://community.n8n.io/t/whatsapp-trigger-not-receiving-any-messages-always-bad-parameters/306810/16 "2026-08-10T05:48:17Z")
As what you said I follow the instruction. ![image](https://europe1.discourse-cdn.com/n8n/original/3X/2/c/2c18a27a1c9c4769a75c0c32c7120dd50d2520b2.png) but I still received the same error ![image](https://europe1.discourse-cdn.com/n8n/original/3X/8/d/8d68fc2d997bb2071f40399559455cfc2bf48bba.png) ```auto Stopping n8n... PS C:\PythonExploration\Automations> ngrok http 5678 PS C:\PythonExploration\Automations> set WEBHOOK_URL=https://quiver-comprised-stack.ngrok-free.dev/ PS C:\PythonExploration\Automations> n8n start ... n8n ready on ::, port 5678 n8n Task Broker ready on 127.0.0.1, port 5679 Failed to start Python task runner in internal mode. because its virtual environment is missing from this system. Launching a Python runner in internal mode is intended only for debugging and is not recommended for production. Users are encouraged to deploy in external mode. See: https://docs.n8n.io/hosting/configuration/task-runners/#setting-up-external-mode There are deprecations related to your n8n setup. Please take the recommended actions to update your configuration: - N8N_UNVERIFIED_PACKAGES_ENABLED -> The default for this variable will change to `false` in a future version. Set it to `true` explicitly to keep installing unverified community packages. - N8N_RUNNERS_TASK_TIMEOUT -> The default for this variable will be reduced from 300 (5 minutes) to 60 (1 minute) in a future version. Set it explicitly to keep your current task timeout. - N8N_COMPRESSION_NODE_MAX_DECOMPRESSED_SIZE_BYTES -> The default for this variable will be reduced from 2 GiB to 256 MiB in a future version. Set it explicitly to keep your current limit. - N8N_COMPRESSION_NODE_MAX_ZIP_ENTRIES -> The default for this variable will be reduced from 5000 to 1000 in a future version. Set it explicitly to keep your current limit. - Running n8n outside a container is deprecated. Future versions will require running n8n via the official Docker image. See https://docs.n8n.io/deploy/host-n8n/install-options/install-with-docker [license SDK] Skipping renewal on init: license cert is not initialized Registered runner "JS Task Runner" (QovVV5W-2UjoryQx0WKMt) Instance registered Discovered 4 cluster checks Version: 2.33.7 Building workflow dependency index... Start Active Workflows: Finished building workflow dependency index. Processed 0 draft workflows, 0 published workflows. Activated workflow "My workflow" (ID: xHV9LUdRCSpoKIUA) Editor is now accessible via: http://localhost:5678 Press "o" to open in Browser. timeout of 6000ms exceeded AxiosError: timeout of 6000ms exceeded at createTimeoutError (C:\Users\Julle myth\AppData\Roaming\npm\node_modules\n8n\node_modules\@n8n\backend-network\node_modules\axios\dist\node\axios.cjs:3562:14) at RedirectableRequest.handleTimeout (C:\Users\Julle myth\AppData\Roaming\npm\node_modules\n8n\node_modules\@n8n\backend-network\node_modules\axios\dist\node\axios.cjs:4080:15) at RedirectableRequest.emit (node:events:509:28) at Timeout._onTimeout (C:\Users\Julle myth\AppData\Roaming\npm\node_modules\n8n\node_modules\follow-redirects\index.js:233:12) at listOnTimeout (node:internal/timers:605:17) at processTimers (node:internal/timers:541:7) at Axios.request (C:\Users\Julle myth\AppData\Roaming\npm\node_modules\n8n\node_modules\@n8n\backend-network\node_modules\axios\dist\node\axios.cjs:5427:41) at processTicksAndRejections (node:internal/process/task_queues:104:5) at invokeAxios (C:\Users\Julle myth\AppData\Roaming\npm\node_modules\n8n\node_modules\@n8n\backend-network\src\http\axios\invoke.ts:15:10) at httpRequest (C:\Users\Julle myth\AppData\Roaming\npm\node_modules\n8n\node_modules\@n8n\backend-network\src\http\axios\request.ts:211:5) at Object.request (C:\Users\Julle myth\AppData\Roaming\npm\node_modules\n8n\node_modules\@n8n\backend-network\src\http\outbound-http.ts:188:12) at paginatedRequest (C:\Users\Julle myth\AppData\Roaming\npm\node_modules\n8n\src\utils\strapi-utils.ts:87:15) at McpRegistryApiClient.fetchServersMetadata (C:\Users\Julle myth\AppData\Roaming\npm\node_modules\n8n\src\modules\mcp-registry\registry\mcp-registry-api.client.ts:31:10) at McpRegistryService.refreshUpdatedServers (C:\Users\Julle myth\AppData\Roaming\npm\node_modules\n8n\src\modules\mcp-registry\registry\mcp-registry.service.ts:184:20) at McpRegistryService.refreshFromApiInternal (C:\Users\Julle myth\AppData\Roaming\npm\node_modules\n8n\src\modules\mcp-registry\registry\mcp-registry.service.ts:157:20) at McpRegistryService.refreshFromApi (C:\Users\Julle myth\AppData\Roaming\npm\node_modules\n8n\src\modules\mcp-registry\registry\mcp-registry.service.ts:144:4) Error fetching from Strapi API (https://api.n8n.io/api/mcp-servers): timeout of 6000ms exceeded Failed to refresh MCP registry ``` and this is ngrok ![image](https://europe1.discourse-cdn.com/n8n/original/3X/f/3/f310538ebca564e9599cb915f9c79b0a3fb79eb6.png) ---
**Author:** ![anon71933009](https://avatars.discourse-cdn.com/v4/letter/a/c6cbf5/32.png) [@anon71933009](https://community.n8n.io/u/anon71933009)\ **Post date:** [August 10, 2026, 5:56am UTC](https://community.n8n.io/t/whatsapp-trigger-not-receiving-any-messages-always-bad-parameters/306810/17 "2026-08-10T05:56:46Z")
Found it, and it’s my fault. I gave you the cmd syntax and you’re in PowerShell. Look at your own log: ```auto PS C:\PythonExploration\Automations> set WEBHOOK_URL=https://quiver-comprised-stack.ngrok-free.dev/ ``` That `PS` at the start means PowerShell, and PowerShell doesn’t understand `set VAR=value`. There `set` is an alias for something else entirely, so the variable was never actually set. n8n started up still thinking it lives on localhost, handed Meta a localhost callback URL, and Meta rejected it. That’s your Invalid parameter. In PowerShell it’s this instead: ```powershell $env:WEBHOOK_URL="https://quiver-comprised-stack.ngrok-free.dev" n8n start ``` Drop the trailing slash too, otherwise you can end up with a double slash in the webhook path. Before starting n8n you can confirm it took by running: ```powershell echo $env:WEBHOOK_URL ``` If that prints your ngrok address you’re good. Then start n8n, open the WhatsApp Trigger node, and the webhook URL should finally show your ngrok domain instead of localhost. Publish after that. One thing worth saying, your tunnel is fine. The ngrok window shows requests hitting n8n and returning 200, so that side was working the whole time. It was only ever n8n not knowing its own public address. Does this help? ---
**Author:** ![Myth\_Xenodo](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/myth_xenodo/32/185016_2.png) [@Myth\_Xenodo](https://community.n8n.io/u/Myth_Xenodo)\ **Post date:** [August 10, 2026, 6:04am UTC](https://community.n8n.io/t/whatsapp-trigger-not-receiving-any-messages-always-bad-parameters/306810/18 "2026-08-10T06:04:17Z")
I thank you so much for this T\_T my 2days problem have been solve ---
**Author:** ![anon71933009](https://avatars.discourse-cdn.com/v4/letter/a/c6cbf5/32.png) [@anon71933009](https://community.n8n.io/u/anon71933009)\ **Post date:** [August 10, 2026, 6:04am UTC](https://community.n8n.io/t/whatsapp-trigger-not-receiving-any-messages-always-bad-parameters/306810/19 "2026-08-10T06:04:54Z")
Welcome means alot. ---
**Author:** ![system](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/system/32/195824_2.png) [@system](https://community.n8n.io/u/system)\ **Post date:** [August 17, 2026, 6:05am UTC](https://community.n8n.io/t/whatsapp-trigger-not-receiving-any-messages-always-bad-parameters/306810/20 "2026-08-17T06:05:11Z")
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.