AI AGENTS
Daily audit of on-call coverage gaps against responder calendars
Each morning this workflow compares the upcoming PagerDuty schedule against every responder's calendar, flags shifts where the assignee will be offline or out of office.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily morning schedule
- ActionPull upcoming PagerDuty schedulePagerDuty
- ActionRead each assignee's calendarGoogle Calendar
- LogicFlag shifts with offline assignees
- ActionFile Linear ticket for gapsLinear
- OutputPost coverage-gap digest to SlackSlack
What it does
Proactively audits the next several days of on-call schedule against responder calendars to surface coverage gaps before they cause a missed page. It produces a ranked digest of risky shifts and opens tracking work so a human can arrange swaps in advance.
When to use it
Use it as a daily preventive check for teams that plan rotations weeks out but where PTO, travel, and meetings change after the schedule is set. It turns silent coverage holes into a visible, actionable list every morning.
How it works
- 1A daily schedule trigger fires each morning.
- 2The workflow pulls the next few days of PagerDuty on-call assignments.
- 3For each shift it reads the assigned responder's Google Calendar for conflicts and out-of-office.
- 4A logic branch flags shifts where the responder will be unavailable during their on-call window.
- 5It opens a Linear ticket listing each gap and a suggested in-hours backup.
- 6It posts a prioritized coverage-gap digest to the team Slack channel.
Set it up
What you configure once, before turning it on.
- 1Connect PagerDutyIncidents, on-call, escalations.
- 2Connect Google CalendarEvents, attendees, availability.
- 3Connect LinearIssues, projects, cycles, triage.
- 4Connect SlackChannels, DMs, threads, mentions.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, 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.