PagerDuty

Connect your own PagerDuty account by saving your REST API key, after checking it actually works. Get a key from PagerDuty: Integrations > Developer Tools > API Access Keys > Create New API Key.

List the connected PagerDuty accounts and whether each saved REST API key still works.

Disconnect a PagerDuty account: deletes the saved REST API key. Nothing in PagerDuty itself is changed; the account's own incidents, services, and configuration are untouched.

Save a per-service Integration Key (routing key) used by Events API v2 and/or Change Events API. Find it on the service's Integrations tab in PagerDuty -- each integration (e.g. 'Events API v2') has its own key.

List saved per-service Integration Keys (routing keys) for Events API v2 / Change Events API. Keys themselves are never echoed back in full.

Permanently delete a saved Integration Key. Does not affect anything in PagerDuty itself -- only removes it from Imperal's storage.

List incidents in the connected PagerDuty account, optionally filtered by status, service, urgency, and date range.

Read one incident in full: status, urgency, service, escalation policy, assignees, and its PagerDuty web URL.

Create a new incident manually on a service (e.g. reporting a problem noticed outside of automated monitoring). Requires a From-email user on the connection.

Change an incident's status: acknowledge, resolve, or reopen (set back to triggered).

Reassign an incident to different users.

Set or clear an incident's priority level.

Merge one or more source incidents into a target incident. Source incidents are closed and their alerts move to the target.

Snooze an incident for N seconds -- it stops notifying and reopens automatically if not resolved by then.

Add a note to an incident -- visible to everyone with access to it.

Read the notes left on an incident.

List the individual alerts grouped into one incident.

Read the full activity timeline of an incident -- every trigger, acknowledge, escalate, reassign, resolve and note event, in order.

Run a saved Response Play against an incident -- executes its predefined set of actions (notify responders, run status update, etc.).

Acknowledge or resolve several incidents in one call, by explicit incident ids. Continues past per-item failures and reports each result.

List services (the things that receive alerts and generate incidents) in the connected PagerDuty account, optionally filtered by name.

Read one PagerDuty service in full: its status, escalation policy, and description.

Create a new PagerDuty service (a monitored system/component that generates incidents), attached to an escalation policy.

Update an existing service's name and/or escalation policy. Only given fields change.

Permanently delete a PagerDuty service. Cannot be undone -- incidents tied to it remain but the service configuration is gone.

List the integrations (event sources / Integration Keys) configured on one service -- each one's own routing_key powers Events API v2 and Change Events API calls for that specific integration.

Add a new integration to a service (e.g. a generic Events API integration, or a specific vendor like Datadog/Prometheus). Returns an Integration Key you can save via save_integration_key for Events API v2 / Change Events API calls.

Permanently remove an integration from a service. Any external system still using its old integration key will stop being able to send alerts.

List escalation policies (who gets notified, in what order, and how fast it escalates) in the connected PagerDuty account.

Read one escalation policy in full, including its rule count and loop/handoff settings.

Create a new escalation policy with a single rule targeting one or more users, with a configurable escalation delay and repeat count.

Update an escalation policy's name and/or repeat-loop count. Only given fields change.

Permanently delete an escalation policy. Fails if any service still references it -- reassign those services to another policy first.

List on-call schedules (rotations) configured in the connected PagerDuty account, optionally filtered by name.

Read one on-call schedule in full, including its current rotation users and time zone.

Create a new on-call rotation schedule with one layer of users rotating on a fixed interval (daily or weekly).

Permanently delete an on-call schedule. Fails if an escalation policy still references it.

Create a one-off override on a schedule -- e.g. swap who's on call for vacation coverage, without changing the underlying rotation.

Remove a schedule override, reverting to the underlying rotation for that time window.

List who is currently on call (or will be), optionally filtered by schedule ids or escalation policy ids, within a time window.

List users registered in the connected PagerDuty account, optionally filtered by name/email substring or team ids.

Read one PagerDuty user's profile in full.

Create a new user in the connected PagerDuty account and send them an invite email.

Update an existing PagerDuty user's name and/or role. Only given fields change.

Permanently remove a user from the connected PagerDuty account. They are also removed from any schedules/escalation policies referencing them.

List teams defined in the connected PagerDuty account, optionally filtered by name substring.

Create a new team to group users, services, and escalation policies.

Permanently delete a team. Members, services, and policies keep existing -- they simply lose this team association.

Add a user to a team with a given role (manager or member).

Remove a user from a team.

List business services -- the non-technical capabilities (e.g. 'Online Checkout') that group technical services for stakeholder-facing status.

Create a new business service -- a non-technical capability stakeholders can watch, made up of one or more technical services underneath it.

Update an existing business service's name and/or description.

Permanently delete a business service. Cannot be undone.

List the technical-service dependencies mapped to one business service -- which underlying services feed its status.

Map a technical service as a dependency of a business service, so the business service's health reflects that underlying service's incidents.

Remove a technical service's dependency mapping from a business service.

List the priority levels (P1-P5 style) configured on the connected PagerDuty account -- used to set/change an incident's priority.

List tags defined in the connected PagerDuty account -- labels attachable to users, teams, escalation policies, or services.

Create a new tag on the connected PagerDuty account.

Permanently delete a tag from the account -- removes it from every resource it was attached to.

Attach an existing tag to a user, team, escalation policy, or service.

Detach a tag from a user, team, escalation policy, or service.

List custom incident fields configured on the connected PagerDuty account -- structured metadata attachable to incidents.

Create a new custom incident field on the connected PagerDuty account.

Permanently delete a custom incident field. Cannot be undone.

Set a custom field's value on one specific incident.

List event orchestrations -- the rule sets that decide which service (and with what enrichment) an incoming event turns into an incident.

Create a new event orchestration -- a rule-based router that decides which service an incoming event becomes an incident on.

Read one event orchestration in full.

Permanently delete an event orchestration. Cannot be undone.

Read one event orchestration's router rules -- the conditions that decide which service an event is routed to.

List incident workflows -- reusable multi-step automated response sequences (e.g. notify + create Slack channel + run a script).

Read one incident workflow in full.

Manually trigger an incident workflow to run against a specific incident right now.

List incident workflow triggers -- what automatically starts a workflow (e.g. incident created on a given service).

List automation actions (runbook automation) configured in the connected PagerDuty account -- scripts/actions that can be invoked directly from an incident.

Read one automation action in full.

Invoke a runbook automation action directly against a specific incident.

List automation runners -- the registered execution environments (Runbook Automation Runner / Process Automation) that carry out automation actions.

List webhook subscriptions (Webhooks v3) configured on the connected PagerDuty account -- which events push notifications to which URL.

Subscribe to PagerDuty events (e.g. incident.triggered, incident.acknowledged, incident.resolved) so PagerDuty POSTs them to your URL as they happen.

Read one webhook subscription's full configuration.

Change a webhook subscription's URL, event list, and/or active state.

Permanently remove a webhook subscription. Cannot be undone.

Send a test ping event to a webhook subscription so you can confirm your endpoint receives it.

Send a new alert into PagerDuty via Events API v2 -- creates (or adds to) an incident on the service tied to the given integration key. Provide either integration_key_id (from list_integration_keys) or a raw routing_key directly.

Acknowledge or resolve an existing alert via Events API v2, using the dedup_key returned by trigger_event (or your own external key).

Send a change event (e.g. a deploy) to PagerDuty's Change Events API -- tracked alongside incidents for correlation, without creating an incident itself. Provide either integration_key_id or a raw routing_key.

Read aggregated incident analytics (mean time to acknowledge/resolve, engagement) grouped by service over a date range.

List audit trail records -- PagerDuty's own log of who changed what configuration and when, optionally filtered by date range and action type.

Value-add report: build one aggregated health snapshot across every service in the connected PagerDuty account -- open incident counts, escalation policy coverage, services with no integrations configured (silent services that can never receive alerts), and disabled services.