> ## 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.

# PagerDuty

> Connect PagerDuty so Sazabi can route issues to your services as PagerDuty alerts.

## Supported capabilities

MCP connectorCore integration

* **MCP connector**: [PagerDuty](https://docs.sazabi.com/catalogs/mcp-connectors/pagerduty.md) — Give the Sazabi agent read-only tools to look up PagerDuty incidents, alerts, services, on-call schedules, escalation policies, and change events.
* **Core integration**: [PagerDuty](https://docs.sazabi.com/catalogs/integrations/pagerduty.md#core-integration) — Connect PagerDuty so Sazabi can route issues to your services as PagerDuty alerts.

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

## Core integration

## About

Connecting PagerDuty lets Sazabi route issues to your PagerDuty services so they page the right on-call responders. PagerDuty is an **incident** integration and a shared [notification channel](https://docs.sazabi.com/guides/detect/notifications.md).

Sazabi triggers and resolves PagerDuty alerts as an issue opens and closes, so a resolved issue clears its PagerDuty alert.

## Prerequisites

* A PagerDuty account and a **REST API token**.
* Organization admin access in Sazabi.

## Set up in the dashboard

**Step 1**

### Create a PagerDuty REST API token

In PagerDuty, create a REST API token. Copy it.

**Step 2**

### Open the PagerDuty integration

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

**Step 3**

### Enter the API token

Paste the token and connect. Sazabi uses it to discover your PagerDuty
services so you can route issues to a specific service.

**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 (for example **Issue triggered**) to a PagerDuty
destination. See [Route notifications](https://docs.sazabi.com/guides/detect/notifications.md).

## Set up with the CLI

You can also connect PagerDuty 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)).

PagerDuty is an API-key provider, so pass its REST API token as the `apiToken` credential. Read the key from an environment variable rather than pasting it inline:

```bash theme={"system"}
export PAGERDUTY_API_TOKEN=...   # your PagerDuty REST API token
sazabi integrations connect pagerduty \
  --credentials "{\"apiToken\":\"$PAGERDUTY_API_TOKEN\"}"
```

Then add a delivery rule so issues reach PagerDuty — 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 PagerDuty 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 a PagerDuty destination. See [Route notifications](https://docs.sazabi.com/guides/detect/notifications.md).

## Incidents

Sazabi opens and resolves PagerDuty alerts as issues fire and clear, so a problem routes to whoever is on call and the alert closes when the issue resolves; Sazabi can also acknowledge an alert and escalate it along your PagerDuty escalation policy. Route issues to PagerDuty with a delivery rule — see [Route notifications](https://docs.sazabi.com/guides/detect/notifications.md).

## Verify

With a delivery rule pointing at a PagerDuty destination, trigger a test issue event (for example, re-open and resolve a test issue in the project inbox) and confirm a PagerDuty alert appears on the target service within a minute. Resolve the issue and confirm the PagerDuty alert clears.

## Troubleshooting

**No alert on the service** — Confirm a delivery rule names both the event type and the PagerDuty destination, and that no severity or component condition excludes the issue.

**Connection shows needs attention** — The REST API token may have been revoked. Create a new token in PagerDuty and reconnect.

## Further reading

> [card] [Route notifications](https://docs.sazabi.com/guides/detect/notifications.md)
>
> Route issues to PagerDuty 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.