Describe the problem/error/question
Hello everyone,
I am facing critical difficulties receiving incoming message logs (payloads) in my n8n instance when using the WhatsApp webhook trigger. This issue appears to be specific to new applications created in the Meta for Developers dashboard.
1. 
Context and Successful Setup
I have followed all standard steps for the WhatsApp Business Cloud API (WABA) integration, and the webhook configuration appears correct:
| Step | Configuration | Status |
|---|---|---|
| A. Initial Verification | The webhook was successfully verified in Meta using the n8n URL and returning the {{ $json.query['hub.challenge'] }}. (Verify Token) |
 Correct |
| B. Event Subscription | I am subscribed to the messages field in the Webhooks configuration. |
Correct |
| C. Meta’s Internal Test | When using the “TEST” function within Meta’s Webhooks section, the content is correctly received by n8n. | Correct |
| D. Meta Logs | The incoming message payload is registered and displayed correctly in Meta’s Webhook Event logs. | Correct |
2. 
The Problem (Symptom)
Despite all testing showing success within Meta’s ecosystem, when I set the n8n trigger to listen and send a real test message to the associated WhatsApp number, no execution loads in n8n. The connection fails outside of Meta’s testing environment.
3. 
Suspected Cause: Meta Dashboard Change
I’ve noticed a crucial change between old and new Meta applications that may be causing this issue. (I am attaching screenshots of both interfaces for reference).
| App Version | API Configuration Field | Functionality Status |
|---|---|---|
| Old Apps | Configure API | Working perfectly (Logs received in n8n) |
| New Apps | Test API | Not working (No logs received in n8n) |
| Old Apps |
|---|
| New Apps |
|---|
Furthermore, I recall the warning from Meta stating:
“Apps will only be able to receive test webhooks sent from the panel while they are unpublished. No production data, including that of the app admins, developers, or testers, will be delivered unless the app has been published.”
The key issue is that even after publishing the new application to Production mode, the problem persists, and messages are not reaching n8n.
4. 
Request to the Community
Has anyone solved this connection failure between the new Meta applications (using the ‘Test API’ scheme) and n8n?
Is there an extra configuration step, permission (e.g., specific WABA access), or a known bug related to the new Meta dashboard structure that I might be missing?
Any guidance or shared experience would be highly appreciated!
Thank you,
Information on your n8n setup
- n8n version: 1.121.3
- Database (default: SQLite):
- n8n EXECUTIONS_PROCESS setting (default: own, main):
- Running n8n via (Docker, npm, n8n cloud, desktop app): Hostinger
- Operating system: