DEVOPS
Start a Worker canary on merge to main
On a push to the main branch, deploys the built Worker as a new uploaded version and starts it at a small canary percentage.
How it runs
The automated pipeline, trigger to output.
- TriggerGitHub push to mainGitHub
- LogicVerify Worker path changed; read SHA
- ActionUpload version and start canary splitCloudflare
- ActionOpen Linear rollout tracking issueLinear
- OutputAnnounce canary live in DiscordDiscord
What it does
Turns a merge into the start of a controlled canary instead of a full deploy. When code lands on main, it tells Cloudflare to upload the new Worker version and route only a small slice of traffic to it, then files a Linear issue that records the version ID, the starting percentage, and a checklist for promotion.
When to use it
Use it as the front door of your Worker delivery pipeline — the step that makes "merged" mean "canarying at 5%" rather than "live for everyone." Pair it with the error-rate or latency gate templates to handle promotion.
How it works
- 1A GitHub push-to-main event fires after CI passes.
- 2A logic step verifies the push touched the Worker source and extracts the commit SHA.
- 3Cloudflare uploads the new version and sets the traffic split to the configured canary start percentage.
- 4A Linear issue is created with the version ID, SHA, percentage, and a promotion checklist.
- 5A Discord message announces the canary is live and links the Linear issue.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect CloudflareWorkers, Pages, R2, KV — the edge stack.
- 3Connect LinearIssues, projects, cycles, triage.
- 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
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.
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…
Page on-call when a Hugging Face Space build is stuck or errored
Polls Hugging Face Space runtime status on a schedule and opens a PagerDuty incident when a Space sits in a build or error state past a deadline, with a Slack heads-up.
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.
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.
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.