AI AGENTS
Escalate unacknowledged pages to a follow-the-sun responder
If a PagerDuty page goes unacknowledged past a threshold, this workflow picks the responder in the timezone where it's currently business hours, reassigns the incident.
How it runs
The automated pipeline, trigger to output.
- TriggerPagerDuty ack timeout exceededPagerDuty
- LogicSelect region currently in business hours
- ActionReassign incident to in-hours responderPagerDuty
- ActionOpen Linear tracking ticketLinear
- OutputPost escalation summary to SlackSlack
What it does
Watches for pages that have not been acknowledged within your SLA window and rebalances them using a follow-the-sun rule: it routes the incident to whichever team region is currently awake and working, then records the late escalation as a Linear ticket for follow-up.
When to use it
Use it for distributed teams spanning multiple regions where a missed ack at 3am local should immediately bounce to the region that is mid-workday, rather than waking a tired engineer or escalating to a manager.
How it works
- 1A PagerDuty webhook fires when an incident crosses its unacknowledged-timeout threshold.
- 2The workflow evaluates the current UTC time against each region's working-hours window.
- 3A logic branch selects the region that is in business hours right now.
- 4It looks up that region's active responder and reassigns the PagerDuty incident.
- 5It creates a Linear issue capturing the missed ack, original assignee, and new owner.
- 6It posts the escalation summary to the team's Slack channel.
Set it up
What you configure once, before turning it on.
- 1Connect PagerDutyIncidents, on-call, escalations.
- 2Connect LinearIssues, projects, cycles, triage.
- 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.