Skip to content
ClickRuntime

Automate PagerDuty

Follow PagerDuty incidents and on-call shifts from your inbox or team chat. Incidents that trigger, get acknowledged or resolve, a weekly breakdown by service with time to resolve, a heads-up the day before your shift and incidents still open after a day are all sent automatically. Write out what you need for your AI assistant, approve what it plans to do, and it goes on running.

Add to ChatGPTAdd to Claude
Works inChatGPTClaudeClaude CodeCursorCodexVS CodeGemini CLIZedopencodeAny MCP client

Try asking

Create a ClickRuntime automation: every 5 minutes, check PagerDuty and email me whenever an incident is triggered, acknowledged or resolved, with the service, title, urgency and who is assigned.

Paste it into your assistant. It tells you what it will send or change before it runs live.

Ideas

What you can automate in PagerDuty

Hear when incidents change state, review each week's incidents and resolution times by service, never be surprised by an on-call shift, and stop incidents from lingering unresolved. These are ready-made starting points. Anything else you can describe works too.
Every 5 minutes

Get an email when a PagerDuty incident changes

When an incident is triggered, acknowledged or resolved, you get the update with its service and urgency.

See how it works
Weekly

Get a weekly incident report by service

Every Monday you see how many incidents each service had last week and how long they took to resolve on average.

See how it works
Daily

Get a reminder the day before you're on call

The afternoon before a shift, you get a note saying when your on-call starts and ends.

See how it works
Daily

Get a morning list of incidents open over a day

Every morning you see the incidents still triggered or acknowledged after 24 hours, oldest first.

See how it works Your own logic

Any other automation you can describe in words

Your own rules, schedule and AI steps with PagerDuty, plus any other app. Describe it and your assistant builds it.

See how to build your own

Build your own

Build any PagerDuty automation you can describe

The ideas above are ready-made starting points, not a fixed list. Describe what PagerDuty should do in your own words, with your conditions, other apps or an AI step, and your assistant writes it, tests it and runs it on ClickRuntime.

  • Your own rules

    Conditions, thresholds, filters and exceptions, written the way you'd explain them to a colleague.

  • Any number of apps

    One automation can read from one app and update several others. Over 248 apps are ready, and anything with an API works too.

  • AI where it helps

    Summaries, classification, extraction and drafts use ClickRuntime's built-in AI, with no extra key.

  • On a schedule or on each event

    Runs as often as every 5 minutes, or the moment an app sends an event, and keeps track of what it already handled.

For example, ask your assistant

Every Monday, pull last week's PagerDuty incidents and send me counts per service, mean time to resolve, and the noisiest alert.

When a PagerDuty incident is triggered, post it to our #incidents Slack channel with the service and urgency.

When a high-urgency PagerDuty incident is resolved, create a postmortem Google Doc from a template, add the timeline, and post the link in Slack.

Beyond chat

Have PagerDuty work when you're not in the chat

Connecting PagerDuty to ChatGPT or Claude lets you ask about it while you chat. ClickRuntime handles the part that should happen on its own: checks on a schedule and actions on each new event, set up from the same chat and running after you close it.

Setup

Connect PagerDuty

PagerDuty connects with a REST API key you create. An admin can make a general access key, read-only if you prefer, or any user can create a personal API token that carries their own permissions.

PagerDuty

Developer / Incident management

  1. As an Admin or Account Owner, open Integrations, then Developer Tools, then API Access Keys, and choose Create New API Key.
  2. Enter a description, tick Read-only if the automations only need to read, then create the key.
  3. Copy the key straight away, since it is shown once. Alternatively, create a personal token under My Profile, User Settings, Create API User Token.
  4. In the ClickRuntime dashboard, save the key as a secret on Connections & secrets. If your account is in the EU region, use the EU API.

Good to know

PagerDuty limits that affect automations

  • An API key is shown only once. If it is lost, create a new one and update the secret.
  • Creating a general access API key requires the Admin or Account Owner role.
  • A personal API user token can do exactly what that user can, no more and no less.
  • Some write actions must include the email of a PagerDuty user, so read-only keys are the simpler choice for reporting.
  • Sending new events into PagerDuty uses the separate Events API with a per-service integration key, not the REST API key.

FAQ

Questions about automating PagerDuty

What can ClickRuntime see in PagerDuty?
What the key allows. With a read-only key it can list incidents, their status and service, and on-call schedules. It cannot acknowledge or resolve incidents with a read-only key.
How fast are incident updates sent?
The incident alert checks every 5 minutes and compares statuses with the last run. You can also point a PagerDuty v3 webhook at it for incident triggered and resolved events, so updates arrive right away.
Can it remind me before my on-call shift?
Yes. Each afternoon it looks up tomorrow's on-call entries for your user and emails you only if you are on call.
How does the weekly report work out time to resolve?
It pulls the last 7 days of incidents, groups them by service and averages the time from trigger to resolution for each one.
Do PagerDuty automations need AI?
These do not; they count and compare incident data. For a written incident summary, the AI that ships with every ClickRuntime plan does the job, and no separate AI key is required.
Is this a PagerDuty connector for ChatGPT or Claude?
Not for chatting with PagerDuty data. A chat connector lets your assistant read and change PagerDuty while you're in the conversation. ClickRuntime is for the work that should happen without you: you set up an automation from the chat once, and it keeps running on a schedule or on each PagerDuty event.

Related pages

Keep exploring

Tell your assistant what PagerDuty should do

Free plan. No credit card.

Add to ChatGPTAdd to Claude