IT OPS
Cloudflare Orphan Records via Axiom Traffic Correlation
Scheduled audit that cross-references Cloudflare DNS records against Axiom request logs to find subdomains that resolve but have served zero traffic for weeks.
How it runs
The automated pipeline, trigger to output.
- TriggerMonthly schedule kicks off the correlation run
- ActionPull full DNS record set from CloudflareCloudflare
- ActionQuery Axiom for per-hostname request countsAxiom
- LogicJoin records to traffic; keep zero-traffic resolvers
- ActionFile GitLab decommission tickets with evidenceGitLab
- OutputPost orphan summary to SlackSlack
What it does
Resolution checks alone miss the records that still resolve but point at a zombie origin nobody hits. This workflow correlates each Cloudflare record against Axiom request-log data to find subdomains with no meaningful traffic over a configurable lookback. Those silent records are the best candidates for decommissioning, and each one becomes a GitLab cleanup ticket.
When to use it
Use it during DNS hygiene sweeps or cost/attack-surface reduction efforts, when you want evidence (zero traffic) before proposing a record be deleted, not just a guess.
How it works
- 1A monthly schedule kicks off the correlation run.
- 2Cloudflare returns the full record set for the in-scope zones.
- 3Axiom is queried for per-hostname request counts over the lookback window.
- 4A join + filter keeps records with zero or near-zero traffic that still resolve.
- 5For each candidate a GitLab issue is opened proposing decommission, with the traffic evidence attached.
- 6A Slack message summarizes how many orphans were found and the total request volume reclaimed.
Set it up
What you configure once, before turning it on.
- 1Connect CloudflareWorkers, Pages, R2, KV — the edge stack.
- 2Connect AxiomLog streams, queries, dashboards.
- 3Connect GitLabRepos, MRs, pipelines, registry.
- 4Connect SlackChannels, DMs, threads, mentions.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More IT Ops workflows
Daily Building Anomaly Digest to MS Teams
Each morning queries BigQuery for the prior day's flagged sensor anomalies, summarizes them by site and system into a ranked briefing.
Indoor Air Quality Breach to Tenant Notice and Work Order
Listens for CO2, VOC, or humidity sensor alerts via webhook, and when a zone exceeds occupant-safety limits it emails affected tenants, opens a Monday remediation task.
Self-Service Reclaim Email for Idle Users
Detects users idle in a SaaS app past the threshold and emails each one a keep-or-release link; unanswered seats after the deadline are auto-flagged for removal.
Outlook Room Conflict Resolver with Approval Gate in Teams
When an Outlook room clashes, proposes a rebooking and asks the bumped meeting's organizer to approve the move in Microsoft Teams before any change is made.
Outlook Room Double-Booking Resolver with Auto-Rebook
Detects when two meetings claim the same Outlook room resource and automatically relocates the lower-priority meeting to a comparable free room.
Monthly Wasted-License Cost Report
Aggregates inactive-seat data across all tracked SaaS apps each month, computes total reclaimable spend, and delivers a ranked cost report to leadership in Notion and Slack.
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.