---
title: "Sazabi"
description: "Start automations from Sazabi issues and give agents access to issues, logs, and investigations."
canonical_url: "https://hoplite.sh/docs/integrations/sazabi"
markdown_url: "https://hoplite.sh/docs/integrations/sazabi.md"
---

# Sazabi
URL: /docs/integrations/sazabi
LLM index: /llms.txt
Description: Start automations from Sazabi issues and give agents access to issues, logs, and investigations.
Related: /docs/integrations, /docs/agent/tools

# Sazabi

Connect Sazabi under **Settings → Integrations** to start automations when Sazabi triggers or resolves an issue, and to let agents investigate production issues with `sazabi_control`. The tool is available only while the current Hoplite workspace has a Sazabi connection.

## Setup

1. In Sazabi, create an organization secret key under **Settings → Secret keys**. Public ingestion keys, user credentials, and partner credentials aren't supported.
2. As a Hoplite workspace administrator, open the Sazabi integration and paste the secret key into the connection form. Hoplite validates the key with Sazabi before storing it encrypted. Don't paste keys into a thread.
3. Hoplite registers a signed webhook in Sazabi named **Hoplite automations** and subscribes it to every project in the organization. The settings page shows how many projects are delivering; use **Send test** to confirm Sazabi can reach Hoplite.
4. Keep issue changes disabled for read-only access, or enable them when agents should be able to triage issues with approval.

The connection grants agents access to the connected Sazabi organization's projects. It isn't restricted to one repository, and it doesn't create a separate Sazabi project binding. Use an organization whose data is appropriate for members of this Hoplite workspace.

## Agent operations

Agents can inspect the connection, list projects, search and read issues, query logs, and read investigation threads and messages. Project-scoped operations use a Sazabi project ID from the project list. List operations support bounded pages and cursors.

When issue changes are enabled, agents can resolve, reopen, ignore, mute, and unmute issues. Each change requires approval. After issue changes are disabled, subsequent runs advertise only read operations, and further writes are blocked during execution even in an already-running thread.

Disconnecting removes the tool from subsequent runs and blocks further calls from active runs. Rotate a key by reconnecting with its replacement; an invalid replacement doesn't remove the working connection.

## Automations

Add a **Sazabi** trigger to any automation, or start from the **Sazabi issue triage** template on the Automations page:

| Trigger | Fires when |
| --- | --- |
| `sazabi.issue.triggered` | Sazabi opens an issue in any subscribed project |
| `sazabi.issue.resolved` | Sazabi resolves an issue |

Each delivery starts one thread per matching automation, across every Hoplite project that has one. Redeliveries of the same Sazabi event don't start another thread. Filter on `issue.severity` (`low`, `medium`, `high`, `critical`), `issue.name`, `issue.status`, `issue.component.name`, `issue.rootCause`, `project.name`, or `project.id`. The thread receives the issue, its component, Sazabi's root-cause notes, and up to 20,000 characters of the issue report, all treated as untrusted input.

Sazabi subscriptions are per project. After you create a Sazabi project, select **Resync** in the Sazabi settings so its issues are delivered too. Turning delivery off removes the webhook from Sazabi; enabled Sazabi automations can't be saved while delivery is off.

Hoplite verifies the `X-Sazabi-Signature` HMAC on every delivery and rejects stale timestamps, unknown endpoints, and events from a different Sazabi organization. Rotating the secret key keeps delivery running; connecting a key from a different Sazabi organization replaces the webhook. Disconnecting removes it.

This integration doesn't ingest telemetry.

## API reference

The integration uses Sazabi's [public REST API](https://docs.sazabi.com/reference/api) at `https://api.sazabi.com/v1`, following its [published OpenAPI contract](https://api.sazabi.com/openapi.json). Requests use the encrypted organization secret on the server; the browser and model never receive it.

## Sitemap

Sitemap discovery is not enabled for this deployment.