ENGINEERING
Block Vercel promotion when a new release's crash-free rate dips
Watches Sentry release-health for a freshly deployed Vercel release and, if the crash-free sessions rate falls below your threshold during the bake window, halts the production…
How it runs
The automated pipeline, trigger to output.
- TriggerVercel deployment-ready webhookVercel
- ActionQuery Sentry crash-free sessions rate for the releaseSentry
- LogicCompare rate to threshold with minimum session sample
- ActionHalt or roll back the Vercel promotion if unhealthyVercel
- OutputPost version, rate, and action to on-call Slack channelSlack
What it does
Gates a Vercel production promotion on real release-health signal. When a new release finishes its bake period, this checks Sentry's crash-free sessions rate and either lets the promotion stand or pulls it back before it reaches all users.
When to use it
Run this when you use Vercel skew protection or staged promotion and want a hard quality gate instead of eyeballing dashboards. Ideal for teams shipping multiple times a day who can't manually babysit every release.
How it works
- 1A Vercel deployment-ready webhook fires with the new release version and deployment ID.
- 2The flow waits out the configured bake window, then queries Sentry release-health for that version's crash-free sessions rate and session count.
- 3A branch compares the rate against your threshold (and requires a minimum session sample so noise doesn't trip it).
- 4If healthy, the promotion proceeds untouched. If the rate dips, the flow calls the Vercel API to halt or roll back the promotion.
- 5A Slack message to on-call summarizes the version, the measured rate, and the action taken.
Set it up
What you configure once, before turning it on.
- 1Connect VercelDeploys, runtime logs, analytics.
- 2Connect SentryErrors, performance, releases.
- 3Connect SlackChannels, DMs, threads, mentions.
- 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 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.