You are absolutely right the native WhatsApp node locks that token away internally, which is exactly why you are stuck in this loop.
Try this: The Manual Handshake:
• Delete the WhatsApp Trigger and add a standard Webhook node.
• Set the Method to GET and the Path to whatsapp.
• Connect a Respond to Webhook node to it.
• Set the Response Body option to {{ $json.query['hub.challenge'] }}.
• Go to the Meta Console, enter your new URL (e.g. .../webhook/whatsapp), type any random token (like 12345), and click Verify.
• Once you get the green success message, switch the Webhook node Method to POST to start receiving actual messages.
This tricks Meta into verifying your URL without needing the specific token from the broken trigger node.
Let me know if that finally gets you the green checkmark.
Thank you, this has worked. However I am experiencing intermittent data exchange during Whatsapp Flows. Should I start a new conversation for that or continue with this one?
That is great news! I’m glad for you.
If you could please mark the post that helped you as the Solution , that would be awesome—it helps others find the right answer quickly when searching later.
Definitely start a new topic for WhatsApp Flows , posting a fresh thread with its own title (and maybe some logs!) will help you catch the eye of the right experts.
regards,
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.
Hi, I’ve been struggling with the same problem for two days. I also have a VPS with Hostinger. I’m wondering if you’re not experiencing this issue anymore and Hostinger has fixed it, or if you’ve followed the advice above and are simply not using the pre-defined WhatsApp trigger? Hostinger’s Bot Assistant is blindly suggesting various solutions and trying to convince me I’ve messed up the server settings. The last piece of advice I got was to use Cloudflare, but I’d still like to explore other, simpler solutions before I switch to Cloudflare.