I’m trying to create a WhatsApp chatbot on n8n cloud, but for the past two days, neither the webhook nor the WhatsApp trigger has been able to capture the messages I sent to the test number. I tried different numbers and different accounts. I verified the callback URL and verification token in the meta panel and enabled message subscription. On n8n, I set the webhook’s HTTP method to POST, then selected the “Respond Immediately” option and clicked the “Listen for Test Event” button. I sent a message to the test number, but it didn’t detect it.
We might need some more details to debug this further. Could you copy/paste your workflow code into a reply (just make sure that you paste the entire workflow in the placeholder when you insert the </> section).
I actually followed Nate Herk’s guide on setting up WhatsApp integration and I didn’t even do any configuration with regards to the callback URL.
The main things for the WhastApp Trigger was:
I sent myself a test message first from n8n. Just to make sure that n8n→ WhatsApp worked and I had the right phone number.
The WhatsApp Trigger is a different credentail to sending.
I have the same Problem.
i also followed Nate Herk´s Guide
But got no Trigger when i send a test Message to the Testnumber
Both Whatsapp Trigger Credentials are green (receive Mesage and send Messages)
I got no Idea where begin to Check what´s wrong
you must set up and verify you own business number. and then, after the verification gone, it works.
it´s not working with Whatsapp Business Testaccount (at least not for me)
important: first send a whatsapp message (for exmaple from your Private Whatsapp) to the PhoneNumber you want to use. Only then will the number from Meta be activated for messages.
Yes, the problem still persist, even I have checked several times. After reviewing all the chats from other community members, I believe it will only work with completely Meta suite verified profile. I am hoping that it will work after that; however, in built n8n AI chat model is saying that we need to active the workflow before starting event listening for the trigger. Let’s see what result will come after full verification.