Cotool + PagerDuty
Connect PagerDuty to Cotool so response and detection agents page on-call, deliver run output as PagerDuty events, and link each escalation to its incident.
The short answer
With PagerDuty connected, Cotool response agents and detection agents can send their output to PagerDuty, escalated-alert notifications can go to PagerDuty, and each alert's detail page links to the PagerDuty incident its escalation created.[1][2]
How it connects: PagerDuty exposes two kinds of credentials for integrations: REST API keys for reading and changing PagerDuty objects, and Events API v2 integration keys, sent as routing_key, for triggering alerts on a specific service.[4][5]
What Cotool uses from PagerDuty
- Incidents linked to alerts
- Cotool's alert detail page shows agent run and notification cards that link directly to the PagerDuty incident each escalation created.[1]
- Events and deduplication
- PagerDuty groups events by
dedup_key. A trigger event without one always creates a new alert, so a stable key per alert keeps repeats on one incident.[6]
Response actions
These change state in PagerDuty, so they are the steps teams usually gate behind approval.
- Page on-call
- Response agent output hooks can deliver a run's metadata and structured output to PagerDuty after each run, and PagerDuty is also a destination for detection agents.[1]
Detections, hunts, and triage
- Page only on confirmed severityResponse
- Cotool's docs show escalation guidance an agent follows from context documents: for a SEV-1, page on-call via PagerDuty, post to the incident channel, and escalate to the CISO.[3]
- Route detection hits to PagerDutyDetection
- Detection agents can use PagerDuty as their destination, so high-severity hits reach the on-call engineer instead of a queue.[1]
Setup and permissions
Admins and the Account Owner create general access REST API keys under API Access Keys. For alerts on a service, add an Events API v2 integration to that service and copy its integration key.[4][5]
| Permission | Access | Why |
|---|---|---|
| General access REST API keyReads and changes PagerDuty objects such as incidents. A read-only key allows only GET calls.[4] | Write | Reads and changes PagerDuty objects such as incidents. A read-only key allows only GET calls.[4] |
| Events API v2 integration keySent as `routing_key` to trigger, acknowledge, or resolve alerts on one service.[5][6] | Write | Sent as `routing_key` to trigger, acknowledge, or resolve alerts on one service.[5][6] |
How Cotool works with PagerDuty
FAQ
Sources
- Changelog (Cotool docs) · accessed November 16, 2026
- Notifications (Cotool docs) · accessed November 16, 2026
- Context documents (Cotool docs) · accessed November 16, 2026
- API access keys (PagerDuty Support) · accessed November 16, 2026
- Events API v2 overview (PagerDuty Developer) · accessed November 16, 2026
- Sending an alert event (PagerDuty Developer) · accessed November 16, 2026
