AI AGENTS
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.
How it runs
The automated pipeline, trigger to output.
- TriggerSentry issue resolvedSentry
- LogicContinue only if issue is customer-facing
- ActionRead resolution; redact internal detailsSentry
- ActionAgent drafts public troubleshooting entry
- ActionOpen PR to ReadMe docsReadMe
- OutputNotify support channel in SlackSlack
What it does
Some resolved incidents map to errors your customers actually see. This agent detects when a resolved Sentry issue is tagged customer-facing, then drafts a public-safe troubleshooting article — symptom, cause in plain language, and the workaround or fix — and opens a PR to your ReadMe docs. It deliberately omits stack traces, internal hostnames, and engineer names.
When to use it
Use it when support tickets repeat known errors that you've already fixed internally but never documented for users. Turns each resolution into self-serve deflection content.
How it works
- 1Sentry triggers on a resolved issue.
- 2The agent checks tags and the issue's user-impact data; it stops unless the issue is customer-facing.
- 3It reads the resolution to understand symptom and fix, then rewrites it as a user-facing troubleshooting entry with all internal detail redacted.
- 4It opens a PR against the ReadMe documentation project.
- 5It notifies the support channel in Slack so the team can link the new article in open tickets.
Set it up
What you configure once, before turning it on.
- 1Connect SentryErrors, performance, releases.
- 2Connect ReadMeAPI docs, changelog, auth.
- 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.
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.
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.
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.