DEVOPS
Cloudflare Worker canary rollout gated by Axiom error rate
Promotes a new Cloudflare Worker version through staged traffic percentages, querying Axiom for the canary's error rate at each step and rolling back automatically if errors…
How it runs
The automated pipeline, trigger to output.
- TriggerDeploy webhook with new + stable version IDsHTTP webhook
- ActionShift traffic split to next canary stageCloudflare
- ActionQuery Axiom for canary vs. stable error rateAxiom
- LogicCompare error-rate delta to regression threshold
- ActionRevert split to 100% stable if breachedCloudflare
- OutputPost promotion or rollback to DiscordDiscord
What it does
Runs a progressive-delivery canary for a Cloudflare Worker. After you deploy a new Worker version, this gradually shifts traffic to it (5% -> 25% -> 50% -> 100%), and between each step it asks Axiom how the canary version is behaving. If the new version's error rate exceeds the old version's by your threshold, traffic is reverted to the last good version and the team is paged.
When to use it
Use it whenever you ship Worker changes that touch request handling, routing, or upstream calls and you cannot afford a bad version taking 100% of traffic. It replaces eyeballing a dashboard after deploy with an automated gate.
How it works
- 1A deploy webhook fires with the new Worker version ID and the previous (stable) version ID.
- 2Cloudflare updates the version split to the next stage percentage.
- 3The flow waits for the bake window, then queries Axiom for 5xx-rate of the canary version vs. the stable version over that window.
- 4A logic step compares the delta against your max-regression threshold.
- 5If healthy, it advances to the next stage; if the delta is breached, Cloudflare reverts the split to 100% stable.
- 6A Discord message reports promotion or rollback with the measured error rates.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect CloudflareWorkers, Pages, R2, KV — the edge stack.
- 3Connect AxiomLog streams, queries, dashboards.
- 4Connect DiscordCommunity channels + voice + bots.
- 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 DevOps workflows
Slack-approved pause for idle Hugging Face Spaces
On a daily scan it finds idle paid Spaces and posts an interactive Slack approval; on approve it pauses the Space and logs the decision to a GitHub issue audit trail.
Block costly Hugging Face Space hardware upgrades in PR review
When a pull request changes a Space's hardware config, it estimates the new monthly cost and posts a GitHub PR comment that flags upgrades crossing a budget ceiling.
Hugging Face Spaces idle-runtime sweep with auto-pause
On a schedule, scans all Hugging Face Spaces for ones running idle past a threshold, pauses them to stop billing, and posts a Slack summary with the estimated monthly savings.
Open a Zoom war-room from a Datadog multi-alert storm
When a Datadog monitor crosses a critical threshold, this workflow dedupes against active incidents, and only for a genuinely new outage it creates a Zoom bridge.
Auto-spin a Zoom war-room when PagerDuty hits SEV-1
When a PagerDuty incident escalates to a critical severity, this workflow creates a dedicated Zoom meeting and posts the bridge link to the incident's Slack channel so responders…
Spin up a war-room on demand from a Slack slash command
When an engineer runs a Slack command, this workflow creates a Zoom bridge, opens a tracking Sentry-linked incident, files a Linear issue for follow-up.
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.