SUMMARIZATION
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.
How it runs
The automated pipeline, trigger to output.
- TriggerSentry error-spike alert webhookSentry
- ActionIdentify the most recent deployVercel
- ActionFetch issues driving the spike and tag originSentry
- LogicCompute share of spike from the new release
- ActionWrite a go/no-go rollback recommendationOpenAI
- OutputPost recommendation to the incident channelSlack
What it does
This workflow turns a raw error-spike alert into a rollback decision. When Sentry reports a spike, it finds the deploy that shipped just before it, pulls the issues driving the spike, and determines how much of the volume comes from error classes that release introduced versus pre-existing noise. An LLM weighs that and writes a clear recommendation: roll back, or hold and investigate, with reasoning.
When to use it
Use it during high-traffic launch windows or for teams without a dedicated SRE on every shift. It compresses the panicked "is it the deploy?" investigation into one Slack message with a defensible recommendation and the exact deploy to revert.
How it works
A Sentry metric-alert webhook fires on the spike. The flow identifies the latest deploy and fetches the issues contributing to the spike, separating new-from-this-release from carried-over. A logic step computes the share of spike volume attributable to the new release. An OpenAI step summarizes the situation and emits a go/no-go rollback call. The recommendation, with the deploy link and contributing issues, is posted to the incident Slack channel.
Set it up
What you configure once, before turning it on.
- 1Connect SentryErrors, performance, releases.
- 2Connect VercelDeploys, runtime logs, analytics.
- 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.