Event families
Each endpoint chooses which of ten families it receives. Wagent's own control events are always sent.
The ten families#
| Family | What it covers | New endpoints |
|---|---|---|
messages | new, edited, deleted, ticks | On |
statuses | stories | Off |
chats | archived, muted, pinned | On |
contacts | added, renamed | On |
groups | members, settings | Off |
labels | added, removed | On |
presences | typing, online | Off |
calls | incoming calls | Off |
channel | connection, QR | On |
users | login, logout | On |
Presences start off and may need a per-chat subscription on the WhatsApp provider side before they arrive.
Always sent#
draft.created, approval.requested, approval.decided, rule.changed, agent.paused and agent.revoked are sent to every endpoint they concern, whatever its families. Agent pause, revoke and an agent's own rule changes go only to that agent's endpoint.
The API reference lists every event type with its family and payload.
Chats you cannot see#
An event about a chat is checked against the endpoint agent's rights on every attempt. If the chat is hidden, outside the agent's history window or the agent is paused, the event is skipped, never sent.