The third-party integrations Anvil ships out of the box won't cover everything — internal dashboards, custom issue trackers, data warehouses, CI/CD pipelines, or homegrown alerting tools. Webhooks would give you a generic way to have Anvil notify any HTTPS endpoint when something happens, so you can wire it into the tools your team already runs without waiting for a first-class integration.

You'd configure a webhook by giving it a name, a URL, and a list of events to subscribe to — new errors, regressions, resolved errors, error spikes, new releases, published releases. When one of those events fires, Anvil POSTs a JSON payload with consistent structure (organization, project, event type, and event-specific data) and an optional HMAC signature so your receiver can verify the request really came from Anvil. You can add custom headers for authentication, set a shared secret, and test the webhook against your endpoint before saving.

Because webhooks can fail for reasons outside Anvil's control, failed deliveries retry with exponential backoff and a delivery log shows recent requests, their status codes, response times, and retry history. If a webhook fails repeatedly it's auto-disabled and admins are notified, so broken integrations don't quietly stop working. The feature is aimed at teams with custom tooling — Anvil's own built-in integrations (Jira, Linear, Slack, etc.) cover the common cases, and webhooks are the escape hatch for everything else.

What we're thinking: