AI AGENTS
Cloudflare Cache-Miss Spike Responder
When Cloudflare cache-miss rate spikes past a threshold, this workflow analyzes which paths regressed and posts a diagnosed alert with a suggested fix to Slack.
How it runs
The automated pipeline, trigger to output.
- TriggerWebhook receives cache-miss spike alertHTTP webhook
- ActionFetch recent edge analytics and per-path metricsCloudflare
- LogicDiff current miss rate against rolling baseline
- LogicConfirm regression is real, drop noise
- OutputPost diagnosed alert with suggested fix to SlackSlack
What it does
This is a fast-reaction monitor. A webhook from your monitoring layer (or a Cloudflare alert) fires when cache-miss rate jumps. The workflow immediately pulls the last hour of edge analytics, isolates which URL patterns regressed versus baseline, and posts a Slack message that names the offending paths, the likely cause, and a one-line suggested cache-key or TTL fix — so on-call can act in seconds instead of hunting through dashboards.
When to use it
Use it when a deploy or origin config change silently tanks your hit ratio and you want to know within minutes, not on the next weekly report.
How it works
- 1A webhook trigger receives the cache-miss spike alert.
- 2The workflow fetches the recent cache analytics and per-path metrics from Cloudflare.
- 3It compares current miss rates against the rolling baseline to find the deltas.
- 4A branch confirms the regression is real and not noise; spurious spikes are dropped.
- 5It composes a diagnosis: offending paths, suspected cause, and a concrete suggested change.
- 6The alert is delivered to the on-call Slack channel.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect CloudflareWorkers, Pages, R2, KV — the edge stack.
- 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 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.