ENGINEERING
Dual-signal promotion gate with Sentry and Honeycomb SLOs
Gates a Vercel promotion on two independent signals at once — Sentry crash-free sessions and a Honeycomb latency/error SLO — promoting only when both clear.
How it runs
The automated pipeline, trigger to output.
- TriggerVercel deployment ready webhookVercel
- ActionQuery Sentry crash-free session rateSentry
- ActionQuery Honeycomb SLO burn + p95 latencyHoneycomb
- LogicBoth signals within budget?
- ActionPromote or rollback on VercelVercel
- OutputSlack summary tagging deciding signalSlack
What it does
Requires a release to satisfy two unrelated health checks before it reaches production: client-side stability from Sentry and server-side performance from a Honeycomb SLO burn query. The promotion proceeds only on a double pass; any single failure triggers rollback and records which signal vetoed it.
When to use it
Use it when crash-free rate alone misses regressions — for example a release that does not crash but doubles p95 latency or error budget burn. Best for services where backend SLOs and frontend stability are both release-gating concerns.
How it works
- 1A Vercel deployment-ready webhook supplies the release version.
- 2The flow queries Sentry for the release's crash-free session rate over the warm-up window.
- 3In parallel it queries Honeycomb for the release's SLO burn rate and p95 latency.
- 4A branch evaluates both results: pass only if crash-free clears its bar and the Honeycomb SLO is within budget.
- 5On a double pass it promotes the deployment on Vercel; otherwise it re-aliases the previous build.
- 6It posts a Slack summary tagging the deciding signal so engineers know whether to look at the client or the server.
Set it up
What you configure once, before turning it on.
- 1Connect VercelDeploys, runtime logs, analytics.
- 2Connect SentryErrors, performance, releases.
- 3Connect HoneycombDistributed traces and queries.
- 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 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.