DEVOPS
Gate Cloudflare deploys on CVE budget with Slack override
Before a Cloudflare deploy goes live, scans the build's container image for CVEs and halts the rollout when the severity budget is breached.
How it runs
The automated pipeline, trigger to output.
- TriggerCloudflare deploy queued webhookCloudflare
- ActionScan build image for CVEsCloudflare
- LogicCompare CVE tally to severity budget
- ActionPost approval request with breakdownSlack
- OutputResume or cancel Cloudflare deployCloudflare
What it does
This workflow intercepts a pending Cloudflare deployment, scans the image artifact for known vulnerabilities, and enforces a severity budget. If the image is clean it promotes the deploy automatically. If it breaches the budget, the rollout is paused and an approval request with the full CVE breakdown is sent to a Slack channel where an on-call engineer can approve or reject.
When to use it
Use it when you want CVE enforcement at the deploy boundary rather than at PR time, and you need a human override path for genuine emergencies (a hotfix that must ship despite a known low-risk finding).
How it works
- 1A webhook fires when a Cloudflare deploy is queued.
- 2An action scans the build's image and tallies CVEs by severity.
- 3A branch checks the tally against the budget.
- 4Within budget, the workflow promotes the Cloudflare deploy and exits.
- 5Over budget, it pauses the rollout and posts an approval prompt to Slack.
- 6The Slack decision either resumes or cancels the Cloudflare deploy.
Set it up
What you configure once, before turning it on.
- 1Connect CloudflareWorkers, Pages, R2, KV — the edge stack.
- 2Connect SlackChannels, DMs, threads, mentions.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, 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.