ZEzernio
Webhook Events

Automation alert resolved event

An open alert ended; reason says which way.

Reasons

Its conditions cleared, a pause or reactivation applied, the rule changed, or nothing checked the object for 7 days.

postWebhookautomation.alert.resolved

Payload

idstring required

Stable webhook event ID: the dedupe key, also sent as the X-Zernio-Event-Id header and identical on every retry and redelivery.

testboolean

Always true when present: only a sample sent by POST /v1/webhooks/test with an event carries it. Real deliveries never do.

event'automation.alert.opened' | 'automation.alert.escalated' | 'automation.alert.resolved' required
accountIdstring required

The connected account the automation acts on.

checkIdstring required

The check that moved the alert.

timestampstring date-time required

Example payload

{
  "profiles": [
    {
      "externalId": "tenant_42"
    }
  ]
}

Response

Webhook received

Changes

Webhooks have no change history: a webhook is keyed by its event name rather than a path and method, so no recorded change can name it.