AI AGENTS
Cloudflare Cache-Ratio Weekly Digest
Compiles a weekly cache-hit-ratio report from Cloudflare analytics, highlights week-over-week movers and top miss offenders, and emails a plain-English summary to stakeholders.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule triggers the digest
- ActionPull this week and last week analyticsCloudflare
- LogicCompute hit-ratio delta and rank movers
- ActionWrite plain-English trend summary
- OutputEmail digest to stakeholdersGmail
What it does
This workflow turns raw Cloudflare cache analytics into a readable weekly digest. It computes the zone-wide hit ratio, compares it to last week, surfaces the paths that improved or regressed the most, and writes a short narrative explaining what moved and why. The result is emailed to engineering leads and finance stakeholders who care about origin cost but won't open a Cloudflare dashboard.
When to use it
Use it for a recurring, low-effort visibility loop — keeping leadership informed of cache health and bandwidth-cost trends without anyone manually pulling numbers.
How it works
- 1A weekly schedule triggers the digest.
- 2The workflow pulls this week's and last week's cache analytics from Cloudflare.
- 3It calculates the hit-ratio delta and ranks the biggest path-level movers.
- 4It writes a plain-English summary of trends, wins, and regressions to watch.
- 5The formatted digest is emailed to the stakeholder list via Gmail.
Set it up
What you configure once, before turning it on.
- 1Connect CloudflareWorkers, Pages, R2, KV — the edge stack.
- 2Connect GmailRead, draft, send, label.
- 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 AI Agents workflows
Custom Metrics Cardinality Spike Pager
A webhook from a Datadog monitor fires when custom-metric cardinality jumps; an agent pinpoints the offending metric and tag, estimates the added cost.
Sentry-to-Confluence Runbook Updater
When a Sentry issue is resolved, the agent finds the matching Confluence runbook page and proposes an inline update with the verified fix.
Stale Doc-PR Chaser for Runbook Gaps
On a daily schedule the agent finds runbook doc PRs that were opened from resolved incidents but never reviewed, summarizes what each one fixes.
Resolved Incident to Public Troubleshooting Doc
For customer-facing errors resolved in Sentry, the agent drafts a sanitized troubleshooting entry and opens a PR to your ReadMe documentation.
On-Call Runbook Gap Closer: Resolved Sentry Issues to Doc PRs
An agent reads each newly resolved Sentry issue, compares the actual fix against your existing runbook, and opens a GitHub PR adding the missing remediation steps.
Weekly On-Call Doc-Gap Digest
Each week the agent reviews every Sentry issue resolved in the last 7 days, ranks the ones whose runbook coverage is missing or thin.
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.