PagerDuty ACTION
Update Escalation Policy
Update an escalation policy's name, description, loop count, or escalation rules. By default, performs a read-then-merge: fetches the current policy and merges your changes before writing, so you only need to specify the fields you want to change. Set
fullReplacement: true to replace all rules wholesale — use with caution as this is destructive. Use List Escalation Policies to find the policy ID. Each escalation rule targets one or more users or schedules: provide targets as an array of objects with id and type (user_reference or schedule_reference). See the documentation- Action
- Writes data
- OAuth
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's PagerDuty account once, then configure and run Update Escalation Policy from your backend or agent.
import { PipedreamClient } from "@pipedream/sdk"
const pd = new PipedreamClient({
projectId: process.env.PIPEDREAM_PROJECT_ID!,
clientId: process.env.PIPEDREAM_CLIENT_ID!,
clientSecret: process.env.PIPEDREAM_CLIENT_SECRET!,
projectEnvironment: "production",
})
const result = await pd.actions.run({
id: "pagerduty-update-escalation-policy",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
pagerduty: { authProvisionId: "apn_xxxxxxx" },
escalationPolicyId: "Escalation Policy ID",
name: "Name",
},
})
console.log(result)curl -X POST https://api.pipedream.com/v1/connect/{project_id}/actions/run \
-H "Content-Type: application/json" \
-H "X-PD-Environment: production" \
-H "Authorization: Bearer {access_token}" \
-d '{
"external_user_id": "{external_user_id}",
"id": "pagerduty-update-escalation-policy",
"configured_props": {
"pagerduty": { "authProvisionId": "apn_xxxxxxx" },
"escalationPolicyId": "Escalation Policy ID",
"name": "Name"
}
}'// accessToken: mint a short-lived token with the Connect SDK — see the MCP guide
const transport = new StreamableHTTPClientTransport(
new URL("https://remote.mcp.pipedream.net/v3"),
{
requestInit: {
headers: {
Authorization: `Bearer ${accessToken}`,
"x-pd-project-id": "{project_id}",
"x-pd-environment": "production",
"x-pd-external-user-id": "{external_user_id}", // any stable ID for this user in your system
"x-pd-app-slug": "pagerduty",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// listTools() hands your model this tool's input schema, so it can
// fill the arguments itself:
const result = await mcp.callTool({
name: "pagerduty-update-escalation-policy",
arguments: {
escalationPolicyId: "Escalation Policy ID",
name: "Name",
},
})SCHEMA
Inputs
Pipedream supplies the connected account. Your application provides the operation-specific values below. Dynamic inputs are resolved against that user's account.
| Property | Type | Description |
|---|---|---|
escalationPolicyId Escalation Policy ID | string | The ID of the escalation policy to update. Use List Escalation Policies to find IDs. Required |
name Name | string | New name for the escalation policy. Optional |
description Description | string | New description for the escalation policy. Optional |
numLoops Number of Loops | integer | How many times to loop through the escalation rules before the incident is escalated no further. Set to 0 for infinite. Optional |
escalationRules Escalation Rules (JSON) | string | JSON array of escalation rules to set. Each rule: {"escalation_delay_in_minutes": 30, "targets": [{"id": "USER_ID", "type": "user_reference"}]}. Use List Users and List Schedules to find target IDs. When provided without fullReplacement: true, these rules replace only the rules of the current policy. Optional |
fullReplacement Full Replacement | boolean | When true, skips the read-then-merge and sends only the fields you provide. All unspecified rules are removed. Use with caution. Optional |
REFERENCE
Tool details
Behavior hints are published with the component in the Pipedream registry and surface as MCP tool annotations, so an agent can reason about a tool before it calls it.
- Registry key
- pagerduty-update-escalation-policy
- Version
- 0.0.2
- App
- PagerDuty
- Authentication
- OAuth
- Read-only
- No
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗