Aident logoAident logo centerAident Loadout
Use CasesPricingDocs
ENStart Now
AppsPagerDuty ToolsPagerduty Execute Response Play By Id
PagerDuty Tools

Pagerduty Execute Response Play By Id

Executes a predefined Response Play for a specific incident in PagerDuty. This endpoint allows you to trigger a sequence of automated actions designed to manage and respond to the given incident. It's useful for standardizing and streamlining your incident response process, ensu…

Write actionRisk level 2 of 5API key connection
Use Pagerduty Execute Response Play By Id

Pricing and limits

Aident logo

Product

Aident LoadoutAident Playbook EditorOpen-CUAK

About

AppsSkillsUse CasesDocsBlogPricingDownloadsPrivacy PolicyTerms of Service

Alternatives

vs Composiovs Zapier
llms.txtGet an AI summary of Aident LoadoutSummarize with ChatGPTSummarize with ClaudeSummarize with GeminiSummarize with Perplexity

© Aident Labs, 2024-2026

Pricing
Free
Unified payment
Not currently supported

Inputs

  • Fromstring
    Required
    REQUIRED: Email address of a valid user associated with the PagerDuty account. This user must have permissions to execute response plays. The email is used to attribute the action and ensure proper authorization. You can use the GET /users/me endpoint to get the current user's e…
  • incident__idstring
    Required
    The unique identifier of the incident on which to run the Response Play. This is the incident that will have the Response Play's actions applied to it. You can obtain incident IDs from the GET /incidents endpoint or from incident creation responses. Example: "Q3X7Z8D90ABCDE". Pa…
  • incident__typestring
    The object type for the incident reference. Must be "incident_reference" to properly identify the incident object type in the API request.
  • response_play_idstring
    Required
    The unique identifier of the Response Play to execute. Response Plays are predefined sets of actions that can be applied to incidents. You can obtain response play IDs using the GET /response_plays endpoint with filter_for_manual_run=true. Example: "PLAY123". Note: Response Play…

Observable output

  • data
    Required
    Data from the action execution
  • errorstring
    Error if any occurred during the execution of the action
  • successfulboolean
    Required
    Whether or not the action execution was successful or not

Skills that use this Action

Related use cases

No verified related use cases are linked yet.

Official source

Provider source

Skills that use this Action

No published Skills explicitly reference this Action yet.