How do I connect Pagerduty to Operator?

You authorize Pagerduty once from your Operator dashboard. Operator holds the connection and refreshes the access token for you, so your agent keeps working with Pagerduty without you signing in again.

Can my agent work with issues and pull requests in Pagerduty?

Yes. It can open and comment on issues, review pull requests, manage labels, and read project details when you ask. Teams use it to triage incoming work, draft release notes, and post a summary of what changed without leaving chat.

Do I need to write code or manage Pagerduty API keys?

No code and no API keys. You authorize Pagerduty through a normal sign in and Operator handles the connection, so there is nothing to wire up or host.

Can my agent use Pagerduty together with my other apps?

Yes. The same agent reaches every app you connect, so it can move between Pagerduty and tools like GitHub, Supabase, Launch darkly in one job, reading from one and acting in another without you wiring anything between them.

← All integrations

Connect Pagerduty to OpenClaw on Operator.io

Pagerduty is a real-time incident management platform for IT teams. It helps organizations resolve critical issues faster with on-call scheduling, alerting, and response automation.

Developer Tools & DevOps363 actions

Get started

Automate Pagerduty with AI

On Operator, an OpenClaw agent pilots Pagerduty for you. It reads your message, plans the steps, and runs them in Pagerduty, using actions like add service to incident workflow trigger, aggregate escalation policy incident metrics, aggregate incident metrics with filters.

Your agent reaches Pagerduty directly or through connectors like Composio MCP and Pipedream MCP, which handle the sign in and token refresh for you, so there is nothing to wire up and no API keys to paste.

What your agent can do with Pagerduty

Your agent can call any of these Pagerduty actions by name as part of a larger task. Ask for the outcome you want and it picks the right ones.

Add service to incident workflow trigger

Adds a service to an existing incident workflow trigger in PagerDuty, enabling the trigger to fire for incidents on that service. Associates a specific service with an incident workflow trigger to automate incident management for that se...

Aggregate escalation policy incident metrics

This endpoint analyzes and aggregates incident metrics across all escalation policies in PagerDuty. It allows for detailed filtering and customization of the analysis, enabling users to gain insights into incident patterns, response time...

Aggregate incident metrics with filters

Retrieves and aggregates metrics for incidents across all services in PagerDuty. This endpoint allows for extensive filtering and customization of incident data, enabling detailed analysis of operational performance. It's particularly us...

Associate service dependencies

Associates multiple service dependencies in PagerDuty, allowing you to define relationships between supporting and dependent services. This endpoint is used to establish a hierarchical structure of services, which is crucial for effectiv...

Associate team with automation action

This endpoint associates a specific team with an automation action in PagerDuty. It allows you to link a team to an automated workflow, enabling better organization and management of automation actions within your incident response proce...

Audit escalation policy records

Retrieves the audit records for a specific escalation policy in PagerDuty. This endpoint allows users to access a detailed history of changes made to the escalation policy, including modifications to escalation rules, associated services...

Convert service rule by id

Converts a service's Event Rules to Event Orchestration rules. This migration endpoint automatically converts Service Event Rules to the newer Event Orchestration format, identically re-creating existing rules while retaining the same be...

Count paused incident reports

Retrieves the count of paused incident reports in the PagerDuty system. This endpoint is part of PagerDuty's Incident Management and Analytics features, providing a quick way to quantify the number of incidents that are currently in a pa...

Create a custom field for an incident type

Create a Custom Field for an Incident Type. Custom Fields (CF) are a feature which will allow customers to extend Incidents with their own custom data, to provide additional context and support features such as customized filtering, sear...

Create a field option for a custom field

Creates a new field option for a custom field on an incident type. Field options represent the allowed values for multi-value or dropdown custom fields. Before using this action: 1. You need a valid incident type ID or name (use LIST_INC...

Create and manage custom incident fields

Creates a new custom field for incidents in PagerDuty. This endpoint allows you to define additional data points to be associated with incidents, enhancing incident management and reporting capabilities. Custom fields can be used to stor...

Create an incident type

Create a new incident type. Incident Types are a feature which will allow customers to categorize incidents, such as a security incident, a major incident, or a fraud incident.  > ### Early Access > This endpoint i...

Create a ruleset

Creates a new Ruleset in PagerDuty for managing incident routing and notification rules. This endpoint allows you to define a named set of rules that determine how incidents are processed and directed to specific teams or users. It's par...

Create incident workflow trigger

Creates a new incident workflow trigger in PagerDuty. Triggers define when and how incident workflows are activated - either automatically based on conditions or manually by responders. Trigger types: 'manual' (started by responders) or...

Create automation runner endpoint

Creates a new Runbook Automation runner in PagerDuty's Automation Actions. A runner is the execution engine that invokes automation actions. Only 'runbook' type runners can be created via API. Required fields: runner_type ('runbook'), na...

Create business service

This endpoint creates a new Business Service in PagerDuty, which represents a specific service or application that can be monitored and managed within the incident management platform. It allows you to define essential properties of the...

Create escalation policy

Creates a new escalation policy in PagerDuty, defining how incidents are escalated to different responders or teams. This endpoint allows you to set up a structured response plan for managing incidents, including escalation rules, target...

Create event orchestration

Creates a new Event Orchestration in PagerDuty, which defines how incoming events are processed and routed to appropriate services. This endpoint allows you to set up a configuration that manages the flow of events from various integrati...

Create event rule in ruleset

Creates a new Event Rule within a specified Ruleset in PagerDuty's incident management system. This endpoint allows you to define complex conditions for event matching and specify actions to be taken when an event meets those conditions....

Create extension object

Creates a new extension in PagerDuty, allowing for additional functionality or integrations to be added to your services. This endpoint is used to set up webhooks, custom integrations, or other specific features that enhance the capabili...

Create handoff notification rule

Creates a new on-call handoff notification rule for a specific user in PagerDuty. This endpoint allows you to set up automated notifications for when a user is about to start or end their on-call shift. It defines how and when the user s...

Create incident field option

Creates a new field option for a specific custom field in PagerDuty's incident management system. This endpoint allows you to add predefined options to custom fields, enhancing the ability to categorize and filter incidents with consiste...

Create incident record

Creates a new incident in PagerDuty with specified details and assignments. Use this endpoint when an event requires immediate attention from on-call teams. It supports comprehensive incident documentation, including priority, urgency, a...

Create incident workflow

This endpoint creates a new Incident Workflow in PagerDuty, allowing users to define a series of automated steps to be executed during incident response. It enables the setup of complex, multi-step processes that can include actions like...

Create incident workflow instance

Creates a new instance of an incident workflow for a specific incident in PagerDuty. This endpoint allows you to initiate a predefined workflow process for managing and resolving an ongoing incident. It links the workflow instance to a p...

Create integration for orchestration

Creates a new integration for an existing event orchestration in PagerDuty. This action adds an integration to an event orchestration, enabling it to receive events from external monitoring tools, alerting systems, or custom applications...

Create integration for service

Creates a new integration for a PagerDuty service to enable incident creation from external monitoring tools and systems. Integrations can be either generic (using 'type' parameter) or vendor-specific (using 'vendor' parameter). **Common...

Create maintenance window object

Creates a new maintenance window in PagerDuty, allowing you to schedule periods of planned maintenance for specific services. During a maintenance window, incidents are not created for the affected services, preventing unnecessary alerts...

Create new schedule layer

Creates a new on-call schedule in PagerDuty with one or more rotation layers. A schedule defines who is on-call at any given time. Each schedule contains one or more layers that specify rotation patterns, with each layer having: - User a...

Create new service

Creates a new service in PagerDuty, which is a key component for managing incidents and alerts. This endpoint allows you to set up a service with various configurations including escalation policies, incident urgency rules, support hours...

Create new tag in system

Creates a new tag in PagerDuty for labeling and categorizing entities. This endpoint allows users to add a custom label to their PagerDuty account, which can be used to organize and filter various resources such as incidents, services, o...

Create new team with details

Creates a new team in PagerDuty for organizing users, incident management, and on-call schedules. Required: team.name (unique team name) Optional: team.description, team.parent (for nested hierarchies), team.default_role Use when setting...

Create new webhook subscription

Creates a new webhook subscription in PagerDuty to receive specific event notifications. This endpoint allows users to set up automated notifications for various incident-related events, such as triggers, acknowledgments, and resolutions...

Create or update status page post

Creates a new post on a PagerDuty Status Page to communicate service status to users. Use this action to publish incident reports (for service disruptions) or maintenance announcements (for scheduled work). Each post includes a title, ty...

Create or update status page postmortem

Creates or updates a postmortem for a specific status page post in PagerDuty. This endpoint allows you to add detailed analysis and insights about an incident after its resolution. The postmortem can include rich-text content and offers...

Create response play for incidents

Creates a new Response Play in PagerDuty, which is a predefined set of actions to be executed in response to an incident. This endpoint allows you to configure automated responses, including adding subscribers, assigning responders, sett...

Create schedule overrides configuration

Creates one or more overrides for a specific schedule in PagerDuty. This endpoint allows you to temporarily modify the on-call schedule by assigning different users for specific time periods. It's useful for handling planned absences, sh...

Create service event rule

Creates a new event rule for a specific service in PagerDuty. This endpoint allows you to define complex conditions and actions for handling incoming events, enabling automated incident management and alert routing. Use this when you nee...

Create statuspage subscription

Creates a new subscription for a PagerDuty status page. This endpoint allows users to set up notifications for specific status pages or components within those pages. It's used to keep subscribers informed about updates, incidents, or ch...

Create status update template

Creates a new status update template in PagerDuty for standardized incident notifications. Templates provide consistent, pre-formatted messages for stakeholder updates across email, SMS, push, and Slack. Supports dynamic variables like {...

Create user notification rule

Creates a new notification rule for a specific user in PagerDuty. This endpoint allows you to define how and when a user should be notified about assigned incidents. You can specify the delay before notification, the method of contact, a...

Create user object

Creates a new user in the PagerDuty system with the specified attributes. This endpoint should be used when onboarding new team members or adding users to your PagerDuty account. It allows you to set up essential user information, includ...

Create user status update notification rule

Creates a new status update notification rule for a specific user in PagerDuty. This endpoint allows you to define how a user will be notified about incident status updates. It's used to customize notification preferences for individual...

Create workflow integration connection

Create a new Workflow Integration Connection. Scoped OAuth requires: `workflow_integrations:connections.write`

Delete account subscription by id

Deletes the account subscription associated with a specific business service in PagerDuty. This endpoint is used to terminate the subscription or billing relationship between a business service and the account. It should be used when you...

Delete a custom field for an incident type

Deletes a custom field from an incident type. This permanently removes the field definition and associated options, but does not affect historical data on existing incidents. Prerequisites: 1. Valid incident type ID or name (use LIST_INC...

Delete addon by id

Deletes a specific add-on from the PagerDuty account using its unique identifier. This endpoint should be used when you want to remove an integration or extension that is no longer needed or active in your PagerDuty setup. It's important...

Delete a field option for a custom field

Deletes a specific field option from a custom field on an incident type. Field options represent the allowed values for multi-value or dropdown custom fields. This action permanently removes a field option. If incidents are using this fi...

Plus 315 more Pagerduty actions your agent can call.

How to connect Pagerduty

You authorize Pagerduty once from your dashboard. Operator holds the connection and refreshes the access tokens on its own, so your agent keeps working with Pagerduty without you signing in again. The same setup unlocks every other app your agent can reach, so you only do it once.

When you are ready, the get started guide walks through standing up your OpenClaw agent.

Common questions about Pagerduty

How do I connect Pagerduty to Operator?: You authorize Pagerduty once from your Operator dashboard. Operator holds the connection and refreshes the access token for you, so your agent keeps working with Pagerduty without you signing in again.
Can my agent work with issues and pull requests in Pagerduty?: Yes. It can open and comment on issues, review pull requests, manage labels, and read project details when you ask. Teams use it to triage incoming work, draft release notes, and post a summary of what changed without leaving chat.
Do I need to write code or manage Pagerduty API keys?: No code and no API keys. You authorize Pagerduty through a normal sign in and Operator handles the connection, so there is nothing to wire up or host.
Can my agent use Pagerduty together with my other apps?: Yes. The same agent reaches every app you connect, so it can move between Pagerduty and tools like GitHub, Supabase, Launch darkly in one job, reading from one and acting in another without you wiring anything between them.