# PagerDuty AI integration on Definable > PagerDuty helps you proactively manage your digital operations by collecting data signals from anywhere, interpreting those signals using machine learning, automatically engaging the right people, and accelerating resolution and learning. ## What this connects PagerDuty helps you proactively manage your digital operations by collecting data signals from anywhere, interpreting those signals using machine learning, automatically engaging the right people, and accelerating resolution and learning. Vendor: https://www.pagerduty.com ## Tools available **368** tools available. First 12: - `PAGERDUTY_ADD_SERVICE_TO_INCIDENT_WORKFLOW_TRIGGER` — 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 service. Prerequisites: - The incident workflow trigger must already exist (create with CREATE_A_TRIGGER) - The service must already exist in your account - The trigger must not be subscribed to all services Use when expanding automated workflows to additional services or incrementally rolling out workflows. This is an additive operation - use DELETE_INCIDENT_WORKFLOW_TRIGGER_SERVICE to remove services. Requires incident_workflows:write OAuth scope. - `PAGERDUTY_AGGREGATE_ESCALATION_POLICY_INCIDENT_METRICS` — 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 times, and escalation effectiveness. The endpoint is particularly useful for operational reviews, performance analysis, and identifying areas for improvement in incident management processes. It provides flexibility in data selection through various filters and supports different time-based aggregations for comprehensive reporting. - `PAGERDUTY_AGGREGATE_INCIDENT_METRICS_WITH_FILTERS` — 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 useful for generating reports, identifying trends, and assessing incident management efficiency over specified time periods. The endpoint supports various filtering criteria, time zone adjustments, and aggregation options, making it a powerful tool for both high-level overviews and granular incident analytics. However, users should be aware of the complexity of the filtering options and ensure they provide accurate parameters to obtain relevant data. - `PAGERDUTY_ASSOCIATE_SERVICE_DEPENDENCIES` — 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 effective incident management and impact analysis. It enables you to create multiple dependencies in a single API call, improving efficiency when setting up complex service relationships. Use this endpoint when you need to define or update the dependency structure of your services in PagerDuty, such as during initial setup, service restructuring, or when adding new services to your incident management workflow. - `PAGERDUTY_ASSOCIATE_TEAM_WITH_AUTOMATION_ACTION` — 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 processes. Use this endpoint when you need to assign responsibility for an automation action to a particular team or when restructuring your automation workflows. The association helps in tracking, auditing, and managing permissions for automation actions across different teams in your organization. Note that this endpoint only creates the association; it does not create new teams or automation actions. - `PAGERDUTY_AUDIT_ESCALATION_POLICY_RECORDS` — 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, and on-call schedules. It's particularly useful for compliance tracking, troubleshooting, and understanding how the incident response process has been adjusted over time. The audit records provide transparency into who made changes, what was changed, and when the changes occurred, helping teams maintain accountability and optimize their incident management workflows. - `PAGERDUTY_CONVERT_SERVICE_RULE_BY_ID` — 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 behavior. Note: Event Rules reached end-of-life in January 2025. This endpoint migrates from legacy Event Rules to Event Orchestration. Important: Conversion does NOT automatically enable Event Orchestration. You must manually enable it in the service Settings or via API for rules to take effect. Safe to run multiple times - returns existing orchestration URL if already converted. Works even when service has no event rules (returns success with orchestration URL). - `PAGERDUTY_COUNT_PAUSED_INCIDENT_REPORTS` — 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 paused state. It's particularly useful for generating high-level analytics, tracking incident management efficiency, and identifying trends in incident handling. The endpoint returns a simple count, making it ideal for dashboard displays or periodic system status checks. It should be used when a rapid overview of paused incidents is needed, but it won't provide detailed information about individual incidents. - `PAGERDUTY_CREATE_A_CUSTOM_FIELD_FOR_AN_INCIDENT_TYPE` — 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, search and analytics. Custom Fields can be applied to different incident types. > ### Early Access > This endpoint is in Early Access and may change at any time. You must pass in the X-EARLY-ACCESS header to access it. Scoped OAuth requires: `custom_fields.write` - `PAGERDUTY_CREATE_A_FIELD_OPTION_FOR_A_CUSTOM_FIELD` — 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_INCIDENT_TYPES to find one) 2. The incident type must have a custom field already created (use CREATE_A_CUSTOM_FIELD_FOR_AN_INCIDENT_TYPE) 3. The custom field should be of type 'multi_value' or 'multi_value_fixed' to support multiple options Use this action to add selectable options to custom fields, enabling users to choose from predefined values when categorizing or tagging incidents. Note: This is an Early Access endpoint that requires the X-EARLY-ACCESS header and the 'custom_fields.write' scope. - `PAGERDUTY_CREATE_AND_MANAGE_CUSTOM_INCIDENT_FIELDS` — 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 store various types of information such as environment, severity, or any other relevant metadata. The field can be configured with different data types and value constraints, allowing for flexible and structured data capture. Use this endpoint when you need to extend the incident data model with organization-specific information. Note that once created, certain properties of a custom field cannot be changed, so careful planning of field structure is important. - `PAGERDUTY_CREATE_AN_INCIDENT_TYPE` — 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 is in Early Access and may change at any time. You must pass in the X-EARLY-ACCESS header to access it. For more information see the [API Concepts Document](../../api-reference/ZG9jOjI3NDc5Nzc-api-concepts#incidentType) Scoped OAuth requires: `incident_types.write` ## Auth Auth schemes: `OAUTH2`, `API_KEY`. Managed by Definable: `OAUTH2` — no client credentials required from the user. ## How agents use PagerDuty Inside a Definable workflow, PagerDuty is one of the tools the **Distributor specialist** can call. Example coordination patterns: - **Researcher → PagerDuty** — the Researcher (GPT-5.5) pulls context from PagerDuty (records, threads, documents), synthesises findings, and briefs the rest of the team. - **Writer → Distributor → PagerDuty** — the Writer (Claude Opus 4.7) drafts copy in brand voice, the Verifier passes it, then the Distributor writes the result into PagerDuty (create record, post message, draft email). - **Designer / Engineer → Distributor → PagerDuty** — the Designer ships an asset or the Engineer ships a code change, the Distributor delivers it via PagerDuty (attach file, open PR comment, post status). The Verifier checks every PagerDuty call. On rate limit, schema drift, or auth refresh it self-heals and retries — the workflow completes without manual intervention. ## Categories - server monitoring — https://definable.ai/apps/category/server-monitoring/ - notifications — https://definable.ai/apps/category/notifications/ ## Related - HTML page: https://definable.ai/apps/pagerduty/ - Same category (server monitoring): https://definable.ai/apps/category/server-monitoring/ - All integrations: https://definable.ai/apps/ - Workflow (multi-agent loop): https://definable.ai/workflow/ - Apps llms.txt index: https://definable.ai/llms-apps.txt