AI AGENTS
Cloudflare Page-Rule Change Validator
After a Cloudflare configuration change is deployed, this agent waits, re-measures cache-hit ratio for the affected paths.
How it runs
The automated pipeline, trigger to output.
- TriggerWebhook fires on config change deployHTTP webhook
- ActionRecord baseline cache metrics for pathsCloudflare
- LogicWait soak window for fresh traffic
- ActionRe-pull metrics and compute deltaCloudflare
- LogicClassify outcome and decide on rollback
- OutputPost validated verdict to SlackSlack
What it does
Closing the loop on cache optimizations: when a page-rule or cache-key change is applied, this workflow captures a before-snapshot, waits for traffic to accumulate, then re-measures the cache-hit ratio for the affected paths. It judges whether the change delivered the expected improvement and posts a verdict — improved, no effect, or regressed — with a rollback recommendation when needed. It turns guesswork into measured outcomes.
When to use it
Use it right after applying any Cloudflare cache change you want to verify in production, especially changes proposed by the optimizer or pruner workflows.
How it works
- 1A webhook fires when a Cloudflare config change is deployed, carrying the affected path patterns.
- 2The agent records the baseline cache metrics for those paths from Cloudflare.
- 3It waits a configured soak window for fresh traffic to flow.
- 4It re-pulls the same metrics and computes the post-change hit-ratio delta.
- 5A branch classifies the result and decides if a rollback is warranted.
- 6It posts the validated verdict and any rollback recommendation to Slack.
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.