Pagerduty

✅ Authorization

Tools	Status
Pre-built authorization (OAuth)	✅
Credentials auto-refresh	✅
Pre-built authorization UI	✅
Custom authorization UI	✅
Expired credentials detection	✅

✅ Read & write data

Tools	Status
Pre-built integrations	✅
API unification	✅
2-way sync	✅
Webhooks from Tenklo on data modifications	✅
Real-time webhooks from 3rd-party API	✅
Proxy requests	✅

✅ Observability & data quality

Tools	Status
HTTP request logging	✅
End-to-end type safety	✅
Data runtime validation	✅
OpenTelemetry export	✅
Slack alerts on errors	✅
Integration status API	✅

✅ Customization

Tools	Status
Create or customize use-cases	✅
Pre-configured pagination	🚫 (time to contribute: <48h)
Pre-configured rate-limit handling	🚫 (time to contribute: <48h)
Per-customer configurations	✅

Others

Function name	Description	Type	Source code
`add-incident-status-update-subscribers`	Subscribe users or teams to status updates for a PagerDuty incident.	Action	🔗 Github
`add-team-escalation-policy`	Associate an escalation policy with a team.	Action	🔗 Github
`add-team-member`	Add a user to a team with a given role.	Action	🔗 Github
`assign-entity-tags`	Add and/or remove tags on a user, team, or escalation policy in one call.	Action	🔗 Github
`bulk-update-incident-alerts`	Manage or unmanage multiple alerts on an incident in a single call.	Action	🔗 Github
`bulk-update-incidents`	Acknowledge, resolve, reassign, or escalate multiple incidents in a single call.	Action	🔗 Github
`count-incidents`	Get a count of incidents matching a filter, without fetching the incident records themselves.	Action	🔗 Github
`create-business-service`	Create a business service.	Action	🔗 Github
`create-escalation-policy`	Create an escalation policy with one or more escalation rules.	Action	🔗 Github
`create-incident-note`	Add a note to an incident.	Action	🔗 Github
`create-incident-responder-request`	Request additional responders (users, teams, or escalation policies) join an incident.	Action	🔗 Github
`create-incident-status-update`	Post a human-readable status update on an incident (visible to subscribers).	Action	🔗 Github
`create-incident`	Create a new incident against a service.	Action	🔗 Github
`create-maintenance-window`	Create a maintenance window suppressing alerts on one or more services for a time range.	Action	🔗 Github
`create-schedule-overrides`	Create one or more overrides on a schedule (temporarily replace who is on-call for a time window).	Action	🔗 Github
`create-schedule`	Create an on-call schedule with one or more layers.	Action	🔗 Github
`create-service-integration`	Create a new integration (event source) on a service.	Action	🔗 Github
`create-service`	Create a service under an escalation policy.	Action	🔗 Github
`create-tag`	Create a tag.	Action	🔗 Github
`create-team`	Create a team.	Action	🔗 Github
`create-user-contact-method`	Add a new contact method to a user.	Action	🔗 Github
`create-user-notification-rule`	Add a new notification rule to a user.	Action	🔗 Github
`create-user`	Create a new user on the account.	Action	🔗 Github
`delete-business-service`	Delete a business service.	Action	🔗 Github
`delete-escalation-policy`	Delete an escalation policy.	Action	🔗 Github
`delete-incident-note`	Delete a note from an incident.	Action	🔗 Github
`delete-maintenance-window`	Delete or end a maintenance window.	Action	🔗 Github
`delete-schedule-override`	Delete a single override from a schedule.	Action	🔗 Github
`delete-schedule`	Delete a schedule.	Action	🔗 Github
`delete-service`	Delete a service.	Action	🔗 Github
`delete-tag`	Delete a tag.	Action	🔗 Github
`delete-team`	Delete a team.	Action	🔗 Github
`delete-user-notification-rule`	Delete a notification rule from a user.	Action	🔗 Github
`delete-user`	Delete a user from the account.	Action	🔗 Github
`get-business-service`	Retrieve a single business service.	Action	🔗 Github
`get-current-user`	Retrieve the user associated with the current API credentials.	Action	🔗 Github
`get-entity-tags`	List the tags assigned to a user, team, or escalation policy.	Action	🔗 Github
`get-incident-alert`	Retrieve a single alert on an incident.	Action	🔗 Github
`get-incident`	Retrieve a single incident.	Action	🔗 Github
`get-log-entry`	Retrieve a single log entry.	Action	🔗 Github
`get-maintenance-window`	Retrieve a single maintenance window.	Action	🔗 Github
`get-schedule`	Retrieve a single schedule, including its layers and assigned users.	Action	🔗 Github
`get-service-integration`	Retrieve a single integration on a service.	Action	🔗 Github
`get-service`	Retrieve a single service, including its embedded escalation policy and integrations.	Action	🔗 Github
`get-tag`	Retrieve a single tag.	Action	🔗 Github
`get-tagged-entities`	List the users, teams, or escalation policies that carry a given tag.	Action	🔗 Github
`get-team`	Retrieve a single team.	Action	🔗 Github
`get-user-contact-method`	Retrieve a single contact method for a user.	Action	🔗 Github
`get-user-notification-rule`	Retrieve a single notification rule for a user.	Action	🔗 Github
`get-user`	Retrieve a single user.	Action	🔗 Github
`get-vendor`	Retrieve a single vendor.	Action	🔗 Github
`list-business-services`	List business services (higher-level business-facing services distinct from technical Services).	Action	🔗 Github
`list-escalation-policies`	List escalation policies, optionally filtered by user or team.	Action	🔗 Github
`list-incident-alerts`	List the alerts attached to an incident.	Action	🔗 Github
`list-incident-log-entries`	List the timeline of log entries (state changes) for an incident.	Action	🔗 Github
`list-incident-notes`	List notes (annotations) on an incident	Action	🔗 Github
`list-incident-status-update-subscribers`	List users/teams subscribed to status updates for an incident.	Action	🔗 Github
`list-incidents`	List incidents, optionally filtered by service, team, user, status, urgency, or date range.	Action	🔗 Github
`list-log-entries`	List the account-wide log entries feed (every incident/alert state-change event across the account).	Action	🔗 Github
`list-maintenance-windows`	List maintenance windows, optionally filtered by service or team.	Action	🔗 Github
`list-oncalls`	List who is currently on-call across every escalation policy and schedule on the account.	Action	🔗 Github
`list-priorities`	List the account's configured incident priority levels (P1-P5).	Action	🔗 Github
`list-schedule-overrides`	List overrides on a schedule within a time window.	Action	🔗 Github
`list-schedule-users`	List the users who are on-call according to a schedule within a time window.	Action	🔗 Github
`list-schedules`	List on-call schedules (legacy/v2 schedule model).	Action	🔗 Github
`list-services`	List services, optionally filtered by team or name.	Action	🔗 Github
`list-tags`	List tags on the account.	Action	🔗 Github
`list-team-members`	List the members of a team.	Action	🔗 Github
`list-teams`	List teams on the account.	Action	🔗 Github
`list-user-contact-methods`	List a user's contact methods (email, SMS, phone, push channels).	Action	🔗 Github
`list-user-notification-rules`	List a user's notification rules (how/when they get notified of assignments).	Action	🔗 Github
`list-users`	List users on the account, optionally filtered by team.	Action	🔗 Github
`list-vendors`	List the global catalog of integration vendor types	Action	🔗 Github
`merge-incident`	Merge one or more source incidents into a destination incident.	Action	🔗 Github
`preview-schedule`	Preview the computed on-call entries for a schedule definition without saving it.	Action	🔗 Github
`remove-incident-status-update-subscriber`	Unsubscribe a single user or team from status updates for an incident.	Action	🔗 Github
`remove-team-escalation-policy`	Remove an escalation policy's association with a team.	Action	🔗 Github
`remove-team-member`	Remove a user from a team.	Action	🔗 Github
`snooze-incident`	Snooze an incident for a given duration (re-triggers it later if not resolved).	Action	🔗 Github
`update-business-service`	Update a PagerDuty business service.	Action	🔗 Github
`update-escalation-policy`	Update an escalation policy's name, description, or rules.	Action	🔗 Github
`update-incident-alert`	Manage or unmanage (resolve/trigger) a single alert on an incident.	Action	🔗 Github
`update-incident-note`	Update the content of an existing incident note.	Action	🔗 Github
`update-incident`	Update an incident: acknowledge, resolve, reassign, escalate, retitle, or change urgency/priority	Action	🔗 Github
`update-maintenance-window`	Update a maintenance window's time range, description, or scoped services.	Action	🔗 Github
`update-schedule`	Update a schedule's name, time zone, or layers.	Action	🔗 Github
`update-service-integration`	Update an existing integration on a service	Action	🔗 Github
`update-service`	Update an existing PagerDuty service's fields, including reassigning its escalation policy.	Action	🔗 Github
`update-team`	Update a PagerDuty team name, description, or default role.	Action	🔗 Github
`update-user-notification-rule`	Update an existing notification rule.	Action	🔗 Github
`update-user`	Update a user's fields (name, job title, role, time zone, etc).	Action	🔗 Github
`business-services`	Sync business services.	Sync	🔗 Github
`incidents`	Sync incidents.	Sync	🔗 Github
`log-entries`	Sync the account-wide log entries feed (every incident/alert state-change event across the account).	Sync	🔗 Github
`maintenance-windows`	Sync maintenance windows.	Sync	🔗 Github
`oncalls`	Sync the current on-call snapshot across every escalation policy and schedule on the account.	Sync	🔗 Github
`priorities`	Sync the account's configured incident priority levels.	Sync	🔗 Github
`schedules`	Sync on-call schedules (legacy/v2 schedule model), including each schedule's layers and assigned users	Sync	🔗 Github
`services`	Sync PagerDuty services, including each service's embedded escalation-policy reference and integrations array.	Sync	🔗 Github
`tags`	Sync tags	Sync	🔗 Github
`teams`	Sync teams.	Sync	🔗 Github
`users`	Sync PagerDuty users.	Sync	🔗 Github
`vendors`	Sync the global integration-vendor-type catalog.	Sync	🔗 Github

Access requirements

Pre-Requisites	Status	Comment
Paid dev account	❓
Paid test account	❓
Partnership	❓
App review	❓
Security audit	❓

Setup guide

No setup guide yet.

Need help getting started? Get help in the community.

Contribute improvements to the setup guide by editing this page

Useful links

Contribute useful links by editing this page

API gotchas

Scopes should be either read or write.

Contribute API gotchas by editing this page

Overview

Pre-built tooling

Pre-built integrations

Access requirements

Setup guide

Useful links

API gotchas

Pre-built tooling

Others

Access requirements

Setup guide

Useful links

API gotchas

On this page

Pagerduty

OverviewCopy Anchor Link

Pre-built tooling

Pre-built integrations

Access requirements

Setup guide

Useful links

API gotchas

Pre-built toolingCopy Anchor Link

OthersCopy Anchor Link

Access requirementsCopy Anchor Link

Setup guideCopy Anchor Link

Useful linksCopy Anchor Link

API gotchasCopy Anchor Link

On this page

Overview

Pre-built tooling

Others

Access requirements

Setup guide

Useful links

API gotchas