PagerDuty ACTION
Create Service
Create a new PagerDuty service. A service represents a system or application that generates incidents. Use List Escalation Policies to find a valid escalation policy ID (required). Set
autoResolveTimeout to 0 to disable auto-resolve. Set acknowledgementTimeout to 0 to disable re-triggering after acknowledgment. See the documentation- Action
- Writes data
- OAuth
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's PagerDuty account once, then configure and run Create Service 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-create-service",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
pagerduty: { authProvisionId: "apn_xxxxxxx" },
name: "Service Name",
escalationPolicyId: "Escalation Policy ID",
},
})
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-create-service",
"configured_props": {
"pagerduty": { "authProvisionId": "apn_xxxxxxx" },
"name": "Service Name",
"escalationPolicyId": "Escalation Policy ID"
}
}'// 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-create-service",
arguments: {
name: "Service Name",
escalationPolicyId: "Escalation Policy ID",
},
})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 |
|---|---|---|
name Service Name | string | The name of the service. Required |
escalationPolicyId Escalation Policy ID | string | The escalation policy for this service (required). Use List Escalation Policies to find IDs. Required |
description Description | string | A description of the service. Optional |
autoResolveTimeout Auto-Resolve Timeout (seconds) | integer | Seconds after which triggered incidents auto-resolve. Set to 0 to disable. Default: 14400 (4 hours). Optional |
acknowledgementTimeout Acknowledgement Timeout (seconds) | integer | Seconds after which acknowledged incidents re-trigger. Set to 0 to disable. Default: 1800 (30 min). 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-create-service
- Version
- 0.0.2
- App
- PagerDuty
- Authentication
- OAuth
- Read-only
- No
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗