PagerDuty API
Arcade Unoptimized
Tools that enable LLMs to interact directly with the Pagerduty API.
374tools
PagerDuty's API toolkit empowers developers to seamlessly integrate and manage incident response workflows through a variety of automated tools. Designed for interaction with the PagerDuty API, it facilitates comprehensive insight into incident management and team coordination.
Capabilities:
- Integrates and manages incident workflows, actions, and teams efficiently.
- Automates alert notifications, service integrations, and escalation policies.
- Enables customization of incident types and field options for enhanced filtering.
- Supports detailed analytics and metrics retrieval for incident performance.
OAuth:
- Provider: PagerDuty
- Scopes:
services.write,incident_workflows.write,users.write, among others.
Secrets: None required.
Available tools(374)
374 of 374 tools
| Tool name | Description | Secrets | |
|---|---|---|---|
Create a cache variable for a service event orchestration.
Use this tool to create a cache variable within a service event orchestration on PagerDuty. Cache variables store event data that can be used in orchestration rules for conditions or actions. Requires OAuth with `services.write` scope. | |||
Add an escalation policy to a team.
This tool adds an escalation policy to a specified team within an organization. It is useful for managing team response structures and assigning appropriate escalation policies to teams. Users should have 'teams.write' permissions to perform this update. | |||
Add a new note to a specific incident.
Use this tool to attach a note to an existing incident when documenting updates or additional information is necessary. Ideal for tracking the progress of resolving an issue.
Note: Understanding the request schema is necessary to properly create
the stringified JSON input object for execution.
This operation also requires path parameters.
Modes:
- GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't
already have it. Do NOT call repeatedly if you already received
the schema.
- EXECUTE: Performs the operation with the provided request body
JSON.
Note: You must also provide the required path parameters when executing.
If you need the schema, call with mode='get_request_schema' ONCE, then execute.
| |||
Create a new option for a custom field in PagerDuty services.
This tool is used to create a new option for a specified custom field in the PagerDuty services. It should be called when you want to extend the available options for a specific field. Requires `custom_fields.write` OAuth scope.
Note: Understanding the request schema is necessary to properly create
the stringified JSON input object for execution.
This operation also requires path parameters.
Modes:
- GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't
already have it. Do NOT call repeatedly if you already received
the schema.
- EXECUTE: Performs the operation with the provided request body
JSON.
Note: You must also provide the required path parameters when executing.
If you need the schema, call with mode='get_request_schema' ONCE, then execute.
| |||
Add a user to a specified team on PagerDuty.
This tool adds a user to a specified team using PagerDuty. It should be called when you need to integrate a user within a team structure in an organization. Note that attempting to add a user with a 'read_only_user' role will result in an error. OAuth scope 'teams.write' is required. | |||
Assign tags to PagerDuty entities like policies, teams, or users.
Assign or update tags for Escalation Policies, Teams, or Users in PagerDuty to facilitate filtering and organization. Use this tool to manage tags efficiently.
Note: Understanding the request schema is necessary to properly create
the stringified JSON input object for execution.
This operation also requires path parameters.
Modes:
- GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't
already have it. Do NOT call repeatedly if you already received
the schema.
- EXECUTE: Performs the operation with the provided request body
JSON.
Note: You must also provide the required path parameters when executing.
If you need the schema, call with mode='get_request_schema' ONCE, then execute.
| |||
Associate an Automation Action with a service.
This tool is used to associate a specified Automation Action with a service in PagerDuty. Call this tool when you need to link an action to a service for automation purposes.
Note: Understanding the request schema is necessary to properly create
the stringified JSON input object for execution.
This operation also requires path parameters.
Modes:
- GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't
already have it. Do NOT call repeatedly if you already received
the schema.
- EXECUTE: Performs the operation with the provided request body
JSON.
Note: You must also provide the required path parameters when executing.
If you need the schema, call with mode='get_request_schema' ONCE, then execute.
| |||
Associate an Automation Action with a team.
Use this tool to link a specific automation action to a designated team in PagerDuty. It should be called when there's a need to establish or update the association between an existing action and a team.
Note: Understanding the request schema is necessary to properly create
the stringified JSON input object for execution.
This operation also requires path parameters.
Modes:
- GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't
already have it. Do NOT call repeatedly if you already received
the schema.
- EXECUTE: Performs the operation with the provided request body
JSON.
Note: You must also provide the required path parameters when executing.
If you need the schema, call with mode='get_request_schema' ONCE, then execute.
| |||
Associate a runner with a specified team.
This tool allows you to associate a specific runner with a team in PagerDuty. Use it when you need to link automation actions runners to teams.
Note: Understanding the request schema is necessary to properly create
the stringified JSON input object for execution.
This operation also requires path parameters.
Modes:
- GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't
already have it. Do NOT call repeatedly if you already received
the schema.
- EXECUTE: Performs the operation with the provided request body
JSON.
Note: You must also provide the required path parameters when executing.
If you need the schema, call with mode='get_request_schema' ONCE, then execute.
| |||
Associate a service with an existing incident workflow trigger.
This tool associates a specific service with an existing incident workflow trigger in PagerDuty. It requires OAuth permission `incident_workflows.write`. Use this tool when you need to link a service to a workflow trigger for better incident management.
Note: Understanding the request schema is necessary to properly create
the stringified JSON input object for execution.
This operation also requires path parameters.
Modes:
- GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't
already have it. Do NOT call repeatedly if you already received
the schema.
- EXECUTE: Performs the operation with the provided request body
JSON.
Note: You must also provide the required path parameters when executing.
If you need the schema, call with mode='get_request_schema' ONCE, then execute.
| |||
Check if your account has a specific ability.
Use this tool to test whether your PagerDuty account has a specific ability or feature available. An ability can depend on factors like your pricing plan or account state, and this tool helps determine availability. | |||
Clear priority thresholds for business services.
This tool clears the priority thresholds for business services in the account, allowing any incident with a priority to impact them. It requires `services.write` OAuth scope. | |||
Convert service event rules to orchestration rules.
Use this tool to convert a service's event rules into equivalent event orchestration rules. This process makes existing event rules read-only, with future updates needing orchestration rules. This tool is vital for migrating as event rules will soon be deprecated. | |||
Create a new Alert Grouping Setting in PagerDuty.
This tool allows the creation of new Alert Grouping Settings for one or multiple services within the PagerDuty platform. It is used to define configurations in the Alert Grouper service. Requires 'services.write' OAuth scope.
Note: Understanding the request schema is necessary to properly create
the stringified JSON input object for execution.
Modes:
- GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't
already have it. Do NOT call repeatedly if you already received
the schema.
- EXECUTE: Performs the operation with the provided request body
JSON.
If you need the schema, call with mode='get_request_schema' ONCE, then execute. | |||
Create a new alert or incident template.
Use this tool to create a new template in PagerDuty, which can be used for alerts or incidents. Requires OAuth with `templates.write` scope. | |||
Create a script, process, or runbook automation action.
This tool creates an automation action such as a script, process automation, or runbook automation action in PagerDuty. Call this when you need to automate or manage workflows.
Note: Understanding the request schema is necessary to properly create
the stringified JSON input object for execution.
Modes:
- GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't
already have it. Do NOT call repeatedly if you already received
the schema.
- EXECUTE: Performs the operation with the provided request body
JSON.
If you need the schema, call with mode='get_request_schema' ONCE, then execute. | |||
Create a Process or Runbook Automation runner.
Use this tool to create a new Process Automation or Runbook Automation runner in PagerDuty.
Note: Understanding the request schema is necessary to properly create
the stringified JSON input object for execution.
Modes:
- GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't
already have it. Do NOT call repeatedly if you already received
the schema.
- EXECUTE: Performs the operation with the provided request body
JSON.
If you need the schema, call with mode='get_request_schema' ONCE, then execute. | |||
Create a new business service in PagerDuty.
Use this tool to create a new business service, which represents capabilities spanning multiple technical services, possibly owned by various teams. Make sure not to exceed the account limit of 5,000 business services. | |||
Create a cache variable for global event orchestration rules.
This tool creates a cache variable within a global event orchestration on PagerDuty. Cache variables are useful for storing event data that can be utilized in orchestration rules for conditions or actions. Ideal for managing and automating event-driven processes. | |||
Create a custom field option for incidents.
This tool creates a field option for a custom field in incidents, allowing users to extend incident data with custom options. It supports additional context, customized filtering, search, and analytics.
Note: Understanding the request schema is necessary to properly create
the stringified JSON input object for execution.
This operation also requires path parameters.
Modes:
- GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't
already have it. Do NOT call repeatedly if you already received
the schema.
- EXECUTE: Performs the operation with the provided request body
JSON.
Note: You must also provide the required path parameters when executing.
If you need the schema, call with mode='get_request_schema' ONCE, then execute.
| |||
Create a new escalation policy in PagerDuty.
Use this tool to create a new escalation policy on PagerDuty. Escalation policies are used to determine which users are alerted and when. At least one escalation rule must be included. Requires OAuth scope: 'escalation_policies.write'.
Note: Understanding the request schema is necessary to properly create
the stringified JSON input object for execution.
Modes:
- GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't
already have it. Do NOT call repeatedly if you already received
the schema.
- EXECUTE: Performs the operation with the provided request body
JSON.
If you need the schema, call with mode='get_request_schema' ONCE, then execute. | |||
Create an integration for event orchestration in PagerDuty.
This tool creates an integration associated with a specified event orchestration in PagerDuty. Use this to obtain a Routing Key for sending events. Requires `event_orchestrations.write` permission.
Note: Understanding the request schema is necessary to properly create
the stringified JSON input object for execution.
This operation also requires path parameters.
Modes:
- GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't
already have it. Do NOT call repeatedly if you already received
the schema.
- EXECUTE: Performs the operation with the provided request body
JSON.
Note: You must also provide the required path parameters when executing.
If you need the schema, call with mode='get_request_schema' ONCE, then execute.
| |||
Create a new event rule within a ruleset.
This tool creates a new event rule in a specified ruleset in PagerDuty. It should be called when you need to set up routing actions based on event content. Note: functionalities related to rulesets and event rules will be deprecated soon. Consider migrating to Event Orchestration.
Note: Understanding the request schema is necessary to properly create
the stringified JSON input object for execution.
This operation also requires path parameters.
Modes:
- GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't
already have it. Do NOT call repeatedly if you already received
the schema.
- EXECUTE: Performs the operation with the provided request body
JSON.
Note: You must also provide the required path parameters when executing.
If you need the schema, call with mode='get_request_schema' ONCE, then execute.
| |||
Create a Global Event Orchestration in PagerDuty.
This tool allows you to create a Global Event Orchestration, defining Global Rules and Router Rules for event processing and routing based on event content.
Note: Understanding the request schema is necessary to properly create
the stringified JSON input object for execution.
Modes:
- GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't
already have it. Do NOT call repeatedly if you already received
the schema.
- EXECUTE: Performs the operation with the provided request body
JSON.
If you need the schema, call with mode='get_request_schema' ONCE, then execute. | |||
Create a handoff notification rule for PagerDuty users.
This tool allows you to create a new handoff notification rule for users in PagerDuty. It should be called when you need to set a notification rule for on-call handoff events for a specific user. Requires `users.write` OAuth scope.
Note: Understanding the request schema is necessary to properly create
the stringified JSON input object for execution.
This operation also requires path parameters.
Modes:
- GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't
already have it. Do NOT call repeatedly if you already received
the schema.
- EXECUTE: Performs the operation with the provided request body
JSON.
Note: You must also provide the required path parameters when executing.
If you need the schema, call with mode='get_request_schema' ONCE, then execute.
|
Page 1 of 15(25 of 374)
Get Building
Last updated on