IT OPS
Cloudflare Pages cleanup with Slack approval gate before deletion
Builds a dry-run list of stale Cloudflare Pages deployments, posts the count and reclaimable storage to Slack with approve/cancel buttons.
How it runs
The automated pipeline, trigger to output.
- TriggerOperator triggers cleanup run
- ActionDry-run list eligible deployments and sizesCloudflare
- ActionPost candidate summary to Slack with approve buttonsSlack
- LogicBranch on approval response
- ActionDelete approved deploymentsCloudflare
- OutputConfirm reclaimed storage in Slack threadSlack
What it does
This is the human-in-the-loop version of cache cleanup. Instead of deleting automatically, it computes which Cloudflare Pages deployments are eligible for removal, summarizes how many builds and how much storage would be reclaimed, and asks an operator in Slack to approve. Deletion happens only after an explicit approval click, and the original Slack thread is updated with the final reclaimed total.
When to use it
Use this for high-stakes or shared Pages projects where an engineer should eyeball the cleanup before anything is purged, but you still want the heavy lifting automated.
How it works
- 1An operator triggers the run manually or via webhook.
- 2Cloudflare returns deployments and their sizes; a dry-run computes the eligible set.
- 3Slack posts the candidate count and reclaimable bytes with Approve and Cancel actions.
- 4A logic step waits on the response and branches: cancel ends the run, approve proceeds.
- 5Cloudflare deletes the approved deployments and reports freed storage.
- 6Slack updates the thread with the confirmed reclaim total.
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 IT Ops workflows
Daily Building Anomaly Digest to MS Teams
Each morning queries BigQuery for the prior day's flagged sensor anomalies, summarizes them by site and system into a ranked briefing.
Indoor Air Quality Breach to Tenant Notice and Work Order
Listens for CO2, VOC, or humidity sensor alerts via webhook, and when a zone exceeds occupant-safety limits it emails affected tenants, opens a Monday remediation task.
Self-Service Reclaim Email for Idle Users
Detects users idle in a SaaS app past the threshold and emails each one a keep-or-release link; unanswered seats after the deadline are auto-flagged for removal.
Outlook Room Conflict Resolver with Approval Gate in Teams
When an Outlook room clashes, proposes a rebooking and asks the bumped meeting's organizer to approve the move in Microsoft Teams before any change is made.
Outlook Room Double-Booking Resolver with Auto-Rebook
Detects when two meetings claim the same Outlook room resource and automatically relocates the lower-priority meeting to a comparable free room.
Monthly Wasted-License Cost Report
Aggregates inactive-seat data across all tracked SaaS apps each month, computes total reclaimable spend, and delivers a ranked cost report to leadership in Notion and Slack.
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.