SUMMARIZATION
Per-deploy Sentry regression brief to Slack
On every Vercel production deploy, pulls the new and spiking Sentry error groups, clusters them by root-cause signature.
How it runs
The automated pipeline, trigger to output.
- TriggerVercel deployment succeeded webhookVercel
- ActionFetch new and spiking Sentry issues for releaseSentry
- LogicCluster issues by root-cause signature
- LogicDrop clusters below noise threshold
- ActionSummarize each cluster into a regression briefOpenAI
- OutputPost release-health brief to SlackSlack
What it does
Turns the raw firehose of Sentry issues that appear after a deploy into one readable verdict. It fetches every error group that is new or newly spiking since the release, groups them by shared root-cause signature (same stack frame, exception type, or culprit), and writes a short brief: what broke, how many users are hit, and whether the release looks safe.
When to use it
When you ship to production several times a day and nobody has time to babysit the Sentry issues feed. Use it to get an automatic health read on each deploy without staring at dashboards.
How it works
- 1A Vercel deployment-succeeded webhook fires with the new release version.
- 2Query Sentry for issues first seen or spiking in that release window.
- 3Cluster the issues by root-cause signature so duplicate symptoms collapse into one cause.
- 4Filter out groups below a noise threshold (few events, no user impact).
- 5An LLM writes a plain-English brief per cluster with severity and likely cause.
- 6Post the brief to the team's deploys Slack channel, tagging the release.
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.