# Other Zendesk events

Zendesk sends 2 other Zendesk events: `zen:event-type:access_log.created` and `zen:event-type:omnichannel_config.omnichannel_routing_feature_changed`. Every event here can also reach agents as an MCP event through Hookdeck: [MCP events](https://hookdeck.com/webhooks/zendesk/mcp-events).

These pages list the events a webhook subscribed to Zendesk events receives. A webhook connected to a [trigger or automation](https://developer.zendesk.com/documentation/webhooks/creating-and-monitoring-webhooks/#connecting-a-webhook-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](https://developer.zendesk.com/api-reference/integration-services/inbound-webhooks/inbound_webhooks/).

Agent skill: `npx skills add hookdeck/webhook-skills --skill zendesk-webhooks` ([details](https://hookdeck.com/webhooks/zendesk/skill))

> Independent reference generated from hookdeck/webhook-registry (commit a24c8d9, 19 Nov 2026). [Zendesk's official docs](https://developer.zendesk.com/api-reference/event-connectors/webhooks/webhook-event-types/).

[Overview](https://hookdeck.com/webhooks/zendesk) · [Webhook events (142)](https://hookdeck.com/webhooks/zendesk/events) · [MCP events](https://hookdeck.com/webhooks/zendesk/mcp-events) · [Verify signatures](https://hookdeck.com/webhooks/zendesk/verify) · [Production guide](https://hookdeck.com/webhooks/zendesk/guide-duplicates-ordering-retries-timeouts) · [Agent skill](https://hookdeck.com/webhooks/zendesk/skill)

## zen:event-type:access_log.created

Confidence: documented · Schema: from Zendesk docs (example)

New access log entries are recorded

Identified by: type in the body; none on trigger or automation webhooks · Object: `access_log`

```json
{
  "account_id": 12514403,
  "detail": { … },
  "event": { … },
  "id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
  "time": "2024-08-15T14:23:45Z",
  "type": "zen:event-type:access_log.created",
  "zendesk_event_version": "2022-11-06",
  "subject": "zen:access_log:01J5M2QGXR3KZ8N4BVWYH6T9PA"
}
```

Trimmed sample. Full payload: [View as JSON](https://hookdeck.com/webhooks/zendesk/events/zen-event-type-access-log-created.json)

| Key field | Type | Example |
|---|---|---|
| `id` | string | `a1b2c3d4-e5f6-7890-abcd-ef1234567890` |
| `type` | string | `zen:event-type:access_log.created` |
| `account_id` | integer | `12514403` |

[View as JSON](https://hookdeck.com/webhooks/zendesk/events/zen-event-type-access-log-created.json)

## zen:event-type:omnichannel_config.omnichannel_routing_feature_changed

Confidence: documented · Schema: from Zendesk docs (example)

Omnichannel routing is switched on or off

Identified by: type in the body; none on trigger or automation webhooks · Object: `omnichannel_config`

```json
{
  "account_id": 2,
  "detail": { … },
  "event": { … },
  "id": "01GX79ST1QX01C889XV42S2J5Z",
  "subject": "zen:account:2",
  "time": "2023-05-10T23:31:58.642630335Z",
  "type": "zen:event-type:omnichannel_config.omnichannel_routing_feature_changed",
  "zendesk_event_version": "2022-11-06"
}
```

Trimmed sample. Full payload: [View as JSON](https://hookdeck.com/webhooks/zendesk/events/zen-event-type-omnichannel-config-omnichannel-routing-feature-changed.json)

| Key field | Type | Example |
|---|---|---|
| `id` | string | `01GX79ST1QX01C889XV42S2J5Z` |
| `type` | string | `zen:event-type:omnichannel_config.omnichannel_routing_feature_changed` |
| `account_id` | integer | `2` |

[View as JSON](https://hookdeck.com/webhooks/zendesk/events/zen-event-type-omnichannel-config-omnichannel-routing-feature-changed.json)

---

Not affiliated with Zendesk. Facts are compiled from public sources and linked inline. [View as JSON](https://hookdeck.com/webhooks/zendesk.json) · [Report a correction](https://hookdeck.com/contact)
