AI AGENTS
Cloudflare Cache-Key Query-Param Pruner
Scans Cloudflare logs for query parameters that fragment the cache without changing responses.
How it runs
The automated pipeline, trigger to output.
- TriggerSchedule starts the param scan
- ActionRetrieve request logs and cache statusCloudflare
- LogicCluster URLs differing only by query params
- LogicVerify params do not change the response
- ActionGenerate cache-key ignore-list change
- OutputOpen GitHub PR against IaC repoGitHub
What it does
Tracking and marketing query params (utm_*, fbclid, gclid, session ids) splinter a single cacheable asset into thousands of unique cache keys, crushing your hit ratio. This workflow scans Cloudflare request logs, clusters URLs that differ only by such params, confirms the responses are identical, and proposes a cache-key configuration that ignores them — delivered as a GitHub pull request against your infrastructure-as-code repo so the change is reviewed and version-controlled.
When to use it
Use it when high-traffic landing pages or product pages show poor cache performance and you suspect query-string fragmentation. Ideal for teams managing Cloudflare via Terraform.
How it works
- 1A schedule kicks off the scan.
- 2The workflow retrieves recent request logs and cache status from Cloudflare.
- 3It clusters URLs that are identical except for query parameters and measures the fragmentation cost.
- 4A branch verifies the candidate params never alter the response body before recommending removal.
- 5It generates the cache-key ignore-list change in your IaC format.
- 6It opens a GitHub pull request with the diff and the supporting analytics in the description.
Set it up
What you configure once, before turning it on.
- 1Connect CloudflareWorkers, Pages, R2, KV — the edge stack.
- 2Connect GitHubRepos, issues, pull requests, actions.
- 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.