AI AGENTS
CEO agent triages a page and rebalances on-call across the org
An agent reads a triggered PagerDuty incident, reasons over responder calendars, recent workload, and presence, then decides the best available responder, reassigns the page.
How it runs
The automated pipeline, trigger to output.
- TriggerPagerDuty incident triggeredPagerDuty
- ActionGather candidate calendars + timezonesGoogle Calendar
- LogicAgent ranks responders by availability + load
- ActionReassign incident to chosen responderPagerDuty
- OutputExplain decision in SlackSlack
What it does
Instead of a fixed rule, an agent makes the rebalancing decision. It pulls the incident context, each candidate's calendar and timezone, and how many pages they have already taken today, then chooses the responder who is both available and least overloaded, reassigns the page, and narrates why.
When to use it
Use it when simple next-in-rotation logic produces unfair or poor outcomes, for example when one engineer keeps absorbing pages while others are idle, or when the right choice depends on incident severity plus human availability. Best for teams that want judgment, not just a lookup.
How it works
- 1A PagerDuty incident webhook starts the agent run.
- 2The agent gathers candidate responders and reads each one's Google Calendar and timezone.
- 3It reasons over availability, current page load, and incident severity to rank candidates.
- 4It reassigns the PagerDuty incident to its chosen responder.
- 5It posts a Slack message explaining the choice and the runners-up so humans can override.
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
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.
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.
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.
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.
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.
Weekly On-Call Doc-Gap Digest
Each week the agent reviews every Sentry issue resolved in the last 7 days, ranks the ones whose runbook coverage is missing or thin.
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.