Currently, Meta changed the interface and setup page on Meta App of WhatsApp. Is there any latest guide on how to set-up on Meta Developer and which node should I be using? (WhatsApp Trigger or HTTP Request)
My previous WhatsApp automation still works fine, but when I create new Meta App of WhatsApp, everything’s changed and I couldn’t be certain that previous settings still applicable. It would be best if I could be pointed a path on how to start with WhatsApp automation again.
Regards.
I tried the process recently, and while the interface has changed a bit, it’s not too different.
I recently setup a Whatsapp trigger for chat - this is the front end of a lengthy content creation and auto-posting to ALL socials project. #1. I started with a truly sanitized real sim phone # not connected to any whatsapp account.
#2. I followed Nate Herk’s youtube tutorial setup (7mo old but worked) https://www.youtube.com/watch?v=A0OwvNOLNlw
#3 Created new app. careful to choose “other” as in vid despite Meta warning that will be deprecated. #4 Instead of test # i plugged the real # right off the bat. Put any (of my whatsapp) phone # as recipient #. that allows to continue.
#5 gen Access Token & permissions.
#6 I was careful to leave Callback URL blank; not enter anything ahead of time. The Hostinger tutorial says: “Click Execute Step (this registers the webhook with Meta automatically)”. That’s the key — when you click “Execute Workflow” or “Execute Step” on the WhatsApp Trigger node in n8n, it auto-registers the webhook URL with Meta behind the scenes. You never need to manually paste the callback URL into the Meta Configuration page.
#7 Of course plug in “App ID - client id” & “App Secret - client secret” into trigger node Creds.
“Whatsapp Bus Acct ID” & “Access Token” into Whatsapp Business Cloud node.
To note → App Mode: Development / Live evidently doesnt matter. The Live toggle matters for:
Facebook Login
Instagram Graph API
Requesting advanced permissions from Meta’s App Review
To note → n8n workflow of course needs to be Published or Active. Then I view Executions and start chatting
To note → my nodes pasted here have extra workflow items (teaser), but essentially you need Whatsapp chat trigger–AI Agent–Whatsapp send msg ; just to test
refs:
https://www.youtube.com/watch?v=A0OwvNOLNlw Nate Herk
Dave’s walkthrough above is solid. A few things that aren’t obvious from the current Meta dashboard:
is_echo filtering: Every message your bot sends comes back as a webhook event with "is_echo": true in the payload. If you don’t filter those out at the top of your workflow, the bot will respond to its own messages and loop. Check for messages[0].from vs your Phone Number ID, or just filter on !event.entry[0].changes[0].value.messages[0].is_echo.
App Review for production: The test phone number in your Meta App works without App Review. But once you want to message real users (numbers not in your test list), you need Advanced Access for whatsapp_business_messaging and whatsapp_business_management. That requires submitting for App Review — budget 5–10 business days. Many people get caught off guard when their bot works in testing but silently fails in production.
Webhook registration on publish: If your n8n WhatsApp trigger stops firing after a server restart or n8n update, it means the webhook registration with Meta went stale. The fix is to deactivate and reactivate the workflow — this forces n8n to re-register the webhook. Running that on a schedule (every 6–12h) prevents it entirely.
Coexistence (phone stays on the app): If your client wants to keep using WhatsApp normally on their phone while the bot runs on Cloud API, this is possible via Embedded Signup with featureType: "whatsapp_business_app_onboarding". Available globally since late 2025. Never use POST /register for this — it transfers ownership to Cloud API and blocks the app.