AI AGENTS
Overdue Remediation Escalator
Watches incident action items in Linear for due-date breaches and escalates each laggard to its owner, then their manager, with a per-item aging report.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily overdue-check schedule fires
- ActionQuery Linear for overdue incident itemsLinear
- LogicBucket items by escalation tier
- ActionDM owners of tier-one laggardsSlack
- ActionEmail managers for tier-two laggardsGmail
- OutputPost aging report to team channelSlack
What it does
Incident remediations slip quietly past their due dates with no one noticing until the next outage. This agent monitors open incident action items in Linear and detects which ones have blown their due date. It escalates on a tiered schedule — first a direct nudge to the owner, then, if still open days later, a notification to their manager — and maintains an aging report so leadership can see how stale the reliability backlog has become.
When to use it
Use it as an always-on safety net for any team that closes incidents but struggles to land the follow-up work on time.
How it works
A daily schedule triggers the agent. It queries Linear for open items labeled `incident` past their due date and computes days overdue for each. A logic step buckets items by escalation tier based on how long they have been overdue. Tier-one laggards get a direct Slack DM to the owner; tier-two laggards trigger an email to the owner's manager via Gmail. Finally the agent posts a consolidated aging report to the team Slack channel.
Set it up
What you configure once, before turning it on.
- 1Connect LinearIssues, projects, cycles, triage.
- 2Connect SlackChannels, DMs, threads, mentions.
- 3Connect GmailRead, draft, send, label.
- 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.
