Integration · Developer
AI agents for PagerDuty
Open, acknowledge and resolve PagerDuty incidents, add notes to them, and see who is on call for a schedule.
- Actions
- 4
- Read
- 1
- Write
- 3
Actions
What your agents can do in PagerDuty
4 actions. Each one is a tool your agents can call and a step your workflows can run.
Read 1
Look things up. Nothing changes.
List who is on call for a schedule
Lists who is on call right now for a schedule, by the schedule's ID: each entry names the user, the escalation policy and level, and when the shift starts and ends.
Write 3
Create, change or send.
Create an incident
Opens an incident on a PagerDuty service, which pages whoever its escalation policy says is on call.
Add a note to an incident
Adds a note to an incident's timeline, by the incident's ID.
Acknowledge or resolve an incident
Sets an incident's status to acknowledged (someone is on it, so paging stops) or resolved (the problem is over), by the incident's ID.
A person can approve first
Any write action can be set to wait for a person's approval before it runs, so an agent asks before it changes anything.
Connection
How it connects
Connect it once in the console, then give it to the agents and workflows that need it.
Paste an API key from your PagerDuty account.
What you enter
- REST API key
Settings
- Act as (user email)
Kept safe
- Credentials are stored encrypted with your organization's own keys.
- They are opened only by the process that makes the call, at the moment it runs, and never go into a prompt or the browser.
- Calls go only to the tool's own servers.
Ideas
Ideas to start with
Starting points made only from the actions above. Mix them with any other tool your agents can use.
- 01
Ask about your PagerDuty data
Ask a question in plain words. The agent can list who is on call for a schedule in PagerDuty, then answers with what it found.
- 02
Let an agent update PagerDuty
Have the agent create an incident or add a note to an incident in PagerDuty as part of a larger task. Turn on approval and a person signs off on each change first.
- 03
Share what it finds in Slack
Give one agent PagerDuty and Slack: it can list who is on call for a schedule in PagerDuty and post a summary to a Slack channel in the same run.
Works well with
More Developer tools
- GitHub4 actionsOpen and comment on issues, and start GitHub Actions workflows, in the repositories a personal access token can reach.
- GitLab4 actionsOpen and comment on issues, and start CI/CD pipelines, in the GitLab.com projects an access token can reach.
- Bitbucket3 actionsComment on and read pull requests, and start Bitbucket Pipelines, in the Bitbucket Cloud repositories your Atlassian API token can reach.
- Sentry3 actionsList, read, resolve and ignore error issues in a sentry.io organization, in its US or EU (Germany) data region.
- Datadog2 actionsPost events to the Datadog Event Explorer and send custom metric points, on any Datadog site, with an API key.
- App Store Connect8 actionsLook after iPhone, iPad and Mac apps on Apple's App Store.
FAQ
PagerDuty and MyDeepAgents
Can MyDeepAgents connect to PagerDuty?
Yes. The PagerDuty connector has 4 actions: 1 reads and 3 make changes. Your agents can call them as tools, and your workflows can run them as steps.
How do I connect PagerDuty?
Paste an API key from your PagerDuty account. You'll need: REST API key. The connection also asks for: Act as (user email). Credentials are stored encrypted with your organization's own keys and are opened only at the moment of a call.
Can an agent change data in PagerDuty without asking?
Only if you let it. Each of the 3 actions that change data can be set to wait for a person's approval before it runs.
Can I use PagerDuty in workflows as well as agents?
Yes. Every PagerDuty action also works as a step in a workflow, and the same connection serves your agents and your workflows.
Early access
Put PagerDuty to work
Connect it in a few minutes, give an agent the actions it needs, and decide which changes wait for a person.