AI AGENTS
Postmortem Doc Action-Item Reconciler
Parses the action-item tables in published Confluence postmortems and reconciles them against Linear, creating tickets for any commitment that was written down but never tracked.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly reconciliation schedule fires
- ActionList and parse postmortem action tables in ConfluenceConfluence
- ActionMatch each row against existing Linear issuesLinear
- LogicKeep only documented commitments with no ticket
- ActionCreate Linear issues for untracked commitmentsLinear
- OutputPost reconciliation summary to SlackSlack
What it does
Postmortem docs are full of action items that live in a Confluence table and die there — never converted into a tracked ticket. This agent reads every postmortem published in a Confluence space, extracts the action-item rows, and reconciles them against Linear. Any commitment with an owner and a due date that has no matching Linear issue gets a ticket created so it can't vanish into a wiki page nobody reopens.
When to use it
Run it weekly, or right after a postmortem review, when you want to guarantee that every documented commitment is actually on a board someone is accountable for.
How it works
The scheduled trigger fires weekly. The agent lists postmortem pages in the configured Confluence space and parses each action-item table into structured rows (action, owner, due date). It searches Linear for an existing issue matching each row. A logic step keeps only unmatched rows. For those, it creates Linear issues assigned to the named owner with the due date and a backlink to the source doc, then posts a reconciliation summary to Slack listing every newly tracked commitment.
Set it up
What you configure once, before turning it on.
- 1Connect ConfluenceSpaces, pages, blueprints.
- 2Connect LinearIssues, projects, cycles, triage.
- 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
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.