AI AGENTS
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.
How it runs
The automated pipeline, trigger to output.
- TriggerSentry issue resolvedSentry
- ActionPull issue, resolving commit, and engineer notesSentry
- ActionSearch Confluence for the matching runbook pageConfluence
- LogicBranch: create new page vs edit existing section
- ActionAgent writes the remediation update
- OutputSave edit and comment for on-call lead approvalConfluence
What it does
For teams whose runbooks live in Confluence rather than Git, this agent watches for resolved Sentry issues, locates the relevant runbook page, and appends or revises the remediation section in place. Instead of merging silently, it adds a Confluence comment summarizing what changed and requests approval from the on-call lead.
When to use it
Reach for this when your operational docs are in Confluence and you want the page to reflect how incidents were genuinely resolved — without forcing engineers to context-switch into a wiki editor after a long on-call shift.
How it works
- 1Sentry triggers on an issue resolution.
- 2The agent retrieves the issue, the resolving commit message, and engineer notes.
- 3It searches Confluence for the runbook page covering the affected service or error class.
- 4If no page exists, it drafts a new child page under the service's runbook space; if one exists, it edits the relevant section.
- 5It saves the change and leaves a Confluence comment explaining the edit and tagging the on-call lead for sign-off.
Set it up
What you configure once, before turning it on.
- 1Connect SentryErrors, performance, releases.
- 2Connect ConfluenceSpaces, pages, blueprints.
- 3Connect GitHubRepos, issues, pull requests, actions.
- 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.
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.
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.