All integrationsMonitoring

PagerDuty

Run incident response from workflows: open, acknowledge, resolve and reassign PagerDuty incidents, add notes and status updates, send alert events, see who is on call, and pause services for maintenance.

actions
24
triggers
3

Triggers

Start a workflow when something happens in PagerDuty.

  • New PagerDuty incidentRuns when an incident is opened in PagerDuty.
  • PagerDuty incident acknowledgedRuns when someone acknowledges an incident in PagerDuty.
  • PagerDuty incident resolvedRuns when an incident is resolved in PagerDuty.

Actions

Steps a workflow can run in PagerDuty.

  • Find incidentsFind incidents, newest first, by status, urgency, service and when they were opened.
  • Get incidentGet one incident: its status, urgency, service and who it is assigned to.
  • Create incidentOpen an incident on a service. PagerDuty notifies whoever is on call for it, or the people you assign.
  • Acknowledge incidentAcknowledge an incident, so PagerDuty stops paging people about it.
  • Resolve incidentResolve an incident, optionally saying how it was fixed.
  • Update incidentChange an incident's title, urgency or priority, or escalate it to another level of its escalation policy.
  • Reassign incidentHand an incident to other people, or to an escalation policy. PagerDuty notifies them.
  • Snooze incidentSnooze an acknowledged incident: it goes back to triggered, and pages again, after the time you give.
  • Add note to incidentAdd a note to an incident's timeline, for the responders.
  • List incident notesList the notes on an incident.
  • List incident alertsList the alerts grouped into an incident, with the details the monitoring tool sent.
  • Get incident timelineList what happened to an incident: when it was triggered, who was notified, acknowledged, reassigned and resolved it.
  • Send status updatePost a status update on an incident, emailed to the people subscribed to it. Needs a plan with status updates.
  • Send alert eventSend an alert to a service the way a monitoring tool does: trigger it (PagerDuty opens or adds to an incident), or later acknowledge or resolve it with its key.
  • List servicesList services by name, with the escalation policy each one pages.
  • Get serviceGet one service, with its escalation policy and its Events API V2 integration key for 'Send alert event'.
  • List escalation policiesList escalation policies: who gets paged, in what order.
  • List schedulesList on-call schedules and the people on them.
  • Get scheduleGet an on-call schedule and its shifts: who is on call when, for the next seven days unless you give a range.
  • Who is on callList who is on call now, or in a time range, with their email and escalation level. Narrow it to schedules or policies.
  • List usersList the people in your PagerDuty account, with their emails and roles.
  • List teamsList the teams in your PagerDuty account.
  • Create maintenance windowPause services for planned work: while the window is open, PagerDuty opens no incidents on them and pages nobody.
  • Delete maintenance windowRemove a maintenance window that hasn't started, or end one that is under way.

Automate PagerDuty with Lodol.

Connect PagerDuty and ask your AI for your first workflow.

Free plan, no credit card