---
title: PagerDuty incident integration
description: Getting paged at night for an incident that already recovered is the fastest way to stop trusting your alerts. Alerts can now route to PagerDuty via Events…
canonical: https://watchfor.io/changelog/2026-07-31-pagerduty-notifications
---

[All updates](/changelog/page/7#2026-07-31-pagerduty-notifications) ✨ New New channel Jul 31, 2026 · v 5.0.8

# PagerDuty incident integration

Getting paged at night for an incident that already recovered is the fastest way to stop trusting your alerts. Alerts can now route to PagerDuty via Events API v2 with the full incident lifecycle: a firing alert opens a PagerDuty incident and the recovery auto-resolves the same one. Diagnosis, expected vs detected values, confirming locations and a View-in-WatchFor link ride along, and EU-region PagerDuty accounts are supported.

Paste the Events API v2 key and pick your PagerDuty region.

## Set it up

- In PagerDuty, open the service that should receive alerts, go to Integrations and add an Events API V2 integration. Copy the 32-character integration key.

- In WatchFor, go to Alerting → Channels & contacts → New channel → PagerDuty , paste the key as the Routing Key and pick the Service Region : US / Global , or EU if your PagerDuty account is in the EU region.

- Attach the contact groups it should serve and click Send test . Tests open an incident but never resolve it, so resolve the test in PagerDuty yourself.

## How the lifecycle maps

In WatchFor In PagerDuty

Incident confirmed Incident triggered

Incident resolves The same incident resolves

Acknowledged Not synced

Each alert rule on each monitor maps to exactly one PagerDuty incident, so a repeat alert updates it instead of opening a second one.

## Example

Your checkout monitor fails at 01:40 and PagerDuty pages the on-call engineer. The incident already carries the diagnosis, expected and detected values and the confirming locations, with a link back to WatchFor. At 01:52 the site recovers; WatchFor resolves the PagerDuty incident and the pages stop.

Docs: [PagerDuty](/docs/notifications/pagerduty).

Share this update

---

Canonical page: https://watchfor.io/changelog/2026-07-31-pagerduty-notifications · Site guide: https://watchfor.io/llms.txt