SUMMARIZATION
Critical post-deploy regression auto-escalation
On a deploy, checks Sentry for newly introduced high-impact error groups, and if a release crashed real users it clusters the cause, pages on-call via PagerDuty.
How it runs
The automated pipeline, trigger to output.
- TriggerVercel deployment succeeded webhookVercel
- ActionFetch release-introduced error groups with impactSentry
- LogicCluster by root cause and score impact
- LogicBranch: exit unless a cluster is critical
- ActionWrite incident briefOpenAI
- ActionTrigger PagerDuty incidentPagerDuty
- OutputPost brief to incident Slack channelSlack
What it does
Acts as an automatic release gate that only speaks up when a deploy actually breaks things for users. It scans Sentry for error groups introduced by the new release, scores user impact, and escalates only when a cluster crosses the critical line, so on-call is paged for genuine regressions rather than background noise.
When to use it
When you want hands-off escalation for bad deploys without subscribing on-call to every minor Sentry blip. Use it as a safety net on high-traffic production services.
How it works
- 1A Vercel deployment-succeeded webhook fires with the release version.
- 2Fetch error groups first seen in that release from Sentry, with user counts.
- 3Cluster them by root-cause signature and compute impact per cluster.
- 4Branch: if no cluster is critical, exit quietly; otherwise continue.
- 5An LLM writes a tight incident brief naming the cause and blast radius.
- 6Trigger a PagerDuty incident for the on-call rotation.
- 7Post the same brief to the incident Slack channel.
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 PagerDutyIncidents, on-call, escalations.
- 5Connect SlackChannels, DMs, threads, mentions.
- 6Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 7Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 8Test, 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.