IT OPS
Cloudflare Pages cache sweep with shell reclaim calc and Axiom + Slack report
Weekly, pulls Cloudflare Pages deployment data, runs a shell script to compute reclaimable storage and rank the bloatiest projects, deletes stale builds.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule starts the sweep
- ActionPull deployment inventory across projectsCloudflare
- ActionShell script computes reclaim and ranks bloatShell
- ActionDelete stale builds identified by the scriptCloudflare
- ActionLog structured run record to AxiomAxiom
- OutputPost ranked weekly digest to SlackSlack
What it does
This is the reporting-heavy weekly sweep. It collects deployment metadata from Cloudflare across every Pages project, hands it to a shell script that computes reclaimable bytes and ranks projects from most to least bloated, then deletes the stale builds. The run is logged to Axiom as a single structured event, and a human-readable ranked digest is posted to Slack so the team sees which projects are driving storage growth.
When to use it
Use this when you want one weekly artifact that both reclaims space and tells the team where bloat is concentrated, so cleanup effort and retention policy changes go to the noisiest projects first.
How it works
- 1A weekly schedule starts the sweep.
- 2Cloudflare returns deployment inventory across all projects.
- 3A shell step computes reclaimable storage and ranks projects by bloat.
- 4Cloudflare deletes the stale builds the script identified.
- 5Axiom ingests the structured run record with totals and per-project figures.
- 6Slack receives the ranked weekly digest.
Set it up
What you configure once, before turning it on.
- 1Connect CloudflareWorkers, Pages, R2, KV — the edge stack.
- 2Connect ShellRun sandboxed commands inside the workspace.
- 3Connect AxiomLog streams, queries, dashboards.
- 4Connect SlackChannels, DMs, threads, mentions.
- 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 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.