DEVOPS
Weekly Cloudflare Cache-Efficiency Scorecard to Confluence
Compiles a weekly cache hit-ratio scorecard per zone, flags any config change that measurably moved efficiency up or down.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule (Monday AM)
- ActionRead per-zone hit-ratio trends (Cloudflare)Cloudflare
- ActionFetch week's merged edge-config commits (GitLab)GitLab
- LogicAttribute ratio moves to specific changes
- ActionPublish scorecard page (Confluence)Confluence
- OutputPost headline digest + page link to SlackSlack
What it does
This is the reporting companion to the real-time sentinels. Once a week it reads cache hit ratio trends per Cloudflare zone, lines them up against the week's merged GitLab config changes, and attributes ratio gains and losses to specific commits. It publishes a scorecard page to Confluence and drops a short digest in Slack so the team sees which edits helped or hurt without digging through dashboards.
When to use it
Use it for the weekly ops review, to build a paper trail of cache-efficiency wins and regressions, and to spot slow erosion that never trips a single-point alert. It makes cache health a visible, accountable metric.
How it works
- 1Schedule fires weekly (e.g. Monday morning).
- 2Cloudflare returns per-zone hit-ratio trends for the past week.
- 3GitLab supplies the week's merged edge-config commits.
- 4A logic step attributes notable ratio moves to specific changes.
- 5Confluence publishes the formatted scorecard page.
- 6Slack posts a digest with the headline numbers and the page link.
Set it up
What you configure once, before turning it on.
- 1Connect CloudflareWorkers, Pages, R2, KV — the edge stack.
- 2Connect GitLabRepos, MRs, pipelines, registry.
- 3Connect ConfluenceSpaces, pages, blueprints.
- 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 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.