Webhook configuration
A Webhook receives alerts from external systems and routes them to a schedule. A Webhook belongs to a Team and references a default Schedule, so create the Team and Schedule first.
Declarative update behavior. This resource is applied declaratively.
transformationandrouting_bindingsare not preserved when omitted. Omitting a field (or sendingnull) unbinds it. When updating a Webhook, always include the values you want to keep — otherwise existing bindings are removed.
Fields
| Field | Type | Required | Default | Notes |
|---|---|---|---|---|
name | string | Yes | — | Webhook name. Cannot be empty. |
description | string | No | "" | Free-text description. Up to 500 characters. |
auth_mode | string | Yes | — | One of standard or secure. |
is_enabled | boolean | No | false | Whether the webhook is active. A missing value is treated as false. |
default_schedule_id | number | Yes | — | The Schedule that receives alerts when no routing rule matches. Must reference an existing Schedule. |
transformation | object | No | — | Transformation rule binding. Omitting or null unbinds it. |
routing_bindings | array | No | [] | List of { routing_rule_id, priority }. Omitting or null removes all bindings. |
