SUMMARIZATION
Auto-file a Linear issue for Sentry release regressions
When a Vercel deploy raises the Sentry error rate past your gate, it summarizes the regression and opens (or updates) a prioritized Linear issue assigned to the deploy author…
How it runs
The automated pipeline, trigger to output.
- TriggerVercel production deploy succeedsVercel
- ActionFetch release-health deltas from SentrySentry
- LogicGate on regression size; map severity to priority
- ActionPull regressing issues and stack tracesSentry
- ActionDraft issue title and regression briefOpenAI
- OutputCreate or update assigned Linear issueLinear
What it does
It watches production deploys, detects when a release regresses error rate or crash-free sessions in Sentry, and turns that into actionable work: a clearly written Linear issue with a summary, the offending stack traces, and a priority set from the severity of the delta. If an issue for the same release already exists, it updates it instead of duplicating.
When to use it
Use it when regressions need to become tracked, owned work rather than a Slack message that scrolls away. Good for teams that run triage out of Linear.
How it works
- 1A Vercel deployment-succeeded webhook provides the release and the author.
- 2Sentry returns release-health deltas versus the prior release.
- 3A logic step gates on the regression size and maps severity to a Linear priority.
- 4Sentry supplies the top regressing issues and their stack traces.
- 5An OpenAI step writes the issue title and body as a tight regression brief.
- 6The flow searches Linear for an existing issue for this release, then creates or updates it and assigns the deploy author.
Set it up
What you configure once, before turning it on.
- 1Connect VercelDeploys, runtime logs, analytics.
- 2Connect SentryErrors, performance, releases.
- 3Connect OpenAIModels, embeddings, files.
- 4Connect LinearIssues, projects, cycles, triage.
- 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 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.