PagerDuty
Manage PagerDuty incidents, services, on-call schedules and escalation policies.
About
PagerDuty ships in the w6w first-party pack. It declares 14 actions, 2 health checks, and the host runs its code in a sandbox that never sees the credential.
- App id
io.w6w.pagerduty- Version
- 0.2.1
- Author
- w6w
- Licence
- MIT
- Categories
- Monitoring & Observability · DevOps & Infrastructure
Overview
PagerDuty routes and escalates incidents to on-call responders, and this app manages that response from a workflow: create, list, and update incidents; acknowledge, resolve, or reassign one; add a note documenting what happened; and read the services, on-call schedules and escalation policies behind the alerting.
Acknowledge, resolve and reassign are given their own dedicated actions rather than leaving a workflow to construct a generic incident update, since those are the moves a responder actually reaches for. Every action that changes an incident is attributed to a named user, matching how PagerDuty records who took each step in an incident’s history.
This app is aimed at the incident-response loop itself — creating, updating and closing out incidents, and reading who is on call and how escalation is configured — rather than at configuring services, schedules or escalation policies, which stay in PagerDuty’s own interface.
Build with PagerDuty
Three routes to the same 14 actions. The Workflow tab is generated from PagerDuty's own manifest and carries its real ids, so it is copy-pasteable; the Code and CLI examples are the same call for any action on any app, so every app-specific value in them is a blank you fill in.
List escalation policies
escalation-policy-list List escalation policies, optionally filtered by name, user or team.
List incidents
incident-list List incidents, optionally filtered by status, urgency, service or assignee.
Update an incident
incident-update Update an incident's title, priority, urgency, or escalation policy/level.
List on-call users
oncall-list List who is on-call, optionally filtered by schedule, escalation policy or user.
Get an on-call schedule
schedule-get Get a single on-call schedule by ID, including its rendered entries.
A workflow step names the app and the action, and the editor fills in the
connection when you pick one. This is the Step shape from the
workflow spec, carrying PagerDuty's real ids.
{
"manifestVersion": "2",
"name": "pagerduty-example",
"steps": [
{
"id": "incident-acknowledge",
"uses": {
"app": "io.w6w.pagerduty",
"action": "incident-acknowledge",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"incidentId": "<incidentId>",
"from": "<from>"
}
}
]
}Here are some of the things you can do
-
Acknowledge an incident
performincident-acknowledge -
List escalation policies
readescalation-policy-list -
Create an incident
performincident-create -
Get an incident
readincident-get -
List incidents
readincident-list
+9 more actions available
Every app-specific value here is a blank you have to fill in. An
app action is reached through the connection that authenticates it, so the
address is a connection id, not the app id — and connections belong to your account,
so a public page cannot know yours. Create one for PagerDuty, then fill in
the three blanks: conn_YOUR_CONNECTION_ID, the action key, and the
parameters that action declares. The call itself is real — the shape is transcribed
from the studio's own snippet builder, which prints the same kind of blanks — but
nothing in it is specific to PagerDuty. The Workflow tab is where this app's
real ids are.
npm install @w6w/sdkyarn add @w6w/sdkpnpm add @w6w/sdkdeno add npm:@w6w/sdkimport { W6wClient, isActionRun } from "@w6w/sdk";
// Reads W6W_BASE_URL and W6W_TOKEN from the environment when omitted.
const client = new W6wClient();
const envelope = await client.run({
urn: "conn_YOUR_CONNECTION_ID",
action: "incident-create",
payload: {
title: "<value>",
serviceId: "<value>",
from: "<value>",
// additionalOptions: "<value>",
// additionalFields: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value);npm install -g @w6w/cliw6w run conn_YOUR_CONNECTION_ID --action incident-create --payload '{"title":"<value>","serviceId":"<value>","from":"<value>"}'Give an AI agent PagerDuty — without giving it PagerDuty's credentials. One MCP endpoint exposes every app, function and workflow the caller is entitled to, as tools it can discover and run. Access is granted per team while we onboard.
One tool call{
"name": "w6w_invoke",
"arguments": {
"ref": "app:io.w6w.pagerduty#incident-acknowledge",
"input": {
"incidentId": "<incidentId>",
"from": "<from>"
}
}
}
Every tool names its target with a single ref. The
app: form above doesn't name a connection at all — the
host resolves which of the caller's PagerDuty connections to sign
with, and refuses rather than guesses when the answer is ambiguous.
What the agent gets
Credentials it can't read
The token is attached host-side, at the moment of the call. It is never a tool argument, never in the model's context, and never in a transcript — so a prompt injection has nothing to exfiltrate.
A tool surface scoped to the caller
Tools are derived per end user from what that person has actually connected and is entitled to — not one shared bot identity carrying the union of everyone's access.
A durable workflow in one call
Multi-step work runs on the workflow engine and returns a run handle the agent can poll — retries, branching and state survive the conversation that started them.
Health-aware discovery
PagerDuty's declared health checks are on the surface too, so an agent can tell "the vendor is down" from "your credential expired" before it burns a retry on either.
The MCP surface is part of the hosted platform. PagerDuty itself is MIT, and the runtime that executes it is source-available (FSL).
Health checks
PagerDuty declares its own checks, so its health is a property of the app rather than something the host guesses at.
PagerDuty platform status
No machine-readable status API, Atom, or RSS feed is published for status.pagerduty.com.
API rate-limit headroom
Requests remaining on this credential, read off the `ratelimit-*` headers.