WhatsApp accounts
0Sources that can trigger account-scoped webhooksAutomations
Route WhatsApp events outward
Attach tenant or account-scoped webhook endpoints for message and session events.
Contacts
0Audience records that can drive inbound eventsCampaigns
0Outbound actions that can trigger delivery webhooksWebhooks
0Tenant event destinations with retry supportAutomations
Webhook engine
Realtime routing
Operational
Webhook guidance & best practices
Keep endpoints idempotent, verify signatures, and expect retries whenever the downstream system is unavailable.
Use account-scoped endpoints when one integration only cares about a single number; use tenant-scoped endpoints to power a single automation layer across all accounts.
Registered endpoints
Active routes, event subscriptions, and scope visibility for the current tenant.
Delivery model
RelayLoop stores payloads, retries failed deliveries, and keeps the event subscription separate from account session state.
| Signal | Meaning |
|---|---|
| message.received | Inbound message or attachment from a customer conversation. |
| message.delivered / message.read | Outbound acknowledgements for sent messages and campaign traffic. |
| session.connected / session.disconnected / session.qr_required | Worker-level account lifecycle events that can wake internal or customer systems. |