PagerDuty

Read PagerDuty services, incidents, alerts, notes, log entries, schedules, on-calls, escalation policies, users and teams; create and update incidents.

Open, update and resolve incidents from monitoring and service desk flows, and report on-call and response data.

Build a flow with PagerDuty Provider API documentation

Source actions

Destination actions

Data types

Validation status

Implemented · fixture tested.

Implementation is checked against provider-shaped fixtures for every action, authentication failures, rate limits, pagination and duplicate safety. Provider sandbox and authorised account validation are recorded separately when credential-backed runs are completed.

What you can map

escalation policies

List escalation policies
Source
Escalation policies with rules, targets, services and teams.

incident alerts

List incident alerts
Source
Alerts grouped into an incident with severity and alert key.

incident notes

Add incident note
Destination
Not retried automatically
Adds a note to an incident timeline.
List incident notes
Source
Notes added to an incident, oldest first.

incidents

Create incident
Destination
Duplicate protected
Opens an incident on a service; a repeat with the same open incident key is rejected.
Get incident
Source
One incident with assignments, priority and service.
List incidents
Source
Incremental
Incidents created in a time range, filtered by status, urgency, service or team, oldest first.
Update incident
Destination
Duplicate protected
Acknowledges, resolves or reopens an incident, or changes title, urgency, priority, assignees or escalation.

log entries

List log entries
Source
Incremental
Incident timeline events (trigger, acknowledge, notify, resolve) for the account or one incident.

oncalls

List on-calls
Source
Who is on call, for which escalation policy, level and schedule, in a time range.

priorities

List priorities
Source
Incident priorities configured for the account, highest first.

schedules

List schedules
Source
On-call schedules with users and escalation policies.

services

List services
Source
Technical and business services with escalation policy and teams.

teams

List teams
Source
Teams in the account.

users

List users
Source
Users with role, time zone and teams.

Authentication

REST API key

Plans and access

All PagerDuty plans with REST API access; incident types and custom fields depend on plan. General access REST API keys act for the account; read-only keys cannot write. Writes record the requester given in the From header.

Test environment

PagerDuty offers free trials and developer accounts for testing.

Rate limits

REST API limits per key and account (around 960 requests per minute, with lower limits on incident creation); HTTP 429.

Provider events

V3 webhook subscriptions for incident and service events. Nexra event triggers are not yet available; flows run on demand or on a schedule.

Before you build a flow

The Events API v2 (events.pagerduty.com) uses integration routing keys on a separate host and is not implemented; incidents are created through the REST API.
Status updates (which notify subscribers), responder requests, merges and deletes are not implemented.
Incident lists filter on creation time (since/until), not last update.
Incident creation requires an incident key so repeats are rejected while the incident is open.