> ## Documentation Index
> Fetch the complete documentation index at: https://docs.sazabi.com/llms.txt
> Use this file to discover all available pages before exploring further.

# incident.io

> Connect incident.io so Sazabi can route issues to an incident.io alert source.

## Supported capabilities

MCP connectorCore integration

* **MCP connector**: [incident.io](https://docs.sazabi.com/catalogs/mcp-connectors/incident-io.md) — Give the Sazabi agent tools to browse incidents, alerts, and on-call schedules from your incident.io organization.
* **Core integration**: [incident.io](https://docs.sazabi.com/catalogs/integrations/incident-io.md#core-integration) — Connect incident.io so Sazabi can route issues to an incident.io alert source.

Each connection method has its own setup and permissions. Connecting one method does not enable the others.

## Core integration

## About

Connecting incident.io lets Sazabi route issues to an incident.io **alert source**, so they enter your incident.io alerting and escalation. incident.io is an **incident** integration and a shared [notification channel](https://docs.sazabi.com/guides/detect/notifications.md).

Sazabi triggers and resolves incident.io alerts as an issue opens and closes.

incident.io is also available as an [MCP connector](https://docs.sazabi.com/catalogs/mcp-connectors/incident-io.md) — a separate way to give the agent incident.io tools.

## Prerequisites

* An incident.io account and an **API key**.
* Organization admin access in Sazabi.

## Set up in the dashboard

**Step 1**

### Create an incident.io API key

In incident.io, create an API key with permission to manage alert sources
and alerts. Copy it.

**Step 2**

### Open the incident.io integration

In the dashboard, go to [**Settings > Integrations > incident.io**](https://app.sazabi.com/settings/integrations/incident-io).

**Step 3**

### Enter the API key

Paste the key and connect. Sazabi validates it and discovers your alert
sources so you can route issues to one.

**Step 4**

### Add a delivery rule

On the project [**Settings > Notifications**](https://app.sazabi.com/settings/project-notifications) page, add a delivery rule that
routes an event type to an incident.io destination. See
[Route notifications](https://docs.sazabi.com/guides/detect/notifications.md).

## Set up with the CLI

You can also connect incident.io with the [Sazabi CLI](https://docs.sazabi.com/reference/cli.md) (installed and authenticated — see [CLI reference](https://docs.sazabi.com/reference/cli/integrations.md)).

incident.io is an API-key provider, so pass its API key as the `apiKey` credential. Read the key from an environment variable rather than pasting it inline:

```bash theme={"system"}
export INCIDENT_IO_API_KEY=...   # your incident.io API key
sazabi integrations connect incident_io \
  --credentials "{\"apiKey\":\"$INCIDENT_IO_API_KEY\"}"
```

Then add a delivery rule so issues reach incident.io — from the project [**Settings > Notifications**](https://app.sazabi.com/settings/project-notifications) page, or with the CLI (`sazabi notifications delivery-rules create`; see [Route notifications](https://docs.sazabi.com/guides/detect/notifications.md#delivery-rules)). Run `sazabi integrations list` to confirm the connection, or `sazabi integrations providers --json` to see each provider's credential fields.

## Notifications

Use incident.io as a delivery destination for issue and system events: on the project [**Settings > Notifications**](https://app.sazabi.com/settings/project-notifications) page, add a delivery rule that routes an event type to an incident.io destination. See [Route notifications](https://docs.sazabi.com/guides/detect/notifications.md).

## Incidents

Sazabi opens and resolves alerts on your incident.io alert source as issues fire and clear, so a problem enters incident.io's alerting and escalation and the alert closes when the issue resolves. Route issues to incident.io with a delivery rule — see [Route notifications](https://docs.sazabi.com/guides/detect/notifications.md).

## Verify

With a delivery rule pointing at an incident.io destination, trigger a test issue and confirm an alert appears on the incident.io alert source within a minute. Resolve the issue and confirm the incident.io alert resolves.

## Troubleshooting

**No alert on the source** — Confirm the delivery rule names both the event type and the incident.io destination, and that no condition excludes the issue.

**Connection shows needs attention** — The API key may have been revoked or lack alert-source permissions. Create a new key and reconnect.

## Further reading

> [card] [Route notifications](https://docs.sazabi.com/guides/detect/notifications.md)
>
> Route issues to incident.io with delivery rules.

> [card] [Integrations](https://docs.sazabi.com/catalogs/integrations.md)
>
> Browse the full integration catalog.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.