PagerDuty Integration
Route incidents to on-call teams via PagerDuty Events API.
PagerDuty Integration
Route CrownSync Playbooks incidents to your on-call teams via PagerDuty. When an incident is declared in CrownSync, PagerDuty automatically pages the right people based on severity. Resolution status syncs back automatically.
No native plugin required
This integration uses the PagerDuty Events API v2 via CrownSync outbound webhooks. No app installation is needed on either side.
Setup Steps
- Create an API key in Admin → Integrations → API Keys.
- In PagerDuty, go to Services → Service Directory → New Service.
- Under Integrations, select Events API v2.
- Copy the Integration Key (routing key) from PagerDuty.
- In CrownSync, go to Admin → Integrations → Webhooks and create an outbound webhook.
- Set the webhook URL to
https://events.pagerduty.com/v2/enqueue. - Select events:
incident.created,incident.status_changed.
Severity Mapping
CrownSync incident severities map to PagerDuty alert severities:
| CrownSync Severity | PagerDuty Severity |
|---|---|
| Critical | critical |
| High | error |
| Medium | warning |
| Low | info |
Auto-Resolve
When an incident is resolved in CrownSync, a resolve event is sent to PagerDuty, automatically resolving the corresponding alert. This keeps both platforms in sync without manual intervention.
Webhook Payload Format
CrownSync formats the webhook payload as a PagerDuty Events API v2 event:
{
"routing_key": "YOUR_INTEGRATION_KEY",
"event_action": "trigger",
"payload": {
"summary": "CrownSync: Ransomware Infection — Critical",
"severity": "critical",
"source": "pb.crownsync.uk",
"component": "incident-response",
"custom_details": {
"incident_ref": "INC-2026-0042",
"playbook": "ransomware-infection",
"dashboard_url": "https://pb.crownsync.uk/incidents/..."
}
}
}Example Use Cases
- Critical incident declared → Page security team immediately
- High severity incident → Alert SOC team within 5 minutes
- Incident resolved in CrownSync → Auto-resolve PagerDuty alert
- Drill started → Send informational alert to on-call team
Integration instructions last verified: April 2026
Was this page helpful?