Four steps to a wired page.
Standard PagerDuty integration key. Encrypted at rest with Fernet.
Circuit fires a dry-run event to confirm the key works.
Add the PagerDuty hook from Settings → Hooks. Circuit doesn’t auto-provision a PagerDuty hook — only GitHub, Slack and Linear get an auto-provisioned starting point on connect.
Fire manually from the spec, or wire your hook to fire on brief generation.
The page gets the why.
The on-call engineer sees what customers said — not just “something is broken.”
Circuit maps urgency to PagerDuty severity (critical / warning / info), so the right page gets the right escalation.
PagerDuty triggers through the same hook architecture as Linear and GitHub. One place to manage automations.
Built on the real plumbing.
PagerDuty Events API v2 integration key, Fernet-encrypted. Severity mapping in backend/services/hooks/providers/pagerduty.py.
Asked and answered.
Production incidents where the customer signal is the source — a spec triggered by a sudden wave of “checkout broken” feedback, for example. The page fires with the customer voice attached, so the on-call team sees what users are experiencing.
Fernet-encrypted at rest and only read at trigger time.
PagerDuty pages affect on-call rotations directly; Circuit defaults to letting you wire the hook deliberately. Add it from Settings → Hooks when you’re ready.
Different purpose. Linear is for tracked engineering work; PagerDuty is for incident response. Same hook architecture — different downstream tools.
Part of Circuit’s autonomous product intelligence stack — see the full picture.