01 · Glossary
What events webhooks deliver
The feed covers the lifecycle of every message.
- Incoming messages from customers
- Delivery and read statuses
- Template approval and rejection updates
- Quality rating and account changes
02 · Glossary
How a webhook works
It is a simple push, with security around it.
- You register a public URL with Meta
- Meta sends JSON events to that URL in real time
- Meta verifies your endpoint with a token before sending
- Your system must acknowledge events quickly to avoid retries
03 · Glossary
Why merchants never see webhooks
Webhooks are plumbing; the inbox is the tap.
- Providers handle webhook setup, retries, and security
- Events become conversations, badges, and automations in the inbox
- You see the result — a message arriving in the shared inbox — not the JSON
- When webhooks break, messages silently stall; that is why reliability matters
04 · Glossary
How Wutt handles webhooks
Wutt runs the webhook layer for the Meta Cloud API: verified endpoints, retry handling, and real-time delivery into the shared WhatsApp and Telegram inbox. Messages appear as they arrive, and automations trigger off the same events.
- Verified endpoints and retry handling
- Real-time delivery into the shared inbox
- Automations triggered off the same events
Last updated 5 August 2026
Common questions
If you build your own integration, yes. With a provider like Wutt, it is handled for you.
Meta retries failed deliveries for a period. Persistent failures cause missed messages — a provider monitors and recovers them.
Meta signs webhook requests, and endpoints verify tokens before accepting events. See the security page for details.
They deliver the events; automations, chatbots, and CRMs decide what to do with them.