SUMMARIZATION
Daily Sentry Release-Regression Roll-Up
Once a day, summarizes the error clusters introduced by every release shipped in the last 24 hours and posts a single ranked roll-up so the team reviews all deploy regressions…
How it runs
The automated pipeline, trigger to output.
- TriggerDaily scheduled run
- ActionList releases shipped in the last 24 hoursSentry
- ActionGather issues first-seen in each releaseSentry
- ActionSummarize and rank regressions per releaseOpenAI
- OutputPost the consolidated roll-up to SlackSlack
What it does
Instead of one alert per deploy, this workflow produces a single morning roll-up covering every release shipped in the prior day. It maps each release to the new error clusters it introduced, summarizes them, and ranks the day's deploys by how much new breakage each one caused, giving a clear picture of which change destabilized the app most.
When to use it
Use it when per-deploy pings are too frequent and you'd rather start the day with one consolidated regression review. Ideal for teams shipping many releases daily who want a standup-ready summary rather than a stream of interruptions.
How it works
A scheduled run lists the releases created in the last 24 hours from Sentry. For each release it gathers the issues first-seen there, then merges everything into a day-level view. The model summarizes the new clusters per release, attributes a severity weight from event volume and affected users, and orders the releases worst-first. The combined roll-up, with one section per release and links to the top issues, is posted to Slack as a single threaded message the team can scan in standup.
Set it up
What you configure once, before turning it on.
- 1Connect SentryErrors, performance, releases.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect SlackChannels, DMs, threads, mentions.
- 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.