SUMMARIZATION
Sentry Canary Burn Check with GitLab Rollback Brief
On a schedule during a canary rollout, compares the canary release's error-budget burn against the stable baseline and, if it regresses, posts a rollback recommendation…
How it runs
The automated pipeline, trigger to output.
- TriggerRollout-window schedule tick
- ActionFetch canary vs baseline release healthSentry
- LogicCompare burn against rollback tolerance
- ActionDraft rollback recommendation briefOpenAI
- ActionPost brief to GitLab pipelineGitLab
- OutputSend rollback alert to SlackSlack
What it does
Watches a canary deploy and decides whether it is safe to continue. On a tight interval during rollout, it compares the canary release's crash-free rate and error-budget burn against the stable baseline. If the canary regresses past tolerance, it writes a rollback recommendation to the GitLab pipeline and pings Slack so a human can pull the trigger fast.
When to use it
Use it during progressive or canary rollouts where you need an automated stability second opinion within minutes, not at end-of-day. The branch keeps quiet while the canary is healthy.
How it works
- 1A schedule fires repeatedly during the active rollout window.
- 2Sentry release-health is fetched for the canary release and the stable baseline.
- 3A logic gate compares burn against tolerance; healthy canaries exit silently.
- 4On regression, an LLM drafts a rollback-recommendation brief.
- 5The brief is posted to the GitLab pipeline and a Slack alert is sent.
Set it up
What you configure once, before turning it on.
- 1Connect SentryErrors, performance, releases.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect GitLabRepos, MRs, pipelines, registry.
- 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.