PagerDuty Escalations
Create smart escalation paths for critical incidents with automatic context gathering and stakeholder notification.
2 Ways to Automate Pagerduty & Slack & Github
1
Auto-Escalate Critical PagerDuty Incidents to Slack
Search query: "pagerduty critical incident escalate slack"
EXAMPLE PROMPT
“When a PagerDuty incident is triggered at P1 severity, post an alert to #incidents with the service name, incident summary, on-call engineer, and a link, then DM the on-call person directly.”
Use this prompt ↗⚡What the agent does
✓Monitors PagerDuty for new incidents
✓Filters by severity level
✓Pulls on-call schedule
✓Posts a structured alert to #incidents
✓DMs the on-call engineer
✓Includes service context and runbook link
IMPACT
Critical incidents reach the right person in seconds, not minutes.
2
Gather GitHub Context for an Active Incident
Search query: "pagerduty incident github recent commits context"
EXAMPLE PROMPT
“When a PagerDuty incident is opened for the API service, automatically pull the last 5 GitHub commits to the API repo and post them to the incident Slack channel as context.”
Use this prompt ↗⚡What the agent does
✓Detects new PagerDuty incident
✓Identifies the affected service
✓Maps service to its GitHub repository
✓Fetches recent commits and authors
✓Posts commit context to Slack incident channel
✓Helps team identify likely cause immediately
IMPACT
Incident responders have deployment context the moment an alert fires.