The CloudRadial AutomationAI PagerDuty extension lets a workflow or agent work through the PagerDuty incident lifecycle: find, raise, acknowledge, and resolve incidents, add notes, find out who is on call, review services, escalation policies, and schedules, look up users, and schedule maintenance windows. This article covers what the extension can do, the secrets it needs, which tools require approval, and the skills that ship with it. It is for workspace users who build automations (Admin or Owner Role).
- What the Extension Covers
- Creating the API Token
- Providing the Credentials to Your Runner
- Reads and Approval-Gated Changes
- Skills
- Tips for Working With PagerDuty Data
What the Extension Covers
The extension calls the PagerDuty REST API (v2) and provides 16 tools across these areas:
| Area | What you can automate |
| Incidents (5 tools) | List incidents filtered by status, service, urgency, assigned user, team, or time window; read one incident; create an incident on a service; acknowledge or resolve an incident; and add a note to an incident |
| On call and schedules (3 tools) | Find who is on call for an escalation policy, schedule, or user over a time window, list schedules, and read one schedule over a time window |
| Services and escalation policies (4 tools) | List and read services and escalation policies, including a policy's ordered escalation rules and targets |
| Users (2 tools) | Find users by name, email, or team, and read one user's role, time zone, and contact methods |
| Maintenance windows (2 tools) | List ongoing, future, or past maintenance windows, and create a window that suppresses alerts on one or more services |
Install it from Extensions like any other catalog extension. It appears in the catalog as PagerDuty. See Browsing and installing extensions for the general install flow.
Creating the API Token
The extension authenticates with a PagerDuty REST API token: either a General Access API key, created in PagerDuty under Integrations > API Access Keys, or a user token. Treat the token as a full-access credential.
Every write the extension makes (creating an incident, acknowledging or resolving one, adding a note, and creating a maintenance window) also carries the email address of a valid PagerDuty user, so PagerDuty can attribute the action. PagerDuty requires it for these writes when you use a General Access API key. Choose the user the extension's actions should be attributed to.
Providing the Credentials to Your Runner
Store three secrets in your runner's Key Vault with these exact names:
| Secret | Value |
PagerDuty-ApiUrl |
The PagerDuty API base URL, https://api.pagerduty.com |
PagerDuty-ApiToken |
The REST API token |
PagerDuty-FromEmail |
The email address of a valid PagerDuty user, as a plain address |
Store the token by itself. PagerDuty expects it after the words Token token= rather than as a Bearer token, and the extension builds that header for you. If PagerDuty-FromEmail isn't a real PagerDuty user, PagerDuty rejects every write. For how to add secrets, see Accessing and updating your runner's Key Vault. If you keep a separate PagerDuty account per client, see Managing companies and per-company credentials.
The agent reads the credentials from the runner and never asks you for them. Once the secrets are in place, ask the AI Playground who is currently on call to confirm the connection works.
Reads and Approval-Gated Changes
Of the 16 tools, 12 are read-only and run without interruption. The four that change PagerDuty are approval-gated: the run pauses and the request appears as an Action Required item in the Inbox until someone approves it. See Handling Action Required items in the Inbox.
| Tool behavior | Tools |
| Approval-gated | Create an incident; acknowledge or resolve an incident; add a note to an incident; create a maintenance window |
| Read-only | List and read incidents; find who is on call; list and read schedules; list and read services; list and read escalation policies; list and read users; list maintenance windows |
A maintenance window suppresses alerts on its services for the whole window, so check the services and the start and end times before you approve one.
Skills
The extension ships five skills that guide an agent through common PagerDuty tasks:
| Skill | Use it to |
| Triage and Manage Incidents | Find, read, raise, acknowledge, or resolve an incident, or add a note to one. Creating, managing, and adding notes wait for approval. |
| Find Who Is On Call | Find out who is on call currently, or will be, for a service, escalation policy, or schedule. Read-only. |
| Review Services and Escalation Policies | Look up services or escalation policies, read their detail, or find their ids before raising an incident or scheduling maintenance. Read-only. |
| Schedule a Maintenance Window | Suppress alerts on one or more services for planned maintenance, or review existing windows. Creating a window waits for approval. |
| Look Up Users | Find a user by name or email and read their role, time zone, and contact methods. Read-only. |
Tips for Working With PagerDuty Data
- Name the service when you ask for an incident or a maintenance window. The agent looks up the service id from your live services rather than guessing one.
- In on-call results, escalation level 1 is the primary on-call
- Give maintenance window start and end times in ISO 8601 format, for example
2026-11-20T22:00:00Z - Acknowledging and resolving work on one incident at a time
- List tools return the complete result in one call, so you don't need to ask for more pages. Use filters such as status, service, or a time window to keep results focused.
If you are still having trouble, we’re here to help! Submit a ticket here for assistance, and don’t forget to check our status page to ensure there are no outages in your area.
Comments
0 comments
Please sign in to leave a comment.