Skip to content
Recued
Menu
← Back to packs

Incident Response - PagerDuty

by recued-core v1 app_pack

API capability pack for bounded PagerDuty REST API v2 operations against https://api.pagerduty.com only. Reads the current user, users, services, escalation policies, schedules, on-calls, incidents, and incident notes, and supports approval-gated incident acknowledgment/resolution plus note creation with an explicit From header. Bundles a scheduled on-call handoff digest, an AI-assisted incident brief, and an approval-gated incident update workflow. Enroll a PagerDuty OAuth or API-token connection named pagerduty with the narrowest scopes needed for the installed operations. The pack intentionally excludes incident creation, bulk incident mutation, service/schedule/escalation-policy/user mutation, maintenance windows, rulesets, webhooks, analytics, audit records, account/admin APIs, and arbitrary API passthrough.

What this pack installs

Trust & control

What installing this whole pack would let it do. Recued grants these permissions at install — review them there before approving.

Where it runs

Device + server Runs on your device (browser) or your server.

What it's allowed to do

Write Web APIs pagerduty external change
Read: user.current · No approvalRead: user.search · No approvalRead: service.search · No approvalRead: service.read · No approvalRead: escalation_policy.search · No approvalRead: escalation_policy.read · No approvalRead: schedule.search · No approvalRead: schedule.read · No approvalRead: on_call.search · No approvalRead: incident.search · No approvalRead: incident.read · No approvalRead: incident.note.search · No approvalWrite: incident.status.update · Asks approvalWrite: incident.note.create · Asks approval

Data it touches

SurfacesWeb APIs

About

Tags

pack:pagerdutypagerdutyincidentson-callschedulesservicesoperationssreapiv3composition