Webhooks and Event Subscriptions

Webhooks and event subscriptions are the VibeControls concept for letting other systems react to what happens in your fleet. A webhook pairs a destination URL with a set of events, such as an agent going offline, a vibe completing or an action failing, so a chat channel can be notified, a CI workflow can be dispatched or an internal automation can start without anyone watching the dashboard.

Integrations like these are often glued together with polling scripts and tokens kept in someone's shell history, and when a delivery starts failing nobody notices. The concept keeps every subscription in one list with its state and delivery record, lets each one be tested and paused, and signs payloads so receivers can check that a request really came from the workspace.

The webhooks list shows how many webhooks are active, with a search field, grid and list views, a status filter and a quick filter for webhooks with errors. Each card has an icon for the destination, a name, an active, degraded or inactive badge, the target URL and chips for its subscribed events, with Test, an enable switch and delete. A footer records total deliveries and the last success or failure, including the HTTP status of a failed call. The New Webhook dialog collects a name, a URL and an optional secret, a scrollable checklist of built-in agent, vibe and session events, custom events in a namespace and event format, a signing key used to sign payloads with an HMAC-SHA256 signature header, and an agent scope that limits the webhook to selected agents or leaves it open to all.

Webhooks sit under Settings next to the workspace defaults and are designed to carry news outward from the rest of VibeControls. Sessions, targets, actions, decks and templates produce the events, the audit log records the operations behind them, and webhooks pass them on to the chat, CI and automation tools a team already relies on.