rocketkind
Incident Management

PagerDuty

PagerDuty is on-call and incident response — services, escalation policies, schedules, and the incidents that page whoever is on call.

Authentication

  • API key

Actions

Generic API request. Call any PagerDuty API endpoint on this connection, for the case where no shipped action covers it yet. The connection supplies the base URL, the authentication and the egress route, so only the path, query and body are yours to fill.

  • Create incidentCreate a new incident on a service (POST /incidents, JSON body).
  • Create incident noteAdd a note to an incident (POST /incidents/{id}/notes, JSON body).
  • Get incidentRead one PagerDuty incident by id to find out whether it is still open and who it is about — the natural follow-up to a webhook or an alert notification.
  • Get serviceRead one PagerDuty service by id — the technical service an incident was raised against — typically to resolve a stored service id back to a name.
  • Get userRead one PagerDuty user by id, typically to turn the assignee id on an incident into a person's name.
  • List escalation policiesList the escalation policies on the account — who is paged for an incident, in what order — with each policy's escalation rules (delay and targets), services and teams.
  • List incident alertsRead the alerts grouped into an incident — the monitoring events behind it — with each alert's status, severity, de-duplication key, service, integration and its body.details payload as the monitoring tool sent it.
  • List incident log entriesRead an incident's timeline — every trigger, notification, acknowledgement, assignment, escalation, note, urgency change and resolution, each with its time, the agent (user, service or integration) that caused it and the channel it came through.
  • List incident notesRead the notes already posted on an incident — each with its text, author (a user, or a service or rule shown as a bot user) and time.
  • List incidentsList incidents on the PagerDuty account, filtered by status, urgency, service, team, assigned user and a since/until window, and sorted by number, creation, resolution or urgency.
  • List on-callsList who is on call — one entry per user, escalation policy, level and schedule, with the shift's start and end — now by default, or across a since/until window to see upcoming shifts.
  • List prioritiesList the priority levels configured on the account (P1, P2, …) — the lookup step before setting an incident's priority, which PagerDuty addresses by priority id rather than by name.
  • List schedulesList the on-call schedules on the connected PagerDuty account, so an escalation policy or an on-call lookup can be addressed by schedule id.
  • List servicesList the technical services on the connected PagerDuty account — the entry point for finding the service id an incident should be raised against.
  • List usersList the users on the connected PagerDuty account, so an incident can be assigned or an on-call rotation attributed to a person.
  • Update incidentDestructiveChange a PagerDuty incident — acknowledge, resolve or reopen it, change its urgency or priority, reassign it to named users, escalate it to a level of its policy, or move it to another escalation policy.

Triggers

  • Incident acknowledged (webhook)Starts the moment a PagerDuty incident is acknowledged, delivered by a webhook instead of polling the incident list.
  • Incident resolved (webhook)Starts the moment a PagerDuty incident is resolved, delivered by a webhook instead of polling the incident list.
  • Incident triggered (webhook)Starts the moment a new PagerDuty incident is triggered, delivered by a webhook instead of polling the incident list.
  • Incidents for the agentAnswers as an agent in PagerDuty: when an incident is triggered the agent opens a conversation on it and posts its findings as incident notes; later notes that mention the agent continue that conversation.
  • New incidentStarts when a new incident is triggered in PagerDuty.

Product names, logos and brands are the property of their respective owners and are used here for identification only. Their use does not imply endorsement by, or affiliation with, those owners.