PagerDuty

· پراستفاده‌ترین #212

Incident response that never waits for a human to notice

ارتباطاتپشتیبانیDeveloperSecurityاتوماسیون

PagerDuty is the operations cloud for incident management — it centralises on-call scheduling, alert routing, escalation policies, and event intelligence so your team responds to outages in seconds, not minutes. Connect it to Actionist and your agents can create incidents the moment a monitor fires, acknowledge alerts to halt escalation chains, resolve issues once a runbook completes, and surface the on-call engineer's identity into any downstream workflow. The result is a closed-loop incident response system that humans supervise but don't have to drive.

میانگین زمان صرفه‌جویی‌شده
10 ساعت
برای هر نفر · در هر ماه
تقریبا 1 روز کاری برگشتی

کار دستی را حذف می‌کند. Agents eliminate the manual handoff loop — checking who is on call, copying alert context into Slack, updating status pages, and writing incident notes — that costs ops and engineering teams 3+ hours of fragmented attention every week.

زمان‌بندی

عامل PagerDuty شما چه چیزهایی را خودکار اجرا می‌کند

یک هفته کارهای زمان‌بندی‌شده که عامل Actionist از طرف شما اجرا می‌کند.

28کارهای زمان‌بندی‌شده
7عامل‌های فعال
24/7همیشه روشن
عامل‌ها
چهارشنبهجمعه
چهارشنبه
پنجشنبه
جمعه
7a
8a
9a
10a
11a
12p
1p
2p
3p
4p
5p
6p
گردش‌کارهای چنداپلیکیشنی

PagerDuty × همه اپلیکیشن‌های دیگر شما

اتوماسیون‌های سرتاسری که چند اپلیکیشن را به هم وصل می‌کنند؛ هرکدام یک خروجی واقعی کسب‌وکار.

6گردش‌کارها
9اپلیکیشن‌های درگیر
حدود 60 ساعتصرفه‌جویی در هفته
6نقش‌های پوشش‌داده‌شده
برای موفقیت مشتری
ویژه4 اپلیکیشن

P1 incident to customer update in 90 seconds

When a customer-impacting Gmail alert arrives flagging a service degradation, your agent reads the matching open PagerDuty incident, confirms its urgency and assigned responder, creates a timestamped incident note with the customer context, posts the on-call engineer's name and ETA to the Slack incident channel, and books a 30-minute incident review on Google Calendar — the customer success team has a full picture before they pick up the phone.

حدود 10 ساعت

زمانی که تیم شما هر هفته و به‌صورت خودکار پس می‌گیرد

جریان کار
تریگر·When a new email arrives in Gmail with a subject matching a customer-reported outage or degradation
نتیجه
Create an incident note with customer email contextPost on-call engineer name and incident status to #incidentsBook 30-minute incident review with CS and on-call
برد اصلی
صرفه‌جویی در هر اجرا
حدود 1 ساعت
اجرا در هفته
~10×
Zero manual coordination between CS and engineering during outages
اجرا توسطCustomer Support Agent
بازگشت سرمایه

صرفه‌جویی

چیزی که تیم شما پس می‌گیرد: کارهای دستی‌ای که حذف می‌شوند و ارزشی که ایجاد می‌شود.

بدون Actionist

کاری که امروز دستی انجام می‌دهید

با Actionist

کاری که عامل شما برایتان اجرا می‌کند

  • Sales
    18 دقیقه در هفته
    Incident impact assessment

    Account executives manually check PagerDuty for active incidents before enterprise calls to avoid promising uptime during an outage.

    عامل Sales
    ۰ دقیقه
    Agent pre-call incident check

    Agent fetches all open incidents 10 minutes before each call and DMs the AE with a one-line status — no manual PagerDuty login required.

  • Marketing
    13 دقیقه در هفته
    Status page copy updates

    Marketing manually rewrites status page text each time an incident severity changes, coordinating with engineering over Slack.

    عامل Marketing
    ۰ دقیقه
    Agent syncs status page copy

    Agent detects priority changes via webhook and updates the status page component copy within 60 seconds, no human in the loop.

  • Customer Support
    18 دقیقه در هفته
    Incident triage for support tickets

    Support agents cross-reference PagerDuty for active incidents every time a customer reports degraded service, burning 3–4 minutes per ticket.

    عامل Customer Support
    ۰ دقیقه
    Agent surfaces active incident links

    Agent fetches the matching open incident and injects its status and ETA into the support reply draft automatically.

  • Human Resources
    7 دقیقه در هفته
    On-call schedule conflict checks

    HR manually emails engineering managers to verify on-call schedules before scheduling all-hands or mandatory training sessions.

    عامل Human Resources
    ۰ دقیقه
    Agent queries on-call schedules

    Agent checks Find User on Call before confirming any session time, flagging schedule conflicts without a single email sent.

  • Finance
    13 دقیقه در هفته
    Outage cost impact logging

    Finance manually calculates revenue impact estimates for P1 incidents by pulling incident duration from PagerDuty and transaction data from billing.

    عامل Finance
    ۰ دقیقه
    Agent calculates and logs impact

    Agent pulls incident duration and maps it to hourly revenue rate automatically, posting the impact figure to the incident note and the finance tracker.

  • Operations
    25 دقیقه در هفته
    Incident handoff documentation

    On-call engineers spend the last 15 minutes of each shift manually writing handoff notes summarising open incidents, recent actions, and next steps.

    عامل Operations
    ۰ دقیقه
    Agent generates handoff summaries

    Agent fetches all open incidents and their notes at rotation time and posts a structured handoff brief to the incoming engineer's Slack DM.

  • Legal
    6 دقیقه در هفته
    SLA breach evidence collection

    Legal manually exports incident logs from PagerDuty and cross-references customer contracts when a breach complaint arrives.

    عامل Legal
    ۰ دقیقه
    Agent compiles SLA audit packages

    Agent fetches all log entries for the incident period and exports a timestamped evidence package to a secure Google Drive folder on demand.

+ صدها اتوماسیون دیگر PagerDuty
میانگین ماهانه
10 ساعت / نفر / ماه
میانگین ماهانه
10 ساعت / نفر / ماه
محاسبه‌گر

محاسبه کنید تیم شما چه چیزی ذخیره می‌کند

اندازه تیم
10 نفر
نرخ ساعتی
20 دلار / ساعت
ساعت ذخیره‌شده / هفته
25
ساعت ذخیره‌شده / سال
1,250
بازگشت سالانه
$25,000

بر اساس الگوی رایج استفاده تیمی از PagerDuty: کارهای قابل مشاهده به‌علاوه چند اتوماسیون دیگر که عامل اجرا می‌کند: حدود2.5 ساعت / نفر / هفته کار اداری خودکار می‌شود.

اتصال

چطور PagerDuty را به Actionist وصل کنید

روش اتصالی را انتخاب کنید که با محیط کاری شما سازگار است.

The fastest path — install PagerDuty's official MCP server in one click and the agent connects via a scoped OAuth handshake, with no tokens to copy or rotate. MCP gives the agent access to incidents, on-call schedules, services, and log entries through PagerDuty's own server implementation.

1
Open the Apps tab

Find PagerDuty in the Apps library and click Connect. MCP is selected by default.

2
Authorise in PagerDuty

A browser window opens to PagerDuty's OAuth authorisation screen. Select the account subdomain you want to connect and confirm the permission scopes — read and write access to incidents, schedules, users, and services.

3
Test the connection

Actionist runs a read-only call to verify the handshake. You're ready.

اکشن‌ها

15 اکشن که عامل شما می‌تواند اجرا کند

عملیات خواندن و نوشتنی که برای عامل Actionist شما در دسترس است.

تریگرها

6 رویداد که عامل شما می‌تواند به آن واکنش نشان دهد

رویدادهایی که عامل شما زیر نظر می‌گیرد و در پاسخ به آن‌ها اکشن اجرا می‌کند.

مهارت‌ها

مهارت‌هایی که با PagerDuty خوب کار می‌کنند

مهارت‌های قابل استفاده مجدد عامل که کنار این اپلیکیشن مفید هستند.

Architecture Designer

Invoke when designing the on-call routing architecture, escalation policy structure, or service dependency map for a PagerDuty integration.

سرورهای MCP

سرورهای MCP سازگار با PagerDuty

Actionist را به سرورهای MCP ساخته‌شده برای این اپلیکیشن یا پیرامون آن وصل کنید.

pagerduty
رسمی

Manage PagerDuty incidents, on-call schedules, escalation policies, and alert notifications via MCP.

pagerduty-mcp
رسمی

PagerDuty's official MCP server for interacting with your PagerDuty account — incidents, services, and schedules.

devops-mcp
رسمی

Unified DevOps MCP server covering Kubernetes, ArgoCD, Prometheus, PagerDuty, and Loki in one integration.

پرسش‌ها

پرسش‌ها درباره PagerDuty + Actionist

How do I connect PagerDuty to Actionist?
The fastest path is MCP: open the Apps tab, find PagerDuty, and click Connect — Actionist installs PagerDuty's official MCP server and walks you through OAuth authorisation. If you prefer a direct API token, go to PagerDuty > Integrations > Developer Tools > API Access Keys, generate a general-access key, and paste it into the API Token field. Either method gives the agent full access to incidents, schedules, users, and log entries.
What permissions does my PagerDuty token need?
A general access API token grants read and write access to all resources the connected account can see — incidents, services, schedules, users, and log entries. If you want to scope it more tightly, create a user-level token for a dedicated service account with the 'Responder' role; this allows incident creation, acknowledgement, and resolution without granting admin-level access to account configuration or billing.
Can I combine PagerDuty with other apps in the same agent workflow?
Yes — PagerDuty is designed to sit at the centre of a multi-app response loop. A common pattern: Datadog fires an alert → agent creates a PagerDuty incident → agent posts to Slack with the on-call user's handle → agent updates the status page → once the runbook completes, agent resolves the incident and seeds the Notion postmortem. Every step is a different app; PagerDuty holds the incident record that ties them all together.
What can the agent do with PagerDuty actions?
The agent can create, read, and update incidents; acknowledge and resolve alerts via the Events API; add notes to incident timelines; fetch on-call user identity for any schedule; retrieve log entries for audit trails; list all services and their escalation policies; and snooze incidents during known maintenance windows. Trigger events from external systems are also supported via Add Trigger Event, letting the agent open PagerDuty alerts from any data source.
How do I avoid trigger loops when the agent updates incidents?
Two safeguards: first, build a condition at the top of any incident-update workflow that checks the incident's current status before acting — if the agent already set it to the target state, skip the write. Second, use PagerDuty's dedup_key field when sending trigger events via the Events API; any subsequent trigger event with the same dedup_key updates the existing alert rather than creating a duplicate, so a fast-firing monitor never opens dozens of incidents.
Which PagerDuty webhook events can trigger agent workflows?
Actionist supports six PagerDuty webhook triggers: New or Updated Incident (any change), Incident Acknowledged, Incident Resolved, Incident Escalated, Incident Priority Updated, and Incident Responder Added. Each fires a distinct webhook payload from PagerDuty's v3 webhook API. You can stack multiple workflows on the same event — for example, both a Slack notification and a postmortem doc creation workflow can fire on Incident Resolved independently.
Does the PagerDuty integration support on-call schedule queries?
Yes — the Find User on Call action resolves the current on-call responder for any PagerDuty schedule or escalation policy. Give the agent a schedule ID and it returns the responder's name, email, and user ID in real time. This is useful for routing Slack DMs, personalising alert messages, building rotation-aware automations, and ensuring handoff summaries always reach the right person without hardcoding names into workflow logic.
Can the agent read PagerDuty incident notes and log entries?
Yes — Get all incident's notes returns every note on an incident in order, and Get a log entry / Get all log entries expose the full event trail including notify, acknowledge, escalate, and resolve events with actor and timestamp. These are the raw materials for automated postmortems, SLA audit exports, and MTTR calculations. The agent can read them without any special scope beyond the base API token.