Webhook event types
When to use this guide: You need to know which Sync Monitoring events fire today, when they fire, and which names are reserved. Inbound SEP event types on Sources are separate — this page is for product Webhooks.
Active events (Sync Monitoring)
Section titled “Active events (Sync Monitoring)”| Event | Fires when |
|---|---|
sync.failed | A source→CRM sync transitions from healthy to failing after 3 consecutive failed syncs for that source×connection pair — one alert per incident, not every failed job |
sync.recovered | A previously failing source→CRM sync starts succeeding again (failing→healthy) |
test.ping | Delivered only by POST /api/v1/webhooks/:id/test — not a subscription type |
Empty or omitted enabledEvents on a webhook means all currently active events (sync.failed and sync.recovered). It does not include reserved names or test.ping.
Reserved event names
Section titled “Reserved event names”These names are held in the namespace. Subscribing returns 400 with the list of available types. They are not delivered yet:
connection.created,connection.degraded,connection.restored,connection.removedblocklist.entry_added,blocklist.sync_failed,blocklist.sync_recovereddestination.forward_failed,destination.forward_recovered- Provisional record-write names such as
contact.created/company.created(naming may change before they ship)
Do not invent shipping timelines for reserved events.
