Configure webhooks

A webhook is a shared notification delivery channel: Sazabi POSTs notification payloads to an HTTPS endpoint you run, the same way it delivers to Slack or email. Sazabi does not define a separate set of webhook events — any notification type can be routed to a webhook with delivery rules, so the webhook event types are exactly the notification types. Setting one up takes a few minutes. You need owner or admin access.

Manage webhook endpoints under Settings > Webhooks.

Create a webhook endpoint

1. Go to Settings > Webhooks and add an endpoint with your HTTPS URL. The URL must be HTTPS and publicly reachable.
2. Optionally add an authentication header — a header name and value that Sazabi sends on every delivery so your endpoint can verify the request came from Sazabi. You should see the endpoint appear as active once saved.

Creating and managing webhook endpoints is dashboard-only — the CLI has no sazabi webhooks command. Once an endpoint exists, the CLI can manage the delivery rules that route notifications to it: sazabi notifications delivery-rules lists, creates, and deletes routing rules whose destinations include your webhook (verify against /reference/cli).

Choose which notifications are delivered

Adding an endpoint does not by itself send anything. Choose which notifications go to it in the project's notification settings — the same delivery rules that route to Slack and other channels. See Route notifications for how delivery rules work. Webhook-routable notification types are listed in Notification types.

Secure the endpoint

Sazabi authenticates deliveries with the optional authentication header you configured: it sends your header name and value on every request, and your endpoint rejects any request that lacks it. Store the header value as a secret. Because the endpoint is public, also confirm the payload matches an event you expect before acting on it.

Retries and auto-disable

Sazabi records the outcome of each delivery. If an endpoint fails repeatedly, Sazabi tracks the consecutive failures and can automatically disable the endpoint, with the reason shown in the dashboard. Re-enable it after fixing the endpoint.

Verify

1. On the endpoint in Settings > Webhooks, use Send test.
2. Sazabi POSTs a test payload to your URL. Your endpoint should receive it and return a 2xx status.
3. The dashboard shows the delivery as successful. If it fails, confirm the URL is reachable over HTTPS and that your endpoint returns a 2xx.

Further reading