Webhooks

Organization Settings > Integrations > Webhooks pushes platform events to the systems your team already watches: the SIEM, the pager, the ops channel.

Add a destination URL and pick the event classes it should receive: swarm completions and failures, gate decisions, budget thresholds. Each webhook gets a signing secret shown once at creation, so your receiver can verify every delivery actually came from the platform. From then on the events your audit stream already records also land where your on-call actually looks, and a Test button proves the wiring before the first real event fires.

The Webhooks tab with two configured destinations: a PagerDuty endpoint receiving budget and swarm events and a Slack endpoint receiving swarm and gate events, each with its event chips, an On toggle, and Test and Delete actions
A budget breach pages the on-call and a failed gate lands in the security channel, without anyone watching a dashboard. The event chips on each row are the contract.