Skip to main content
The PagerDuty toolkit connects a PagerDuty account to agents and workflows using a REST API token and lets you list and manage incidents, create and resolve incidents, look up services and users, and find the current on-call responder for a schedule or service.

​
Prerequisites

  • An active PagerDuty account with at least one service.
  • A PagerDuty REST API token — go to Integrations → API Access Keys in PagerDuty and create a General Access or User Token.
  • A Default From Email — the exact email address of a PagerDuty user who is allowed to create, acknowledge, and resolve incidents. PagerDuty requires this for all incident write actions.
  • Schedule IDs for on-call lookups, and service IDs for incident filters and creation. Use List Services and List Users to discover these.
Write actions (Acknowledge Incident, Resolve Incident, Create Incident) change live PagerDuty data immediately. Confirm the incident ID, service, and intended outcome before running them. Avoid automatic retries on Create Incident — uncertain responses can create duplicate incidents. Never expose the API token in prompts, chat, tickets, screenshots, or documentation.

​
Setup

1

Create a PagerDuty REST API token

In PagerDuty, go to Integrations → API Access Keys and create a General Access or User Token. Copy it immediately and store it securely.
2

Identify the Default From Email

Go to People → Users in PagerDuty and find the email address of a user allowed to manage incidents. You will need this exact address for all incident write actions.
3

Open an agent or workflow

Open an agent and add the PagerDuty toolkit under Toolkits, or add a PagerDuty step to a workflow.
4

Create a saved connection

In the PagerDuty step, choose + New under Select saved connection. Enter a Connection Name, the API Token, and the Default From Email. Save the connection.
5

Test with a read action first

Run List Services or List Incidents to confirm access before using incident write actions. For agents, use the Test Connection button to verify authentication.

​
Available tools

​
Incident Retrieval

​
Incident Management

​
Service and User Discovery

​
On-Call

​
Use cases

  • List all triggered high-urgency incidents for a production service and surface them in a standup summary.
  • Find the current on-call responder for a service and include their name and email in a downstream notification.
  • Automatically acknowledge an incident after an operator accepts ownership in an approval step.
  • Create a high-urgency incident when an automated monitoring step detects a critical service failure.
  • Resolve an incident and add a resolution note after a health-check step confirms recovery.

​
Troubleshooting