WhatsApp Trigger not receiving real messages

Amol_Mhasalkar · December 22, 2025, 6:04am

Hi,
My WhatsApp Trigger node only receives Meta test messages, but not real incoming messages from my test (personal) phone.

Describe the problem/error/question

Works:
- “Send Test Message” from Meta → received in n8n
- Outgoing messages from n8n → WhatsApp work

Does NOT work:
- Real incoming WhatsApp messages
- n8n Executions = 0
- Meta “See Webhook Events” shows the message, but n8n never receives it

What is the error message (if any)?

I am not getting any error.

Please share your workflow

{
  "nodes": [
    {
      "parameters": {
        "updates": [
          "messages"
        ],
        "options": {
          "messageStatusUpdates": [
            "all"
          ]
        }
      },
      "type": "n8n-nodes-base.whatsAppTrigger",
      "typeVersion": 1,
      "position": [
        -192,
        -48
      ],
      "id": "b662ca4d-cc1f-47c0-ad14-20725e9284cc",
      "name": "WhatsApp Trigger",
      "webhookId": "e0421071-8c4c-491d-be20-64b7806056fc",
      "alwaysOutputData": true,
      "notesInFlow": true,
      "credentials": {
        "whatsAppTriggerApi": {
          "id": "06BcnuTAgwdUP3LB",
          "name": "WhatsApp OAuth account"
        }
      },
      "notes": "My 1 WhatsApp Workflow for since last 3 days."
    }
  ],
  "connections": {},
  "pinData": {},
  "meta": {
    "templateCredsSetupCompleted": true,
    "instanceId": "11cb63c1ba96fcae9dcfb5c5e443f920b6141ad52a940aab863243667fbb6319"
  }
} output returned by the last node

Information on your n8n setup

New Meta App → Business → WhatsApp
Using Meta sandbox test number
n8n Cloud
Workflow published
1 node: WhatsApp Trigger (On Message)

Miliaga · December 22, 2025, 8:34am

@Amol_Mhasalkar did you switch your app mode to live configuration?

See here:

Amol_Mhasalkar · December 22, 2025, 8:18pm

@Miliaga - I am doing POC and nothing developed yet to go-live. So, currently app is in development mode. I thought to take app in live mode but for that I need to submit documentation to Meta, right? I am a developer and trying to develop. Currently, I was trying to do some basic functionality test so that I can approach my client to show some demo.

I just stuck at very basic step i.e. WhatsApp Trigger on message. Note: I’ve only 1 workflow inside my account and just 1 node, that’s it.

~Amol

Wouter_Nigrini · December 23, 2025, 9:43am

Hi @Amol_Mhasalkar assuming you have done all the necessary meta business account setup etc for your whatsapp number, have you Activated your workflow in the top right corner?

Amol_Mhasalkar · December 23, 2025, 6:12pm

Hi @Wouter_Nigrini - This what I have done so far.

High‑Level Setup (Step‑by‑Step)

Here is the format you asked for:

Step 1 — Create a personal Facebook account - Done

Step 2 — Create a Meta Developer Account - Done

Step 3 — Create a Meta Business Portfolio – Done (not real business)

Step 4 — Create a Meta App – Done

Type - Business type
Add product - WhatsApp
Type - Development (not live)

Step 5 — Get WhatsApp → API Setup

Test phone number – Received from Meta
Temporary access token - done
WhatsApp Business Account ID - done

Step 6 — Add test phone numbers

1 test number provided by Meta - +1-555-195-1789
Up to 5 personal numbers registered for testing – Added my personal WhatsApp Number – done.

Step 7 — Add test recipients

Meta requires you to add the numbers you want to message.

Step 8 — Copy your Access Token + Business Account ID – Done

Step 9 — Add credentials in n8n

In n8n:

Create WhatsApp Business Cloud credentials
Paste:
- Access Token
- Business Account ID

Step 10 — Build your workflow

Use:

WhatsApp Business Cloud node (send messages) – Worked
WhatsApp Trigger node (receive messages — requires OAuth2) - Not Working
Personal WA –> send message To Test WABA –> I can see this message in WA –> API Testing –> Webhook events –> Payload
But I am not getting this message in n8n. Tried published (activated) and unpublished workflow too.
Whenever I publish my workflow, it automatically register my Webhook URL under Meta - WhatsApp - API testing automatically (that means no issue with credentials).

Turn Meta App – Live - This too failed

· Error Invalid Privacy Policy URL

You must provide a valid Privacy Policy URL in order to take your app Live.

Go to App Setting → Basic and make sure it is valid.

· Access verification

- Verify that your business is a Tech Provider.

- We review submissions and follow up within 5 days.

- To start access verification, you need to complete business verification.

- Start business verification

I am really shocked that this small setup turned nightmare for me.

Is there any way to open case n8n support? So that someone can see live on my screen?

Best Regards,

Amol

Amol_Mhasalkar · December 23, 2025, 6:20pm

@Miliaga Thanks for sharing this note. I also found this similar post.

Did I make my app live - Ans is “No”

Reason - I was just testing my n8n - WhatsApp integration so that I can show it to my prospect.

I believe Meta will do business verification before going live - Am I correct?
Let me try that if that works.

Yeah I tried and it is asking my business documentation.

Turn Meta App – Live

· Error Invalid Privacy Policy URL

You must provide a valid Privacy Policy URL in order to take your app Live.

Go to App Setting → Basic and make sure it is valid.

· Access verification

- Verify that your business is a Tech Provider.

- We review submissions and follow up within 5 days.

- To start access verification, you need to complete business verification.

- Start business verification

CarlosGerardo27 · December 28, 2025, 9:50am

If Webhook tests work in Meta but real WhatsApp messages never reach n8n, the problem is very likely that your WABA (WhatsApp Business Account) is subscribed to a DIFFERENT Meta App than the one where you configured the webhook.

This is extremely easy to miss.

Symptoms

WhatsApp “Test” button in Meta Webhooks works
You can see real messages in Meta event logs
Your webhook URL:
- is public
- accepts POST
- returns 200 OK
BUT:
- n8n never receives real messages
- No executions appear in n8n

The Hidden Cause (this is the key)

A WhatsApp Business Account (WABA) can be subscribed to multiple Meta apps, but:

Real WhatsApp messages are delivered ONLY to the webhook configured on the app that is actually subscribed to the WABA.

In our case:

WABA was subscribed to App A (a DevX / test app)
Webhook was configured on App B (our real app)
Result:
- Meta logs showed messages
- But they were being routed to another app’s webhook, not ours

The Meta UI does not make this obvious.

How to Diagnose (100% deterministic)

Identify your WABA ID

You’ll see it in webhook payloads as:

entry[0].id

Example:

2198758223867330

Check which apps are subscribed to your WABA

Run:

curl -s "https://graph.facebook.com/v24.0/WABA_ID/subscribed_apps?access_token=YOUR_TOKEN"

If you see something like:

{
  "data": [
    { "id": "2202427980234937", "name": "WA DevX Webhook Events 1P App" }
  ]
}

…and your app is NOT listed, then real messages will never reach your webhook, no matter how perfect your setup is.

The Fix (this is what actually solved it)

Generate a System User access token for YOUR app

Do not use:

Graph API Explorer token
Temporary “Getting Started” token

Instead:

Business Manager → System Users
Assign:
- Your App
- Your WABA
Generate token

Subscribe the WABA to YOUR app

curl -X POST "https://graph.facebook.com/v24.0/WABA_ID/subscribed_apps" \
  -d "access_token=SYSTEM_USER_TOKEN_FOR_YOUR_APP"

Verify it worked

curl -s "https://graph.facebook.com/v24.0/WABA_ID/subscribed_apps?access_token=SYSTEM_USER_TOKEN_FOR_YOUR_APP"

Expected result:

{
  "data": [
    { "id": "YOUR_APP_ID", "name": "Your App Name" }
  ]
}

(or multiple apps, but your app must be there).

Final Step (very important)

Make sure the webhook callback URL is configured on the SAME app that is now subscribed to the WABA.

Each app has its own webhook configuration.

Result

After subscribing the WABA to the correct app:

Real WhatsApp messages immediately started triggering n8n executions
No changes were required in:
- n8n
- reverse proxy
- webhook URL
- SSL
- permissions

Takeaway

Seeing messages in Meta logs ≠ webhook delivery

Always check /{WABA_ID}/subscribed_apps

This single endpoint would have saved days of debugging.

Hope this helps someone else

Amol_Mhasalkar · December 31, 2025, 12:45am

@CarlosGerardo27

Thanks for the steps.

Additional info: As previously localhost wasn’t exposed to internet and I thought that could be the reason Meta wasn’t reaching to me, so added following

- WSL - Ubuntu - Docker
- my own domain (from Bluehost)
- CloudFlared for DNS looks up and port forwarding
- n8n on docker
- CloudFlared for actual website

I have executed all the steps

Step 2 → It shows exactly what you showed in the example. So seems something is 101% screwed up. But where? I am still clue less …

Note: I had created multiple apps to test this scenario earlier but as of today I kept single app. Rest all apps are deleted already in last couple of weeks.

So I continued all your steps
From section → Fix → Step 3 → Worked and I see only 1 APP.

So that means setup should work yet I am not getting anything in my n8n - Trigger.

For further test

I have added WhatsApp Send message node and when I triggered test message from Webhook - Message Test → it send message internally to WhatsApp Trigger and 2nd Node reply back to me on my personal mobile properly.

Is there any way, I can I raise this with n8n support?

Sayf_ul-Basri · January 4, 2026, 1:11am

BRILLIANT! Your solution worked for me.

Thank you very much @CarlosGerardo27

Chris_Villarroel · January 4, 2026, 4:01pm

Thanks you Carlos,

I spent all my day trying things until I read your solution,

Thanks!

Oscar_Oyola · January 9, 2026, 2:49am

La respuesta es perfecta @CarlosGerardo27, dure más de 5 horas buscando la solución, yo optimice un poco de carlos para solucionar en 5 minutos

El problema es que: Los masajes salen del celular llegan a meta pero no a n8n, pero con el nodo de Send message los masajes si salen de n8n a mi celular.

paso 1: herramienta oficial de meta para identificar y solucionar el problema Meta for Business (formerly Facebook for Business)

Paso 2 : en la parte de arriba remplaza el texto: me?fields=id,name por TU_WABA_ID/subscribed_apps

TU WABA ID : es el Identificador de la cuenta de WhatsApp Business lo encuentras en tu app Meta for Business (formerly Facebook for Business)

paso 3 : verifica que los datos a la derecha correspondan y le das en enviar.

{

  "whatsapp_business_api_data": {

    "category": "Negocios",

    "link": "[https://www.facebook.com/games/?app_id=](https://www.facebook.com/games/?app_id=2202427980234937)xxxxxxxxxxx",

    "name": "WA DevX Webhook Events 1P App",

    "id": "xxxxxxxxxxxxxx"

  }

}

]

}
aquí es donde el nombre de tu aplicación debe aparecer pero, no está aparece es una aplicacion del sistema o una antigua.

Paso 4 : deja todo como esta y solo cambia el método de GET a POST y vuelve a dar en enviar y listo ….. vuelve a GET y enviar …. y problema SOLUCIONADO…..

Alejandro_Zirczy · January 15, 2026, 2:51am

@Amol_Mhasalkar Please let me know if you already have a solution. You’re not the only one — this has started to be a nightmare for me as well. I’ve invested around 15 hours without success. I tried the suggestions from the people in this chat, but I’m still not receiving messages on WhatsApp from n8n, and I’m not seeing any error messages either. Thanks in advance!