ENGINEERING
Require a Linear approval when burn rate is borderline before promoting
When a Vercel promotion is requested and the Honeycomb burn rate sits in a warning band, it holds the promotion and opens a Linear issue requiring a named approver to sign off…
How it runs
The automated pipeline, trigger to output.
- TriggerVercel promotion requested webhookVercel
- ActionRead SLO burn rate from HoneycombHoneycomb
- LogicClassify: healthy / warning / critical
- ActionOpen Linear approval issue for warning bandLinear
- OutputNotify owner in Slack with approval linkSlack
What it does
Adds a human gate only when the data is ambiguous. Instead of blocking outright, this workflow looks at the Honeycomb SLO burn rate at promotion time. If it is in a borderline warning band (healthy but trending hot), it pauses the promotion and creates a Linear approval issue assigned to the on-call owner. The promotion resumes only after the issue is marked approved.
When to use it
Use it when a hard auto-block is too blunt but you still want a checkpoint for risky-looking deploys. Good for teams who want a documented, auditable approval trail in Linear for every borderline release.
How it works
- 1A Vercel promotion-requested webhook starts the flow.
- 2The workflow pulls the current burn rate for the service's SLO from Honeycomb.
- 3A branch routes: healthy passes through, critical hard-blocks, and the warning band falls through to approval.
- 4For the warning band it opens a Linear issue with the burn-rate context and assigns the on-call owner.
- 5It posts a Slack message linking the Linear issue and noting the promotion is held pending sign-off.
Set it up
What you configure once, before turning it on.
- 1Connect VercelDeploys, runtime logs, analytics.
- 2Connect HoneycombDistributed traces and queries.
- 3Connect LinearIssues, projects, cycles, triage.
- 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.