AI AGENTS
Pre-flight the next on-call shift and swap offline responders before handoff
Thirty minutes before each on-call shift change, this workflow checks the incoming responder's Slack presence and calendar.
How it runs
The automated pipeline, trigger to output.
- TriggerSchedule: 30 min before shift change
- ActionCheck incoming responder presence + calendarSlack
- LogicBranch: incoming responder unavailable?
- ActionPick in-hours covering responderGoogle Calendar
- ActionApply PagerDuty schedule overridePagerDuty
- OutputDM both engineers with swap detailsSlack
What it does
Runs a readiness check just before every shift boundary so the person about to go on-call is actually online and not on vacation. When the incoming responder is unreachable, it finds a covering teammate and applies a PagerDuty schedule override so the rotation is correct before any page ever lands.
When to use it
Use it when handoffs routinely go to someone who forgot they were on-call or is traveling. It moves the failure detection from incident-time to pre-shift, eliminating the scramble during a live page.
How it works
- 1A schedule trigger fires 30 minutes before the next PagerDuty shift starts.
- 2The workflow reads the incoming responder's Slack presence and their Google Calendar for the shift window.
- 3A logic branch checks whether they are present and free.
- 4If unavailable, it selects a covering responder whose timezone puts them in working hours.
- 5It writes a PagerDuty schedule override for the shift to the covering responder.
- 6It DMs both engineers on Slack confirming the swap and the reason.
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.