Skip to main content

Runbook Hooks

The recommended way to integrate Hoop with external systems — SIEMs, alerting pipelines, audit platforms — is through runbook hooks. Hook scripts live in your runbooks git repository and execute automatically when session events occur, with the full event payload available as an environment variable.
Runbook hooks require version 1.36.11+ and the Runbooks plugin configured with a git repository.

How It Works

Place hook scripts in a hoop-hooks/ directory in your runbooks repository. Hoop executes the matching script automatically when the corresponding event fires, injecting the event payload as HOOP_RUNBOOK_HOOK_PAYLOAD.

Enabling Hooks

Set GIT_HOOK_CONFIG_TTL in your runbooks plugin configuration. This activates hook support and controls how long (in seconds) the configuration is cached between git fetches. See the Runbooks configuration guide for full setup instructions.
Use a higher TTL if your hook scripts change infrequently — this reduces the number of requests to your git server.

Event Payload

The HOOP_RUNBOOK_HOOK_PAYLOAD environment variable contains a JSON object with session context. The event_session_open or event_session_close attribute is populated depending on which event fired.

Forwarding Events to a SIEM

The example below shows a session-close hook that forwards the event payload to an external endpoint — a SIEM, a logging pipeline, or any HTTP receiver.
For more on writing and configuring runbooks, see the Runbooks configuration guide.

Svix Integration

The Svix webhook integration is deprecated. Use Runbook Hooks instead.

Prerequisites

Configuring

Log in and create the webhooks plugin:
Then enable it for a specific resource role:

Dashboard

Open the Svix dashboard to configure endpoints and subscriptions:
The dashboard is only available with Svix SaaS and can only be opened by administrators.
To view activity, interact with any resource role. The Message Logs link shows all resource role events.

Adding Endpoints

Click Endpoints to route messages to your SIEM.
Adding endpoints to a self-hosted Svix instance requires the Svix CLI or API.
Use Svix Play to test endpoints before wiring up production systems.

Event Types

Refer to the Event Catalog link in the dashboard for event definitions.

Consuming Webhooks

Refer to the Svix documentation for guidelines on secure verification and consumption of webhooks.

Svix Self-Hosted

For self-hosted installations, manage Svix resources directly via the Svix CLI or the Hoop CLI wrappers.

Event Types

Create event types with:

Endpoints

Messages