Hey n8n community! I’m struggling with a WhatsApp webhook setup for multiple workflows and could use your expertise. Here’s my setup: I have two n8n workflows (w1 for num1, w2 for num2), each using separate Meta Business Apps (app1 and app2). For incoming messages, I’m using the WhatsApp OAuth API node (with Client ID/Secret), and for outgoing, the WhatsApp API node (with Access Token/Business ID).
The first workflow (w1) works perfectly, which now I configured its callback URL (POST production URL) and verify token (A dummy text because i was not able to find one in n8n neither in json nor in n8n UI) in Meta without issues. But for the second workflow (w2), Meta throws: “The callback URL or verify token couldn’t be validated” when I try to add its webhook URL (using the same steps that worked for w1). Even weirder: messages to num2 sometimes trigger w1 instead of w2, suggesting cross-wiring between workflows.
Here’s what I’ve tried:
- Double-checked that webhook URLs and tokens match exactly in n8n/Meta.
- Both the workflows uses separate apps and numbers..
- Ensured both workflows are active during verification attempts.
- Confirmed HTTPS accessibility via ngrok (testing URLs in a browser works).
- Recreated credentials in Meta multiple times.
My questions:
- Why would verification work for one app but fail identically for the second?
- Could Meta throttle webhook registrations from the same IP? (I’m hosting n8n locally).
- Any proven fixes to isolate workflows and resolve verification failures?
Would massively appreciate troubleshooting tips or success stories with multi-number WhatsApp setups!