# Feature Tutorial: Automation Actions

Runs pre-built diagnostic and remediation jobs on an incident through a secured Runner, without escalating to a specialist for known fixes.

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**

* [Extending Automation Actions Across the PagerDuty Platform](https://www.pagerduty.com/blog/automation/summit-automation-actions-updates/) - covers Automation Actions in Incident Response and in Slack, and how it lets first-line responders triage without escalating.

**Watch the product demos and webinars**

* [PagerDuty Rundeck Integration Demo](https://www.youtube.com/watch?v=rR450shsjMc) — covers triggering automated jobs from a PagerDuty incident to shorten resolution and reduce escalations.

**Check out the training modules on PDU**

* [End-to-End Event-Driven Automation](https://university.pagerduty.com/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**

* [PagerDuty Automation Actions](/incident-management/automation/automation-actions)
* [Automated Diagnostics](https://docs.rundeck.com/docs/learning/solutions/automated-diagnostics/solution-overview.html) — a prebuilt library of automation jobs designed to be invoked using Automation Actions
* [PagerDuty Automation Trial](/incident-management/automation/pagerduty-automation-trial)

**Using the API?**

Automation Actions are managed via the [Automation Actions API](/developer/api/reference#rest/tag/automation-actions):
* [List Automation Actions](https://developer.pagerduty.com/api-reference/410000e970715-list-automation-actions)
* [Create an Automation Action](https://developer.pagerduty.com/api-reference/d64584a4371d3-create-an-automation-action)
* [Create an Automation Action runner](https://developer.pagerduty.com/api-reference/d78999fb7e863-create-an-automation-action-runner)

**Managing PagerDuty with Terraform?**

* [pagerduty_automation_actions_action](https://registry.terraform.io/providers/PagerDuty/pagerduty/latest/docs/resources/automation_actions_action) — define a script or Runbook Automation job as an Action
* [pagerduty_automation_actions_runner](https://registry.terraform.io/providers/PagerDuty/pagerduty/latest/docs/resources/automation_actions_runner) — configure the Runner that executes Actions

**Other Resources**

* [Automating the Response Process](/ops-guides/auto-remediation) - PagerDuty's Ops Guide on using automation for incident remediation, including how to identify good candidates for automated remediation and self-healing.