SUMMARIZATION
Per-Deploy Sentry Regression Digest to Slack
On each Vercel deploy, finds the error issues newly introduced by that release and posts a plain-English digest of the new clusters to Slack so the team knows what broke before…
How it runs
The automated pipeline, trigger to output.
- TriggerVercel deployment-succeeded webhook with release versionVercel
- ActionQuery Sentry for issues first-seen in this releaseSentry
- LogicFilter out known issues and low-event noise
- ActionSummarize and rank the new error clustersOpenAI
- OutputPost the deploy regression digest to SlackSlack
What it does
Every time a release ships, this workflow asks Sentry which error issues first appeared in that release and turns the raw issue list into a readable digest: what the new error clusters are, how often they are firing, and which parts of the app they touch. The summary lands in Slack within minutes of the deploy, so the team sees regressions tied directly to the change that caused them.
When to use it
Use it when you deploy often and your Sentry inbox is too noisy to scan after every release. Ideal for teams who want a deploy-scoped "what's new and broken" readout instead of trawling the full issue stream.
How it works
A Vercel deployment-succeeded webhook fires with the release version. The flow queries Sentry for issues whose first-seen release matches that deploy and filters out anything already known or below an event-count floor. The surviving clusters are passed to the model, which groups them by symptom, ranks by frequency and impact, and writes a tight summary with links back to each Sentry issue. The digest posts to a Slack channel; if no new regressions are found, it posts a short all-clear instead.
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
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…
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.
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.
Escalate blockers from Loom standups to Slack
Transcribes each new Loom standup video, uses AI to detect blockers and dependencies.
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.