# PagerDuty

Trace incidents to the release behind them. Open the **PagerDuty** card on the Integrations page to add a source.

## Incidents

> **Beta, early access.** Flags: `pagerduty`, plus `forensics` or `release_health`.

Triggered incidents become [incidents](/docs/release-health#what-broke-production) ranked against recent releases, with evidence.

1. Add a source in Bumpkit.
2. In PagerDuty, open **Integrations > Generic Webhooks (v3)** and subscribe the URL to `incident.triggered` for the service.
3. PagerDuty shows a signing secret once. Paste it into the source.

Bumpkit checks every delivery's `X-PagerDuty-Signature` (`v1=` HMAC-SHA256 of the body). Other event types are ignored.

```bash
bumpkit sources add pagerduty --repository owner/name
bumpkit sources set-secret pagerduty SOURCE_ID --secret-env PAGERDUTY_SECRET
```

The `sources_add` and `sources_set_secret` MCP tools do the same. Owners and admins add sources.