SUMMARIZATION
Auto-File a Linear Rollback Issue on Crash-Free Regression
When a Sentry release-finalized webhook arrives, evaluates the crash-free trend over the last three deploys and, if the new release regressed sharply, opens a Linear issue…
How it runs
The automated pipeline, trigger to output.
- TriggerSentry release finalized webhookSentry
- ActionRetrieve crash-free rates across last three releasesSentry
- LogicClassify regression severity; stop unless severe
- ActionCompose narrative plus rollback recommendationOpenAI
- OutputOpen a high-priority Linear rollback issueLinear
What it does
The moment Sentry finalizes a new release, this workflow checks whether crash-free rates dropped versus the previous two releases. If the regression is severe, it writes up what happened and opens a triaged Linear issue recommending a rollback, so the decision lands in your backlog instead of someone's memory.
When to use it
Use it when a crash-free drop should become actionable engineering work automatically. Good for teams that treat stability regressions as ship-blockers and want a paper trail with an owner and severity.
How it works
- 1A Sentry release-finalized webhook triggers the run with the new release version.
- 2The flow retrieves crash-free session rates for the last three releases.
- 3A logic step classifies the regression as none, minor, or severe based on the three-point delta; non-severe outcomes stop here.
- 4An LLM step composes a regression narrative plus a rollback recommendation.
- 5A Linear issue is created with the narrative, the comparison numbers, and a high-priority label.
Set it up
What you configure once, before turning it on.
- 1Connect SentryErrors, performance, releases.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect LinearIssues, projects, cycles, triage.
- 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 Summarization workflows
On-submit Loom standup roll-up archived to Confluence
When a standup video is submitted via webhook, transcribes it, generates a per-person written summary, and appends it to a running team standup page in Confluence.
Front Escalation Handoff Doc in Notion
When a Front escalation closes, drafts a structured handoff document in Notion capturing the resolution, customer commitments, and open follow-ups, then alerts the AE in Slack.
Front Escalation War-Room Brief to Slack
On a Front escalation, posts a concise threat-assessment brief to a Slack channel only when the AI judges the situation high-severity.
VIP Front Escalation Instant Exec Page-Out
Detects escalations from VIP accounts in Front, generates a one-paragraph executive recap, and pages the named account exec via Slack and Salesforce task within minutes.
Release health note per Vercel deploy
When a Vercel deploy goes live, summarizes the Sentry errors observed in the release window into a plain-English health note that separates brand-new error classes…
Rollback recommendation when a deploy spikes errors
When a Sentry alert fires for an error spike, attributes it to the most recent deploy, summarizes whether the spike is dominated by new error classes introduced by that release.
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.