|docs
Start Trial

Feature Tutorials

Automation Actions

Automation Actions Tutorial

View as Markdown

When an incident needs a known diagnostic or fix, the fastest path is usually to escalate to whoever knows the runbook — which means waking someone up for something that's already been solved before, more than once.

Automation Actions gives responders push-button access to a library of diagnostic and remediation jobs directly from an incident, without needing to escalate to a specialist. An Action invokes a job staged in Runbook Automation (or a script run by a Runbook Automation Self-Hosted Runner), and can be triggered manually from the PagerDuty web app, mobile app, or Slack — or automatically as part of an Event Orchestration rule, with no human in the loop at all.

Because Actions connect to production infrastructure through a Runner deployed within a firewall or VPC, responders get safely delegated automation rather than direct access to sensitive systems. Results — logs, diagnostics output, remediation status — flow back into the incident's Automation Actions Log, so the team has a record of what ran and what it found without leaving PagerDuty.

Automation Actions is available to accounts with Runbook Automation (SaaS or Self-Hosted), and requires a PD Automation Actions user license.

Learn More

Read more about what Automation Actions provides

Watch the product demos and webinars

Check out the training modules on PDU

  • End-to-End Event-Driven Automation — includes the "Speed Up Incident Resolution with Automation Actions" module on applying Automation Actions to reduce manual intervention and improve resolution times.

Watch the click-through tutorial

  • need one recorded for this

Find the product documentation in our Knowledge Base

Managing PagerDuty with Terraform?

Other Resources

  • Automating the Response Process - PagerDuty's Ops Guide on using automation for incident remediation, including how to identify good candidates for automated remediation and self-healing.