AI AGENTS
On-Incident-Close Action Item Extractor
Triggers when a PagerDuty incident is resolved, reads the timeline and chat thread, drafts concrete remediation action items, and files them in Linear linked back to the incident.
How it runs
The automated pipeline, trigger to output.
- TriggerPagerDuty incident resolvedPagerDuty
- ActionPull incident timeline and Slack discussionSlack
- LogicDrop vague or duplicate action suggestions
- ActionFile concrete action items as linked Linear issuesLinear
- OutputPost recap to the incident Slack threadSlack
What it does
The moment an incident resolves is when context is freshest and action items are most accurate — yet teams wait days to write them up, by which point the details have decayed. This agent fires the instant a PagerDuty incident is resolved, reads the incident timeline and the resolution discussion, and drafts specific, owner-assignable remediation action items. It files each as a Linear issue tagged to the incident so the postmortem starts with real follow-ups already on the board.
When to use it
Use it for any team that wants postmortem action items captured automatically at resolution time, not reconstructed from memory a week later.
How it works
A PagerDuty incident-resolved event triggers the agent. It pulls the incident timeline and notes from PagerDuty and the linked Slack discussion thread. The agent drafts discrete action items with proposed owners and severity. A logic step drops vague or duplicate suggestions, keeping only concrete, actionable items. Each survivor becomes a Linear issue linked to the incident, and a recap is posted to the incident's Slack thread for review.
Set it up
What you configure once, before turning it on.
- 1Connect PagerDutyIncidents, on-call, escalations.
- 2Connect SlackChannels, DMs, threads, mentions.
- 3Connect LinearIssues, projects, cycles, triage.
- 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.