Webhook Events

Automation action applied event

An automation changed something, such as an ad set paused or a budget raised.

Payload notes

previous and target carry the value before and the value set. Each action sends one event; dedupe on id, which stays the same if the event is sent again.

postWebhookautomation.action.applied

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.action.applied' | 'automation.action.failed' | 'automation.action.unknown' required

accountIdstring required

The connected account the automation acts on.

checkIdstring required

The check that recorded the action.

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.