Hi guys,
I am having a problem to get the whatsapp node working in a very, very basic workflow to just test the business whatsapp API. I am seeing the Webhook in the Meta App Dashboard, but it is not reaching the node in N8N when I send a message from my phone to the test number. But if I go to “API Tests” in the Meta Dashboard, click on “test”, the N8N node is working.
Can someone help me understand what am I doing wrong?
@terivi If you run into that same stuck webhook issue, you might find this quick walkthrough helpful. It covers setting up the WhatsApp node and webhook in n8n to help you nail the configuration:
Hope this helps!
Hey @terivi Welcome !
Your setup is good enough for webhook verification and Meta’s “Send test” button, but that doesn’t guarantee real WhatsApp messages will reach n8n. This exact pattern has shown up before, and it usually comes down to one of two things.
First, test vs real subscription.
Meta can send test events even if the WhatsApp number isn’t actually subscribed to the app. In that case, verification and test events work, but real messages never arrive. The fix is to subscribe the WhatsApp account to the app via the Graph API (/<whatsapp_account_id>/subscribed_apps). If that list is empty, real messages won’t be delivered.
Second, only one webhook per app.
WhatsApp supports only a single webhook URL per app. If you switched between test and production URLs or different environments, WhatsApp will only send real messages to the last registered URL. Tests may still succeed while your workflow is listening on a different one.
Quick check:
Make sure the WhatsApp account is subscribed to the app
Make sure the production webhook URL is the one currently registered not the test one.
(The test url will have webhook-test in it’s URL)
Once those two are aligned, real messages should start hitting your n8n trigger.
Let me know if this helps you @terivi
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.