PagerDuty

What it does

PagerDuty incidents can trigger Loop Engine workflows, turning urgent alerts into governed and attributable response loops. The adapter maps incident events to loop signals, starts a loop per incident, and keeps human decisions in-policy.

Use case

PagerDuty fires a SEV-2 database incident:

1. Loop Engine starts incident-response loop
2. On-call engineer acknowledges (human-only guard)
3. Runbook automation executes
4. Loop closes and emits learning signal

Quick setup

1. Install

   ⧉

   1npm install @loop-engine/adapter-pagerduty

2. Configure webhook endpoint

   ⧉

   1POST https:"cmt">//your-app.example.com/hooks/pagerduty

3. Wire a PagerDutyNotifier (Events v2 key)

   ⧉

   1import { PagerDutyNotifier } from "@loop-engine/adapter-pagerduty";
   2 
   3const notifier = new PagerDutyNotifier({
   4  integrationKey: process.env.PAGERDUTY_INTEGRATION_KEY!
   5});
   6void notifier;

4. Define incident loop

   ⧉

   1loopId: incident-response
   2initialState: triage
   3states:
   4  - stateId: triage
   5    transitions:
   6      - signalId: acknowledge_incident
   7        toState: executing

Configuration reference

| Option | Type | Default | Description | |---|---|---|---| | webhookSecret | string | required | PagerDuty webhook signing secret | | incidentLoopId | string | required | Loop definition ID to start on incident | | severityMap | object | — | Map PagerDuty severity to loop signals |

Troubleshooting

• Webhook signature invalid — Ensure webhookSecret matches PagerDuty integration settings.
• Loop not starting — Verify incidentLoopId is registered in runtime.

Related

• Governed Incident Response with Perplexity and PagerDuty
• Perplexity Sonar
• Infrastructure Change Approval example
• Human Approval Gates
• PagerDuty webhook docs