PagerDuty Webhook Payload Transformer
PagerDuty webhooks broadcast incident lifecycle events — triggered, acknowledged, resolved — letting your systems react to on-call alerts in real time.
Example Payload — incident.triggered
{
"event": {
"id": "01BKQHXY1JTHNZQ2DCQP7HNFTS",
"event_type": "incident.triggered",
"occurred_at": "2024-01-15T03:14:15Z",
"agent": {
"summary": "Monitoring Bot"
},
"data": {
"id": "P123ABCD",
"title": "Database connection pool exhausted on prod-db-01",
"urgency": "high",
"status": "triggered",
"service": {
"id": "PABC123",
"name": "Production Database"
}
}
}
}Best Output Formats
Notification payload
extract title, urgency, and service.name for Slack or SMS alerts
Runbook trigger
map incident.id and title to a runbook automation starter payload
Incident log entry
flatten incident data with occurred_at for append-only audit storage
Common Use Cases
Post formatted incident alerts to a dedicated war-room Slack channel automatically
Trigger auto-remediation scripts when specific high-urgency incident patterns are detected
Update a status page API with the current incident state as it progresses
Ready to transform your PagerDuty webhooks?
Open Webhook Transformer →FAQ
What does a PagerDuty webhook payload look like?
PagerDuty webhooks broadcast incident lifecycle events — triggered, acknowledged, resolved — letting your systems react to on-call alerts in real time. A typical "incident.triggered" event includes fields for notification payload.
How do I transform PagerDuty webhook payloads?
Use the Aarunya Webhook Transformer to paste your PagerDuty payload and select your desired output format. Common formats include: Notification payload, Runbook trigger, Incident log entry.
What are the best uses for PagerDuty webhooks?
Post formatted incident alerts to a dedicated war-room Slack channel automatically Trigger auto-remediation scripts when specific high-urgency incident patterns are detected Update a status page API with the current incident state as it progresses