ENGINEERING
Auto-disable a risky feature flag via Cloudflare when budget burns
When a Honeycomb burn alert ties budget loss to a specific feature, it flips that feature's flag off through a Cloudflare KV killswitch and logs the action to a Postgres audit…
How it runs
The automated pipeline, trigger to output.
- TriggerHoneycomb burn alert with feature tagHoneycomb
- LogicConfirm kill threshold and resolve flag key
- ActionSet flag off in Cloudflare KV killswitchCloudflare
- ActionInsert audit row into PostgresPostgres
- OutputAlert team in Slack with feature + impactSlack
What it does
This workflow connects an SLO burn alert to an automatic feature killswitch. When Honeycomb attributes a service's budget burn to a recently shipped feature, the workflow writes the flag's value to off in a Cloudflare KV namespace that your edge code reads, immediately disabling the feature for all users without a redeploy. Every action is recorded for audit.
When to use it
Use this when feature rollouts are gated by edge-evaluated flags in Cloudflare and you want bad features pulled automatically the instant they start eating budget, rather than waiting for a human to react.
How it works
- 1A Honeycomb burn-alert webhook fires with the offending feature tag in the payload.
- 2A logic step confirms the burn exceeds the kill threshold and resolves the matching flag key.
- 3The workflow writes the flag to off in the Cloudflare KV namespace, taking effect at the edge.
- 4It inserts an audit row into Postgres recording who, what, and the burn rate at kill time.
- 5It posts a Slack message naming the disabled feature and the budget impact.
Set it up
What you configure once, before turning it on.
- 1Connect HoneycombDistributed traces and queries.
- 2Connect CloudflareWorkers, Pages, R2, KV — the edge stack.
- 3Connect PostgresAny Postgres URL — query, write, migrate.
- 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
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…
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.
Scan for deprecated endpoints and email consumers a weekly sunset countdown
On a weekly schedule, scans the OpenAPI spec for endpoints marked deprecated with a sunset date, and emails each consuming team a countdown of how many days remain before removal.
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.
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.
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.