Automate an incident response runbook in PagerDuty using Incident Workflows and Automation Actions, capturing evidence at each step

Steps

1. Define an Incident Workflow with trigger conditions (e.g., an incident created at a given priority or for a specific service) and a sequence of if-this-then-that steps.
2. Add Automation Action steps to the workflow to run predefined diagnostic or remediation jobs, such as pulling logs or restarting a service, against integrated runners.
3. Configure Workflow Integrations to connect steps to external systems (cloud providers, monitoring tools, or a generic Web API) so the workflow can both gather data and trigger actions outside PagerDuty.
4. Review captured evidence in the incident's Automation Actions log, where each run creates an expandable record of the job's output, and export or link that data into the post-incident report for audit purposes.
5. Apply the equivalent pattern in Opsgenie using action policies that trigger diagnostic or remediation actions on alert match, integrated with a separate runbook automation tool to execute the actual steps.