SUMMARIZATION
Block MR merge on a Sentry crash-rate regression
After a deploy, checks the new release's crash-free rate against the previous one and, if it regressed past a threshold, posts a blocking summary on the GitLab MR and pages…
How it runs
The automated pipeline, trigger to output.
- TriggerSentry new release createdSentry
- ActionPull crash-free rate vs. previous releaseSentry
- LogicRegression exceeds threshold?
- ActionSummarize culprit signaturesOpenAI
- ActionPage on-callPagerDuty
- OutputPost blocking or healthy note on MRGitLab
What it does
This workflow gates merges on release health. When a Sentry release lands, it compares the new crash-free session rate to the prior release. If the rate dropped beyond your threshold, it writes a summary of the offending error signatures, posts it as a blocking comment on the GitLab MR, and pages on-call. If health is fine, it posts a short green confirmation instead.
When to use it
Use it when a single bad deploy can cause real user pain and you want an automatic stop sign rather than relying on someone watching dashboards. It is the decision-logic counterpart to a plain digest.
How it works
- 1Sentry fires the release-created webhook.
- 2The flow pulls crash-free rate and top issues for the new and previous release.
- 3A branch checks whether the regression exceeds the configured threshold.
- 4On regression, an OpenAI step summarizes the likely-culprit signatures into a blocking note, posted to the GitLab MR, and PagerDuty pages on-call.
- 5Otherwise it posts a brief "release healthy" comment on the MR.
Set it up
What you configure once, before turning it on.
- 1Connect SentryErrors, performance, releases.
- 2Connect GitLabRepos, MRs, pipelines, registry.
- 3Connect OpenAIModels, embeddings, files.
- 4Connect PagerDutyIncidents, on-call, escalations.
- 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.
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…
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.
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.