- Community
- Question
Phone Number ID: 1093280623874834 WABA ID: 1604198601036475 App ID: 970680308935262
Problem: Incoming WhatsApp messages are received by Meta (messages show double check ✓✓ and WABA stats show "mensajes recibidos" increasing) but webhook POST events are NEVER triggered to our server.
Verified configuration: - App mode: LIVE - Webhook subscription: active, object=whatsapp_business_account, field=messages, callback_url=https://bikepassion-ana-production.up.railway.app/webhook - App subscribed to WABA: confirmed - Phone status: CONNECTED, quality_rating=GREEN, code_verification_status=VERIFIED - webhook_configuration on phone number shows correct URL - Webhook GET verification works correctly (200 OK with hub.challenge)
The webhook server receives GET verifications from Meta but NEVER receives POST requests when users send WhatsApp messages to the business number.
Steps reproduced multiple times over 2 days. No POST requests appear in server logs despite messages being delivered (✓✓).
Any idea what could prevent Meta from sending webhook POST events for this specific number/WABA?
Additional clue: When sending WhatsApp messages to +573150657376, the chat shows ONLY the phone number, NOT the business name "Bike Passion Training Center". This suggests the number may not be properly recognized as a Cloud API business number by WhatsApp clients, even though the API shows status=CONNECTED and verified_name="Bike Passion Training Center".
Facing a similar issue with the test WhatsApp number. Messages from my whitelisted number are being delivered (double tick, stats incrementing), but no webhook is firing — so my app never generates a response.
Webhook itself works fine: when I manually trigger it from the webhook subscription page, Railway logs show the correct payload. But messages sent from my phone to the test number trigger nothing.
This happens both with and without the app published. Production number not connected yet.
Hey - I managed to figure this out. Its working for me now.
So whats happened is that when we tested the webhook - meta only configured the send messages request. It never actually subscribed our wa business account to the webhook.
in order to subscribe to the webhook - go to postman and call the waba cloud graph api. the command to look for in the docs is webhook subscription.
This is the exact api to call - no auth needed to subscribe to the webhook. just replace the waba id https://graph.facebook.com/v25.0//subscribed_apps
this should subscribe you, and after that you can send a message from your phone. !! let me know if this worked for you.
I made those changes but it didn't work