PagerDuty
Turn incidents and requests into PagerDuty work items, and keep status in step across your tools.
32 ways to read, 11 ways to write, each write switched on by you.
Quality checks
Built and tested with example responses.
- Ready to connect: doneEvery listed action is built in.
- Built and tested with example responses: doneEach action is built from the provider’s published API and tested against example responses, errors, rate limits and paging.
Connected, approved, proven.
The things teams do most with PagerDuty, an example flow with a person in the loop, and what Nexra keeps as proof.
Top actions
- Create business serviceApproval by rule
- Add incident noteApproval by rule
- List business servicesRead
Example flow
- PagerDuty · List business servicesDone
- PagerDuty · Create business serviceNeeds approval
- Nexra · Record the decision and result in the evidence chainProven
Example workflow. Routine runs go through on their own. Only a change your rules flag, such as one over a limit you set, waits for the right person, who sees the exact change and the rule before it reaches PagerDuty.
What gets logged
- Whether it ran on its own or who approved it, and under which rule
- A fingerprint of the exact request sent to PagerDuty
- PagerDuty's reply: what it created or changed
- One entry in the evidence chain, linked to the one before
Try this in the sandbox
Run the whole flow with test data in your sandbox, then connect your own account when you are ready to go live.
For developers
Technical detail
Read PagerDuty services, incidents, alerts, notes, custom fields, change events, schedules, on-calls, policies, users and teams; manage incidents, services and teams.
PagerDuty API docs- Source actions
- 32
- Destination actions
- 11
- Data types
- 23
What you can map
Reads are always available. Writes are off until you switch them on for a connection, and governed writes follow your policies.
Business services4
- Create business serviceDestinationNot retried automaticallyApproval before production
Adds a business service to the service catalogue.
- Get business serviceSource
One business service.
- List business servicesSource
Business services with point of contact and owning team.
- Update business serviceDestinationProvider duplicate protectionApproval before production
Updates a business service's name, description, contact or team.
Change events2
- Get change eventSource
One change event with its services and links.
- List change eventsSourceIncremental
Deploys and other change events sent to PagerDuty, in a time range.
Escalation policies2
- Get escalation policySource
One escalation policy with rules and targets.
- List escalation policiesSource
Escalation policies with rules, targets, services and teams.
Incident alerts1
- List incident alertsSource
Alerts grouped into an incident with severity and alert key.
Incident custom fields2
- List incident custom field valuesSource
Custom field values set on an incident, with their types.
- Set incident custom field valuesDestinationProvider duplicate protectionApproval before production
Sets custom field values on an incident by field name or ID. Does not notify responders.
Incident notes2
- Add incident noteDestinationNot retried automaticallyApproval before production
Adds a note to an incident timeline.
- List incident notesSource
Notes added to an incident, oldest first.
Incident related change events1
- List related change eventsSource
Change events PagerDuty correlates with an incident, with the correlation reason.
Incident types1
- List incident typesSource
Incident types configured for the account.
Incidents4
- Create incidentDestinationProvider duplicate protectionApproval before production
Opens an incident on a service; a repeat with the same open incident key is rejected.
- Get incidentSource
One incident with assignments, priority and service.
- List incidentsSourceIncremental
Incidents created in a time range, filtered by status, urgency, service or team, oldest first.
- Update incidentDestinationProvider duplicate protectionApproval before production
Acknowledges, resolves or reopens an incident, or changes title, urgency, priority, assignees or escalation.
Log entries2
- Get log entrySource
One incident timeline event.
- List log entriesSourceIncremental
Incident timeline events (trigger, acknowledge, notify, resolve) for the account or one incident.
Maintenance windows1
- List maintenance windowsSource
Maintenance windows that suppress incidents on services.
Notifications1
- List notificationsSourceIncremental
Notifications PagerDuty sent to responders in a time range, by channel. Contact addresses are not returned.
Oncalls1
- List on-callsSource
Who is on call, for which escalation policy, level and schedule, in a time range.
Priorities1
- List prioritiesSource
Incident priorities configured for the account, highest first.
Schedule overrides1
- List schedule overridesSource
Overrides on a schedule in a time range.
Schedule users1
- List schedule on-call usersSource
Users on call for a schedule in a time range.
Schedules2
- Get scheduleSource
One schedule with its rendered on-call entries for a time range.
- List schedulesSource
On-call schedules with users and escalation policies.
Services4
- Create serviceDestinationNot retried automaticallyApproval before production
Creates a technical service routed to an escalation policy. Does not open incidents.
- Get serviceSource
One service with escalation policy, timeouts, urgency rule and integrations.
- List servicesSource
Technical and business services with escalation policy and teams.
- Update serviceDestinationProvider duplicate protectionApproval before production
Updates a service's name, description, escalation policy, timeouts or urgency.
Tags2
- Create tagDestinationNot retried automaticallyApproval before production
Creates a tag label.
- List tagsSource
Tags used to label users, teams and escalation policies.
Team members1
- List team membersSource
Members of a team with their team role.
Teams4
- Create teamDestinationNot retried automaticallyApproval before production
Creates a team.
- Get teamSource
One team.
- List teamsSource
Teams in the account.
- Update teamDestinationProvider duplicate protectionApproval before production
Updates a team's name or description.
Users2
- Get userSource
One user with role, time zone and teams.
- List usersSource
Users with role, time zone and teams.
Webhook subscriptions1
- List webhook subscriptionsSource
V3 webhook subscriptions with their events and filters. Delivery headers are not returned.
Access and limits
- 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.
- Pagination
- Classic offset pagination with limit up to 100 and the more flag; offsets above 10,000 are rejected.
- Provider events
- V3 webhook subscriptions for incident and service events. Flows run on demand, on a schedule, or when a scheduled check finds new or changed records.
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, snoozes, merges, alert resolution, user creation (sends invitations), change event sends and every delete are intentionally not implemented.
- Schedule, override and escalation policy writes are not implemented because they change who is paged; manage them in PagerDuty.
- Service, business service, team and tag creates have no idempotency key; uncertain writes are not repeated automatically.
- Notifications are returned without the contact address PagerDuty delivered to, and webhook subscriptions without delivery headers.
- Incident custom fields and incident types depend on the PagerDuty plan.
- 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.
Developer reference
- Create the PagerDuty credentials described above with the narrowest permissions your flows need.
- In Nexra, open Connect, then Connections, then New connection, choose PagerDuty, enter its settings and credentials, and tick only the write actions you need. Connection guide
- Test the connection, then use its actions as flow sources and destinations. Flow guide
Machine-readable detail: GET /api/public/connect/connectors/pagerduty and the Connections API.