PagerDuty ACTION
Update Incident
Update an incident's status, title, urgency, priority, escalation policy, or assignments. Use List Incidents or Get Incident to find the incident ID. To acknowledge: set
status to acknowledged. To resolve: set status to resolved. Use List Users to find user IDs for assignments and List Priorities for priority IDs. 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 Incident 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-incident",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
pagerduty: { authProvisionId: "apn_xxxxxxx" },
incidentId: "Incident ID",
status: "Status",
},
})
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-incident",
"configured_props": {
"pagerduty": { "authProvisionId": "apn_xxxxxxx" },
"incidentId": "Incident ID",
"status": "Status"
}
}'// 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-incident",
arguments: {
incidentId: "Incident ID",
status: "Status",
},
})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 |
|---|---|---|
incidentId Incident ID | string | The ID of the incident to update. Use List Incidents to find IDs. Required |
status Status | string | New status for the incident. Options: acknowledged, resolved. Optional |
title Title | string | New title for the incident. Optional |
urgency Urgency | string | New urgency level. Options: high, low. Optional |
priorityId Priority ID | string | New priority. Use List Priorities to discover valid IDs. Optional |
escalationPolicyId Escalation Policy ID | string | Reassign to a different escalation policy. Use List Escalation Policies to find IDs. Optional |
assignments Assignments (User IDs) | string[] | Replace current assignments with these user IDs. Use List Users to find IDs. 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-incident
- Version
- 0.0.2
- App
- PagerDuty
- Authentication
- OAuth
- Read-only
- No
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗