SUMMARIZATION
Sentry deploy regression triage brief to Slack
On each new Vercel production deploy, compares Sentry error rates against the previous release and posts a plain-English triage brief to Slack only when a regression crosses your…
How it runs
The automated pipeline, trigger to output.
- TriggerVercel production deploy succeedsVercel
- ActionFetch release-health stats for new + previous releaseSentry
- LogicCompute error-rate delta; stop if below threshold
- ActionPull top new and spiking issues for the releaseSentry
- ActionSummarize deltas + culprits into a triage briefOpenAI
- OutputPost brief to incident Slack channelSlack
What it does
After every production deploy, it pulls Sentry release-health stats for the new release and the one it replaced, computes the crash-free-session and error-rate deltas, and — when the regression is material — writes a concise triage brief naming the most likely culprit issues and posts it to your incident Slack channel.
When to use it
Use it when your team ships to production several times a day and nobody has time to babysit the Sentry release dashboard after each deploy. It catches the silent regressions that don't page anyone but quietly degrade reliability.
How it works
- 1A Vercel deployment-succeeded webhook fires with the new release version.
- 2The flow fetches release-health metrics for the new and previous releases from Sentry.
- 3A logic step computes error-rate and crash-free deltas and stops quietly if the regression is below threshold.
- 4Sentry returns the top new and spiking issues for the release.
- 5An OpenAI step distills the numbers and issues into a short, ranked triage brief.
- 6The brief posts to Slack with links back to Sentry and the deploy.
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 SlackChannels, DMs, threads, mentions.
- 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
Daily Front Escalation Digest with Salesforce Rollup
Each morning, sweeps the prior day's escalated Front conversations, summarizes each, enriches with Salesforce account value, and emails account execs a single prioritized digest.
File a Linear ticket for regressed errors after deploy
Detects Sentry issues that regressed in the latest deploy's release window, summarizes what broke and when it was previously fixed.
Daily release-health rollup to Confluence
Each morning, compares the last 24 hours of Sentry activity against the deploys that shipped in that window and publishes a dated release-health page to Confluence summarizing…
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.
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.
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.