pagerduty-agent
Manage PagerDuty incidents, on-call schedules, services, and maintenance windows directly from your agent.
Install via CLI (Recommended)
clawhub install openclaw/skills/skills/clawdbotworker/pagerduty-agentPagerDuty Agent
⚠️ This is an unofficial community skill and is not affiliated with or endorsed by PagerDuty, Inc.
Trigger, acknowledge, and resolve PagerDuty incidents, check who's on-call, manage maintenance windows, and inspect services — all without leaving your agent workflow.
Setup
- Generate a PagerDuty API key: PagerDuty → Integrations → API Access Keys → Create New API Key
- Export required environment variables:
export PAGERDUTY_API_KEY="your-v2-api-key"
export PAGERDUTY_FROM_EMAIL="[email protected]" # required for write operations
PAGERDUTY_FROM_EMAILmust be the email of a valid PagerDuty user in your account. It is required by PagerDuty's REST API for any POST/PUT request.
Usage
All commands are invoked by piping a { command, params } JSON object to
node pagerduty.js. The skill returns structured JSON on stdout.
echo '{"command":"list_incidents","params":{"status":"triggered"}}' | node pagerduty.js
Commands
Incidents
trigger_incident
Create a new incident on a service.
Params
| Field | Type | Required | Description |
|---|---|---|---|
service_id | string | ✓ | PagerDuty service ID (e.g. "P1ABCDE") |
title | string | ✓ | Incident title / summary |
severity | string | "critical", "error", "warning", "info" — maps to urgency | |
body | string | Detailed description / runbook context |
Example
{
"command": "trigger_incident",
"params": {
"service_id": "P1ABCDE",
"title": "Database replication lag > 60s",
"severity": "critical",
"body": "Replica db-02 is 90s behind primary. Check pg_stat_replication."
}
}
Response
{
"id": "Q2W3E4R",
"incident_number": 1042,
"title": "Database replication lag > 60s",
"status": "triggered",
"urgency": "high",
"html_url": "https://your-subdomain.pagerduty.com/incidents/Q2W3E4R",
"created_at": "2026-03-04T12:00:00Z",
"service": { "id": "P1ABCDE", "name": "Production Database" }
}
acknowledge_incident
Acknowledge an incident to signal it is being worked on.
Params
| Field | Type | Required | Description |
|---|---|---|---|
incident_id | string | ✓ | PagerDuty incident ID |
Example
{ "command": "acknowledge_incident", "params": { "incident_id": "Q2W3E4R" } }
Response
{
"id": "Q2W3E4R",
"incident_number": 1042,
"title": "Database replication lag > 60s",
"status": "acknowledged",
"acknowledged_at": "2026-03-04T12:03:00Z"
}
resolve_incident
Mark an incident as resolved.
Params
| Field | Type | Required | Description |
|---|---|---|---|
incident_id | string | ✓ | PagerDuty incident ID |
Example
{ "command": "resolve_incident", "params": { "incident_id": "Q2W3E4R" } }
Response
Metadata
Not sure this is the right skill?
Describe what you want to build — we'll match you to the best skill from 16,000+ options.
Find the right skillPaste this into your clawhub.json to enable this plugin.
{
"plugins": {
"official-clawdbotworker-pagerduty-agent": {
"enabled": true,
"auto_update": true
}
}
}