incident.io

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.

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

incident.io is also available as an MCP connector — 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

Create an incident.io API key

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

Open the incident.io integration

In the dashboard, go to Settings > Integrations > incident.io.

Enter the API key

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

Add a delivery rule

On the project Settings > Notifications page, add a delivery rule that routes an event type to an incident.io destination. See Route notifications.

Set up with the CLI

You can also connect incident.io with the Sazabi CLI (installed and authenticated — see CLI reference).

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:

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 page, or with the CLI (sazabi notifications delivery-rules create; see Route notifications). 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 page, add a delivery rule that routes an event type to an incident.io destination. See Route notifications.

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.

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.