Zendesk messaging webhook events
Zendesk sends 3 messaging events: zen:event-type:messaging_ticket.message_added, zen:event-type:chat_ticket.member_joined and zen:event-type:chat_ticket.listening_agents_changed.
These pages list the events a webhook subscribed to Zendesk events receives. A webhook connected to a trigger or automation sends the request you define, a JSON or XML body or URL parameters, with no type field but the same signature headers. To send events into Zendesk instead, see ZIS inbound webhooks.
Every event here can also reach agents as an MCP event through Hookdeck: MCP events →
zen:event-type:messaging_ticket.message_added
documented from Zendesk docs (example)
zen:event-type:messaging_ticket.message_added Message is posted in a messaging conversation
Identified by type in the body; none on trigger or automation webhooks
Resource messaging
{
"account_id": 21825834,
"detail": { … },
"event": { … },
"id": "01JQMQH83YNAKWSWJ8B1QH2NSC",
"subject": "zen:ticket:141",
"time": "2025-02-11T14:32:05.254571515Z",
"type": "zen:event-type:messaging_ticket.message_added",
"zendesk_event_version": "2022-11-06"
} Key fields
| Field | Type | Example |
|---|---|---|
id | string | 01JQMQH83YNAKWSWJ8B1QH2NSC |
type | string | zen:event-type:messaging_ticket.message_added |
account_id | integer | 21825834 |
Full schema: 17 fields.
zen:event-type:chat_ticket.member_joined
documented from Zendesk docs (example)
zen:event-type:chat_ticket.member_joined Someone joins a chat conversation
Identified by type in the body; none on trigger or automation webhooks
Resource messaging
{
"account_id": 18168347,
"detail": { … },
"event": { … },
"id": "01JQ5PFR38WW2P4XKPMG611Y5W",
"subject": "zen:ticket:19223",
"time": "2025-02-06T10:18:42.956868Z",
"type": "zen:event-type:chat_ticket.member_joined",
"zendesk_event_version": "2022-11-06"
} Key fields
| Field | Type | Example |
|---|---|---|
id | string | 01JQ5PFR38WW2P4XKPMG611Y5W |
type | string | zen:event-type:chat_ticket.member_joined |
account_id | integer | 18168347 |
Full schema: 13 fields.
zen:event-type:chat_ticket.listening_agents_changed
documented from Zendesk docs (example)
zen:event-type:chat_ticket.listening_agents_changed Set of agents listening to a chat is updated
Identified by type in the body; none on trigger or automation webhooks
Resource messaging
{
"account_id": 23588097,
"detail": { … },
"event": { … },
"id": "01JQ5PMCJV44CQKA25BY01FMQJ",
"subject": "zen:ticket:7184",
"time": "2025-03-07T00:57:00.173282Z",
"type": "zen:event-type:chat_ticket.listening_agents_changed",
"zendesk_event_version": "2022-11-06"
} Key fields
| Field | Type | Example |
|---|---|---|
id | string | 01JQ5PMCJV44CQKA25BY01FMQJ |
type | string | zen:event-type:chat_ticket.listening_agents_changed |
account_id | integer | 23588097 |
Full schema: 13 fields.
Route Zendesk events by type.
Event Gateway receives every Zendesk delivery and filters and routes it by event type, so each service gets only the events it handles.