DEVOPS
Nightly cache warm of top pages after purge
On a schedule, purges Cloudflare for a curated list of high-traffic pages and immediately re-requests each one to repopulate the edge cache before peak traffic.
How it runs
The automated pipeline, trigger to output.
- TriggerNightly schedule fires
- LogicLoad curated priority URL list
- ActionCloudflare purge-by-URL for priority pagesCloudflare
- ActionFetch each URL to warm the edgeShell
- OutputSlack digest of warm resultsSlack
What it does
This workflow runs on a cron schedule, purges a defined set of your most-visited pages from Cloudflare, then warms them by issuing a fetch to each URL so the edge re-caches a fresh copy. Your busiest pages are guaranteed fresh and already cached when morning traffic arrives.
When to use it
Use it when you deploy overnight or regenerate static content on a daily job and want predictable, pre-warmed edge cache for key landing pages. It avoids the first-visitor-of-the-day paying the cache-miss penalty.
How it works
- 1A schedule trigger fires nightly after your deploy window.
- 2A logic step loads the curated list of priority URLs from config.
- 3Cloudflare purge-by-URL clears those specific pages.
- 4A shell step fetches each URL to repopulate the cache and records the cache-status header.
- 5A Slack digest reports how many pages warmed successfully and flags any that returned a non-200 or stayed a MISS.
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 SlackChannels, DMs, threads, mentions.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, 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.