ENGINEERING
AI-summarize a release regression and request Slack approval to promote
When a Sentry release shows a crash-free regression, an LLM summarizes the top new issues driving it and posts an interactive Slack approval request that links straight…
How it runs
The automated pipeline, trigger to output.
- TriggerSentry release-health regression eventSentry
- ActionFetch top unresolved issues for the releaseSentry
- ActionSummarize root causes and user impactOpenAI
- LogicConfirm regression exceeds alert threshold
- OutputSend Slack approval request with Vercel linkSlack
What it does
Turns a raw crash-free drop into a human-readable decision. When Sentry flags that a new release is less healthy than baseline, this workflow asks an LLM to summarize the specific new error issues responsible, then sends an approval-style Slack message to your release channel. The on-call lead can read what broke and decide whether to promote or hold the Vercel deployment.
When to use it
Use it when crash-free percentages alone don't tell engineers what actually regressed. The AI summary saves the on-call from digging through Sentry, and the Slack message keeps the promote/hold decision in one place with the Vercel link attached.
How it works
- 1Sentry emits a release-health event showing a crash-free regression.
- 2The flow pulls the new release's top unresolved issues from Sentry.
- 3An OpenAI step writes a tight summary of likely root causes and user impact.
- 4A logic step confirms the regression clears your alert threshold.
- 5It posts a Slack approval message with the summary plus a deep link to the pending Vercel deployment for the human to act on.
Set it up
What you configure once, before turning it on.
- 1Connect SentryErrors, performance, releases.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect SlackChannels, DMs, threads, mentions.
- 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 Engineering workflows
Agent reviews model-license fit and suggests compliant swaps on the PR
When a PR adds a Hugging Face model, an agent reads the model card and license, judges fit against your commercial-use policy.
Block PRs that add incompatible Hugging Face model licenses
When a pull request adds or bumps a Hugging Face model dependency, it fetches the model card license, checks it against your org's allowed-license policy.
Quarterly Logging Hygiene Audit Agent
An agent-driven quarterly sweep that surveys all Axiom datasets, builds a logging-hygiene scorecard per service.
Post-Merge Log Volume Recheck After Downsampling PR
After a log-level PR merges, waits a day then re-queries Axiom to confirm the targeted stream's volume actually dropped.
Axiom Ingest Cost Spike to Linear Triage Ticket
When Axiom ingest volume spikes beyond its baseline, identifies which service caused it and files a Linear ticket with the offending log stream, sample lines, and a downsampling…
File a Linear license-review ticket for risky model adds
When a PR introduces a Hugging Face model with a non-permissive or unknown license, it opens a Linear issue assigned to the legal-review team with the model, license.
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.