SUMMARIZATION
Sentry release-health digest into the deploy's GitLab MR
On each new Sentry release, summarizes new error signatures and crash-rate regressions and posts a plain-English health digest as a comment on the GitLab merge request…
How it runs
The automated pipeline, trigger to output.
- TriggerSentry new release createdSentry
- ActionFetch release issues and crash-free rateSentry
- ActionSummarize new and regressed signaturesOpenAI
- LogicMatch release commit SHA to its GitLab MR
- OutputPost health digest as MR commentGitLab
What it does
When Sentry registers a new release, this workflow pulls the issues and session crash-rate tied to that release, summarizes what is new or regressed versus the prior release, and drops a readable digest comment on the GitLab merge request that produced the deploy.
When to use it
Use it when your team merges to deploy and wants release health surfaced where code review already happens, instead of buried in the Sentry dashboard. It turns a noisy issue stream into a single "is this release healthy?" verdict on the MR.
How it works
- 1Sentry fires a release-created webhook with the version and associated commits.
- 2The flow fetches new and regressed issues plus the crash-free session rate for that release from Sentry.
- 3An OpenAI summarization step groups errors by signature, flags first-seen vs. regressed, and writes a concise health summary with a healthy/degraded verdict.
- 4The release version is matched to its GitLab MR via the commit SHA.
- 5The digest is posted as a comment on that MR so reviewers see it inline.
Set it up
What you configure once, before turning it on.
- 1Connect SentryErrors, performance, releases.
- 2Connect GitLabRepos, MRs, pipelines, registry.
- 3Connect OpenAIModels, embeddings, files.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, 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.
