ENGINEERING
Block Vercel promotion when crash-free rate regresses vs baseline
On a new Sentry release deploy, compares the crash-free session rate against the previous stable release and, if it drops below your threshold, posts a blocking comment…
How it runs
The automated pipeline, trigger to output.
- TriggerSentry release created for new deploySentry
- ActionFetch crash-free rate for new + baseline releaseSentry
- LogicCompare delta against allowed drop threshold
- ActionPost approval comment on Vercel deploymentVercel
- OutputPost blocking comment if regression detectedVercel
What it does
Gates production promotion on release health. When Sentry reports a fresh release, this workflow pulls the new release's crash-free session rate, compares it to the last stable release as a baseline, and decides whether the build is safe to promote. A regression beyond your tolerance leaves a clear blocking comment on the Vercel deployment so no one promotes a degraded build by accident.
When to use it
Use it when your team promotes Vercel deployments manually and you want an automated quality bar tied to real user crash data, not just CI green checks. Ideal for high-traffic web apps where a small crash-free dip means thousands of broken sessions.
How it works
- 1Sentry emits a release-created event for the new deploy.
- 2The flow fetches crash-free session rates for the new release and the prior stable baseline from Sentry.
- 3A logic step computes the delta and checks it against your allowed drop (e.g. 0.5%).
- 4If healthy, it posts an approval comment on the Vercel deployment.
- 5If regressed, it posts a blocking comment naming the baseline, the new rate, and the delta so a human stops the promotion.
Set it up
What you configure once, before turning it on.
- 1Connect SentryErrors, performance, releases.
- 2Connect VercelDeploys, runtime logs, analytics.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Engineering workflows
Gate breaking API PRs behind downstream consumer acknowledgement
When a PR introduces a breaking contract change, comments the impact summary back on the PR, applies a blocking label.
Publish a versioned API changelog to Confluence on each release tag
On a new semver release tag, gathers the contract changes since the last release and writes a clean.
Agent reviews model-license fit and suggests compliant swaps on the PR
When a PR adds a Hugging Face model, an agent reads the model card and license, judges fit against your commercial-use policy.
Upgrade Impact Router to Module Code Owners
Maps a dependency-bump PR's affected modules to their CODEOWNERS, then DMs each owner on Slack with only the changelog slice that touches code they own.
Re-Voice IVR Prompts on Phone-Tree Config Merge
When a phone-tree config change merges in GitHub, regenerates the ElevenLabs audio for any prompt whose script changed in the diff and opens a follow-up PR adding the new audio…
Upstream Release to Notion Upgrade Brief
When a watched package publishes a new release, fetches the release notes, maps them to the internal modules that depend on it.
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.