ENGINEERING
Crash-free session gate before Vercel production promotion
When a new Sentry release is created, polls its crash-free session rate until enough sessions accumulate.
How it runs
The automated pipeline, trigger to output.
- TriggerVercel deployment ready webhookVercel
- ActionPoll Sentry crash-free rate + session countSentry
- LogicWait until minimum session sample reached
- LogicCrash-free rate clears threshold?
- ActionPromote or re-alias previous deployment on VercelVercel
- OutputPost gate verdict with metrics to SlackSlack
What it does
Holds a freshly deployed Vercel build in a staged state and only promotes it to the production alias once Sentry confirms the release is healthy. If the crash-free session rate fails to clear your bar after a defined number of sessions, it cancels the promotion and re-aliases the previous good deployment.
When to use it
Use it when every production push should earn its place by proving stability on real traffic, not by passing CI alone. Ideal for teams that already ship to a staging alias and want an objective, session-weighted gate instead of a human eyeballing dashboards.
How it works
- 1A Vercel deployment-ready webhook fires with the release version and deployment ID.
- 2The flow waits and repeatedly queries Sentry for that release's crash-free session rate and total session count.
- 3A branch checks whether the sample size has reached the minimum (e.g. 500 sessions).
- 4Once enough sessions exist, it compares the rate against the threshold (e.g. 99.5%).
- 5If healthy, it promotes the deployment to the production alias on Vercel.
- 6If unhealthy, it re-aliases the prior deployment and posts the verdict with numbers to Slack.
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.