IT OPS
Cloudflare Dangling-CNAME Sweeper to GitLab Tickets
Weekly audit that resolves every CNAME record in your Cloudflare zones, flags any that point at an unclaimed or NXDOMAIN origin.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule fires the DNS audit
- ActionList all CNAME records across Cloudflare zonesCloudflare
- LogicResolve each target; keep only dead/unclaimed origins
- ActionOpen a GitLab issue per orphaned subdomainGitLab
- OutputPost run summary with issue links to SlackSlack
What it does
This workflow walks all CNAME records across your Cloudflare zones and checks whether each target still resolves to a live, claimed origin. CNAMEs pointing at decommissioned cloud buckets, retired Heroku/Vercel apps, or NXDOMAIN hosts are classic subdomain-takeover risks. Every dangling record becomes a GitLab issue with the record name, target, and zone, so nothing rots silently.
When to use it
Run it on any account with dozens or hundreds of subdomains where teams spin up and tear down origins faster than DNS gets cleaned. It is especially valuable after a platform migration or vendor switch left CNAMEs aimed at hosts you no longer control.
How it works
- 1A weekly schedule fires the audit.
- 2Cloudflare returns every CNAME record across all zones.
- 3For each target the workflow performs a resolution check (live origin vs. NXDOMAIN / unclaimed bucket pattern).
- 4A filter keeps only records whose targets are dead or takeover-prone.
- 5For each flagged record a GitLab issue is opened, labeled `dns-dangling`, with the subdomain, target, and zone.
- 6A Slack summary posts the total count and links to the new issues.
Set it up
What you configure once, before turning it on.
- 1Connect CloudflareWorkers, Pages, R2, KV — the edge stack.
- 2Connect GitLabRepos, MRs, pipelines, registry.
- 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 IT Ops workflows
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.
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.
Reconcile SSO logins against expense spend to find unmanaged tools
Joins SSO usage data with expense/payment records in Snowflake to surface tools that are being used but not paid for, or paid for but never logged.
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.
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.
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.