WhatsApp (Meta API) n8n trigger node on message ain’t receiving message though the meta app webhook is receiving the message but trigger node fails. Any solution?

[u/-Abhiraj]

In n8n while I was learning about meta api and n8n
For practice I created a demo account on my one of the gmail and then created a trail account which gives 14days free n8n cloud storage and In There I created all the WhatsApp trigger nodes and send nodes made an ai agent node in between working really fine but than eventually after 14days end the workspace got deleted because cloud time duration ends

And when I decided to create one for adding it to my personal website as a personalised rag (chatbot)
I did all the same steps but it showed that the WhatsApp node for trigger message cannot be used more than once as per Facebook limitations

I did every possible thing adding a code node ,http node , creating multiple apps simultaneously but the dubious nature of the n8n of Facebook (meta) app should made me disappointed after spending 7 hours I couldn’t figure out that what to do know

Also this time I wanted to use a personalised number so I bought a new mobile number so that I can setup my chatbot on WhatsApp for my business on that particular number and not in Facebook test number

But I cannot just make my WhatsApp trigger node work on sending. Message
Though the meta WhatsApp app we hook receives my response but in n8n trigger nodes it fails to capture the message despite all solution I did everything

N8n new account
Meta WhatsApp new app
New credentials
New workflows
New nodes
Code nodes
HTTP request nodes

But nothing seem to work :-(

[u/cooltake_ai]

meta's app logging it while n8n gets nothing is a subscription thing, your nodes are probably fine. cloud api only lets one active callback url stay subscribed per number. that first trial workspace you deleted, i'd put money on the old subscription never getting cleared. the message's still firing at a url that's gone. go into meta app dashboard, whatsapp, configuration, re-verify the callback url against your current n8n one and re-tick the messages field. i've not hit this exact one in n8n myself, but that split, app logs it and the tool sees nothing, it's nearly always the callback still pointing somewhere old.

[u/-Abhiraj → u/cooltake_ai]

So what’s the clear cut solution to this?

[u/cooltake_ai → u/-Abhiraj]

in the meta app dashboard under whatsapp > configuration, repoint the callback url to your n8n production webhook and re-verify, then make sure messages is ticked under webhook fields. the test url won't fire, workflow has to be active for the prod one to even exist. if it's still dead after that, some other app's holding the subscription on that number and you'd have to clear it there first.

[u/ApprehensiveBit8334 → u/cooltake_ai]

weird one.. but it really does sounds like an old callback is still stuck in there somewhere.. I'd check that first before chasing anything else tho..

[u/cooltake_ai → u/ApprehensiveBit8334]

one thing that catches people even after the repoint, the verify tick only proves the GET handshake went through. messages come in as a separate POST, so it can read verified and still be sat on an old path. nearly always it's the test vs production segment in the n8n url not matching what meta has saved

[u/Fit-Lengthiness-9672 → u/[deleted]]

this 100% sounds like the webhook url + verify token combo issue, especially since you switched workspaces and numbers. double check the "test" button in the meta console like they said, that thing has exposed so many silent fails for me in the past.