SUMMARIZATION
Severe-Regression Detector with PagerDuty Escalation
On each deploy, summarizes newly introduced Sentry clusters and routes them by severity: high-impact regressions page on-call via PagerDuty, the rest go to a Slack digest.
How it runs
The automated pipeline, trigger to output.
- TriggerVercel deploy webhook with release versionVercel
- ActionFetch Sentry issues first-seen in this releaseSentry
- ActionScore and summarize each cluster's severityOpenAI
- LogicBranch on severity against the page threshold
- ActionPage on-call for high-impact regressionsPagerDuty
- OutputSend the remaining clusters to a Slack digestSlack
What it does
This workflow grades the error clusters a release introduces and reacts differently to each tier. A regression spiking across many users or hitting a critical path gets an immediate PagerDuty page with a summarized incident description. Lower-severity new clusters are batched into a Slack digest so on-call isn't woken for noise. The decision logic, not a human, decides what is worth a page.
When to use it
Use it when some deploy regressions are genuine incidents and others are minor, and you need automatic separation. Best for teams with on-call rotations who want paging reserved for real impact while still tracking the long tail.
How it works
A Vercel deploy webhook provides the release. The flow fetches Sentry issues first-seen in that release and the model scores each cluster on event rate, user count, and whether it hits a flagged critical surface, producing a severity label and a one-line summary. A branch splits the clusters: anything above the page threshold triggers a PagerDuty incident with the summary and Sentry link attached; everything below is collected into a Slack digest so the full set still gets visibility.
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.