PagerDuty Incident Triggers for Workflows

We’ve added PagerDuty as a trigger source for your workflows in Cased. Now when incidents fire in PagerDuty, your agents can automatically jump into action.

Zero config

There’s nothing to configure on the PagerDuty side. When you connect PagerDuty to Cased, we automatically:

1. Create webhook subscriptions in PagerDuty
2. Set up secure signature verification
3. Start receiving all incident events

Available triggers

Workflows can respond to three key incident events:

• Incident Triggered - When a new incident is created
• Incident Acknowledged - When someone acknowledges the incident
• Incident Resolved - When the incident is marked as resolved

Real world examples

Auto-diagnostics on incident trigger:

When database CPU alert triggers:
1. Check current connections and slow queries
2. Capture last 5 minutes of error logs
3. Take thread dump if applicable
4. Post findings to incident Slack channel

Automated remediation:

When disk space alert triggers:
1. Check which directories are full
2. Clear old logs and temp files
3. If still critical, scale up storage
4. Update incident with actions taken

Post-incident automation:

When incident resolves:
1. Create post-mortem document from template
2. Gather metrics from incident timeframe
3. Create follow-up tickets for action items
4. Schedule review meeting

Get started with PagerDuty workflows →