WhatsApp Trigger receives no data while “Start listening” is active (self-hosted n8n)

Questions
1

Hi everyone,
I’m using n8n self-hosted with the WhatsApp Trigger node to receive incoming WhatsApp messages.

The WhatsApp Cloud setup is complete and working (webhook verified, events subscribed, test number configured). However, when I start listening on the WhatsApp Trigger and send a message, nothing appears in the node output.
Problem

When I send a WhatsApp message:

No error in Meta

No error in n8n

No incoming data appears in the WhatsApp Trigger output

The workflow simply stays empty while listening.

1 Like
2

HI @msanta7 ,

Welcome the community,

So about your whatsApp trigger not receiving messages, can you confirm if all of these are setup correctly.

  • Webhook URL Mismatch

  • Workflow Must Be Active

  • Webhook Verification and Message Delivery

  • WhatsApp Event Subscriptions

  • Phone Number Configuration

  • and finally network Issues
3

Welcome to the n8n community @msanta7 !

If the WhatsApp Trigger never shows incoming messages even though your Meta setup looks correct, the issue is usually with how the webhook and subscriptions are registered, not with your workflow logic.

What to check

  1. Workflow must be active/published
    The WhatsApp Trigger only receives real messages when the workflow is activated in n8n. If it is just running in manual mode, Meta will not send real webhook events.

  2. WhatsApp number must be subscribed to your Meta App
    Your phone number (test or production) needs to be subscribed to your Meta app so that real messages are forwarded to the trigger. If it is not subscribed, Meta can log messages internally but n8n never gets them.

  3. Ensure you use the correct credentials
    The WhatsApp OAuth credential for the trigger must be valid and match what Meta expects. If tokens or IDs change or expire, the webhook may not work.

  4. Test messages vs real messages
    Meta’s internal “Send Test Message” feature may work while real messages do not. This often points to missing subscriptions for real message events.

  5. Recreate the trigger if needed
    Sometimes deleting and re-adding the WhatsApp Trigger node and activating the workflow again forces Meta to register a fresh webhook.

If you verify the workflow is active, the number is subscribed to your Meta app, and your credentials are correct, real incoming WhatsApp messages should start appearing in the WhatsApp Trigger output. Hope this helps