AI AGENTS
Sentry Error-Spike Rollback Guard
On a Sentry error spike, an agent follows the deployment rollback runbook from a GitHub repo, confirms the bad release.
How it runs
The automated pipeline, trigger to output.
- TriggerSentry error-spike alertSentry
- ActionRead rollback runbook from GitHubGitHub
- LogicCorrelate spike with recent release
- ActionRequest rollback approval in TeamsMicrosoft Teams
- LogicGate on human approval
- OutputTrigger Vercel rollback to last healthy deployVercel
What it does
Handles the specific, high-stakes case of rolling back a bad deploy. When Sentry detects an error spike, the agent walks the rollback runbook, identifies the offending release, and asks for explicit approval in Microsoft Teams before reverting production to the last known-good deployment.
When to use it
Use it when a regression in a new release is your most common Sev-1 and rolling back is the standard fix, but you never want an automated system to flip production traffic without a named human signing off.
How it works
- 1A Sentry alert fires when error rate crosses the spike threshold.
- 2The agent reads the rollback runbook stored as Markdown in your GitHub repo.
- 3It correlates the spike start time with recent deploys to name the suspect release.
- 4Logic confirms the spike is release-correlated, not infrastructure-wide.
- 5It posts the suspect release and rollback target to Teams and waits for approval.
- 6On approval it triggers the Vercel rollback and posts confirmation with the restored deployment ID.
Set it up
What you configure once, before turning it on.
- 1Connect SentryErrors, performance, releases.
- 2Connect GitHubRepos, issues, pull requests, actions.
- 3Connect Microsoft TeamsChannels, chats, files.
- 4Connect VercelDeploys, runtime logs, analytics.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, 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.