PagerDuty

Connect Cased to PagerDuty to manage incidents and alerts

PagerDuty

To use PagerDuty, we just need a single API key, which is easy to create.

Generate an API Key

1. Visit PagerDuty API Keys
2. Create a new API key
3. Do not select a read-only API key
4. The API key should have write permissions so that we can create the event webhook

Connect to Cased

1. Go to app.cased.com/connections/pagerduty
2. Enter your PagerDuty API key
3. Enter your default service name (e.g., “Production” or “Main Service”)
4. Cased will automatically configure webhooks to receive PagerDuty incident events
5. Cased agent will start using the PagerDuty connection.

Workflow Triggers

Once connected, PagerDuty can trigger automated workflows based on incident events. This allows you to automatically respond to incidents, gather diagnostics, notify teams, or even attempt automated remediation.

Available Trigger Events

PagerDuty workflows can be triggered by the following incident events:

• Incident Triggered - Fires when a new incident is created
• Incident Acknowledged - Fires when someone acknowledges an incident
• Incident Resolved - Fires when an incident is marked as resolved

Setting Up a PagerDuty Workflow

1. Navigate to your project’s Workflows page
2. Create a new workflow or edit an existing one
3. In the Trigger section, select “PagerDuty”
4. Choose which incident events should trigger this workflow
5. Configure your workflow instructions to handle the incident

Example Use Cases

• Auto-diagnostics: When an incident triggers, automatically gather logs, metrics, and system status
• Team notifications: Send custom notifications to Slack or other channels with incident details
• Runbook automation: Execute predefined runbooks based on the incident type or service
• Post-incident actions: When an incident resolves, create a post-mortem document or update status pages

Workflow Context

When a PagerDuty incident triggers a workflow, the following context is available:

• incident_number - The PagerDuty incident number
• incident_title - Title/description of the incident
• incident_urgency - Urgency level (high, low)
• incident_url - Direct link to the incident in PagerDuty
• service - The affected service name

This context can be used in your workflow instructions to create targeted responses based on the specific incident details.