SUMMARIZATION
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…
How it runs
The automated pipeline, trigger to output.
- TriggerVercel deployment succeeded webhookVercel
- ActionFetch Sentry issues in the release windowSentry
- LogicClassify each issue: new vs regressed vs carried-over
- ActionSummarize into a plain-English health noteOpenAI
- OutputPost the health note to the release channelSlack
What it does
After every production deploy, this workflow pulls the Sentry errors tied to the new release and writes a short, readable health note. It explicitly separates three buckets: brand-new error classes that never appeared before, regressions of issues that were marked resolved, and pre-existing noise that carried over. The result is a Slack message any on-call engineer can read in fifteen seconds.
When to use it
Use it if your team deploys often and nobody actually reads the raw Sentry issue feed after a release. It replaces the "is this deploy okay?" Slack question with an automatic answer scoped to exactly the release window.
How it works
A Vercel deployment-succeeded webhook fires with the release SHA. The flow queries Sentry for issues whose first-seen or regression timestamp falls inside the release window and tags each issue as new, regressed, or carried-over. An OpenAI step turns that classified list into a plain-English narrative with counts and the top offenders named. The note is delivered to a Slack release channel with a link back to each Sentry issue.
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
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.
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.
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.