AI AGENTS
Cloudflare Origin Cache-Header Auditor
Crawls high-traffic origin responses, flags assets whose Cache-Control headers prevent edge caching, and files a Linear ticket per fixable header with the recommended directive.
How it runs
The automated pipeline, trigger to output.
- TriggerSchedule launches the audit
- ActionPull highest-traffic paths from analyticsCloudflare
- ActionFetch origin responses and read headersHTTP webhook
- LogicFilter to cache-blocking headers on static content
- LogicMap findings to recommended directives
- OutputFile a Linear ticket per fixable assetLinear
What it does
Many cache misses trace back to the origin sending no-cache, no-store, or missing Cache-Control headers on content that is actually static. This workflow takes your top-traffic paths from Cloudflare analytics, fetches each origin response, inspects the caching headers, and identifies assets that should be cacheable but aren't. For every fixable case it files a Linear ticket naming the URL, the current header, and the recommended directive for the backend team.
When to use it
Use it when edge cache rules look correct but hit ratio is still poor — the culprit is usually origin headers, not Cloudflare config. A good periodic hygiene check for backend caching.
How it works
- 1A schedule launches the audit.
- 2The workflow pulls the highest-traffic paths from Cloudflare analytics.
- 3It fetches each origin response via HTTP and reads the Cache-Control and related headers.
- 4A branch filters to responses where headers block caching of otherwise-static content.
- 5It maps each finding to a recommended header directive.
- 6It files one Linear ticket per fixable asset for the backend team.
Set it up
What you configure once, before turning it on.
- 1Connect CloudflareWorkers, Pages, R2, KV — the edge stack.
- 2Connect HTTP webhookTrigger any URL on agent actions.
- 3Connect LinearIssues, projects, cycles, triage.
- 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
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.
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.
Datadog Bill Spike Attribution Agent
When a daily Datadog cost check detects a spend jump, an agent attributes the increase to the specific services and metric types driving it and posts a ranked breakdown to Slack.
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.
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.
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.
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.