DEVOPS
ChatOps Cloudflare purge with a Slack approval gate
Lets an engineer request a Cloudflare purge from Slack; a full-zone purge requires a second person's approval before it runs, while scoped URL purges run immediately, and every…
How it runs
The automated pipeline, trigger to output.
- TriggerSlack slash command requests purgeSlack
- LogicBranch scoped-URL vs full-zone purge
- ActionCloudflare purge-by-URL for scoped requestsCloudflare
- ActionPost Slack approval gate for full-zoneSlack
- ActionCloudflare purge_everything on approvalCloudflare
- OutputReply with result and approver in threadSlack
What it does
This workflow turns Cloudflare cache purges into a controlled ChatOps action. An engineer types a purge request in Slack with a scope. Narrow URL purges execute right away; a risky purge-everything is held behind an approval button that a second team member must click before it fires. Each run is recorded.
When to use it
Use it when you want on-demand purges without handing everyone Cloudflare API tokens, and you need a guardrail so nobody flushes the entire zone during peak traffic on a whim. It gives you speed for safe operations and a human gate for dangerous ones.
How it works
- 1A Slack slash command starts the request with the requested scope and target.
- 2A logic branch splits scoped-URL purges from full-zone purges.
- 3Scoped purges call Cloudflare purge-by-URL immediately.
- 4Full-zone purges post an approval prompt to Slack and wait for a second approver to confirm.
- 5On approval, Cloudflare purge_everything runs; the result and approver are posted back to the thread.
Set it up
What you configure once, before turning it on.
- 1Connect SlackChannels, DMs, threads, mentions.
- 2Connect CloudflareWorkers, Pages, R2, KV — the edge stack.
- 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.