Typebot doesn’t reply to inbound messages even though WhatsApp Cloud API integration looks OK
Hi folks, looking for help. I integrated WhatsApp Cloud API with Typebot and everything looks good on the Meta side: webhook points to the Typebot Callback URL, verify token matches Typebot, I clicked Verify & Save, the messages (v23.0) field is subscribed, and the webhook Test returns HTTP 200. I can also open the 24-hour window with a template—API returns wamid and accepted:
----------------------------
POST /v23.0/{PHONE_NUMBER_ID}/messages
Authorization: Bearer {ACCESS_TOKEN}
Content-Type: application/json
{
"messaging_product": "whatsapp",
"to": "+55DD9XXXXXXX",
"type": "template",
"template": { "name": "saudacao_teste", "language": { "code": "pt_BR" } }
}
----------------------------
On Typebot, WhatsApp integration is ON, I’m using the sender’s Phone number ID, the same Access Token as in the tests, the bot is Published, and I tested triggers both as Start on every message and User message → Contains → “menu”.
Behavior: the template arrives (OK), I reply “menu”, and the bot doesn’t answer. Since Meta’s webhook test returns 200 and triggers look correct, it seems the inbound messages event isn’t being processed by Typebot. Has anyone seen this? Could this be an issue in Typebot’s WhatsApp handler/routing? If you can check inbound webhook logs, that would help—Meta side appears fine.
2 Replies
I’m experiencing the same issue on my side — inbound messages aren’t being processed by Typebot even though the Cloud API setup and webhook tests return OK.
@Vanessa., have you had any updates or found a solution since posting this?