AI AGENTS
Re-route PagerDuty pages when the primary responder is offline
When a PagerDuty incident triggers, this workflow checks the primary on-call responder's calendar and presence.
How it runs
The automated pipeline, trigger to output.
- TriggerPagerDuty incident triggeredPagerDuty
- ActionRead primary responder's calendar availabilityGoogle Calendar
- LogicBranch: responder offline or busy?
- ActionFind next available in-hours responderPagerDuty
- ActionReassign incident to new responderPagerDuty
- OutputPost handoff notice to incident channelSlack
What it does
Catches a fresh PagerDuty page, verifies whether the primary on-call engineer is actually reachable right now, and silently rebalances the page to the next available responder when they are not. No more incidents sitting unacknowledged because the assignee is asleep or out of office.
When to use it
Use it for global rotations where the schedule says someone is on-call but their calendar (PTO, focus block, travel) tells a different story. Ideal for teams that page across timezones and cannot afford a 15-minute ack delay before the schedule auto-escalates.
How it works
- 1A PagerDuty incident webhook fires and identifies the current primary responder.
- 2The workflow reads that responder's Google Calendar for an active out-of-office or busy block.
- 3A logic branch decides: if they are free, leave the page as-is and exit; if blocked, continue.
- 4It queries PagerDuty for the next on-call responder whose local time falls in working hours.
- 5It reassigns the incident in PagerDuty to that responder.
- 6It posts a Slack message to the incident channel naming the new owner and why the handoff happened.
Set it up
What you configure once, before turning it on.
- 1Connect PagerDutyIncidents, on-call, escalations.
- 2Connect Google CalendarEvents, attendees, availability.
- 3Connect SlackChannels, DMs, threads, mentions.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More AI Agents workflows
Stale Doc-PR Chaser for Runbook Gaps
On a daily schedule the agent finds runbook doc PRs that were opened from resolved incidents but never reviewed, summarizes what each one fixes.
On-Call Runbook Gap Closer: Resolved Sentry Issues to Doc PRs
An agent reads each newly resolved Sentry issue, compares the actual fix against your existing runbook, and opens a GitHub PR adding the missing remediation steps.
Datadog Bill Spike Attribution Agent
When a daily Datadog cost check detects a spend jump, an agent attributes the increase to the specific services and metric types driving it and posts a ranked breakdown to Slack.
Sentry-to-Confluence Runbook Updater
When a Sentry issue is resolved, the agent finds the matching Confluence runbook page and proposes an inline update with the verified fix.
Custom Metrics Cardinality Spike Pager
A webhook from a Datadog monitor fires when custom-metric cardinality jumps; an agent pinpoints the offending metric and tag, estimates the added cost.
Resolved Incident to Public Troubleshooting Doc
For customer-facing errors resolved in Sentry, the agent drafts a sanitized troubleshooting entry and opens a PR to your ReadMe documentation.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.