IT OPS
Scheduled Cloudflare DNS Drift Audit vs Git Manifest
Every hour, compares your live Cloudflare DNS zone against a version-controlled YAML manifest in GitHub and posts any added, removed, or changed records to Slack.
How it runs
The automated pipeline, trigger to output.
- TriggerHourly schedule fires
- ActionFetch live DNS records from Cloudflare zoneCloudflare
- ActionRead canonical zone manifest from GitHubGitHub
- LogicDiff live records against manifest (added/removed/changed)
- LogicStop if no drift detected
- OutputPost drift report to Slack channelSlack
What it does
This workflow keeps your live Cloudflare DNS in lockstep with the source-of-truth manifest you keep in Git. On a fixed schedule it pulls every record from the zone, pulls the committed manifest, diffs them field by field, and reports exactly which records drifted.
When to use it
Run this when DNS is managed as code but humans still make emergency changes in the Cloudflare dashboard. It catches the manual edit someone forgot to commit, the record someone deleted by accident, and the TTL or proxy-status that quietly changed. Ideal for teams that want continuous assurance without standing up full IaC reconciliation.
How it works
- 1A schedule fires hourly to start the audit.
- 2The flow fetches all DNS records for the configured zone from the Cloudflare API.
- 3It reads the canonical `dns/zone.yaml` manifest from the GitHub repository.
- 4A logic step normalizes both sets (name, type, content, TTL, proxied) and computes added, removed, and modified records.
- 5If the diff is empty the run ends silently; otherwise it formats a per-record changelog.
- 6The drift report is posted to a Slack channel with a clear added/removed/changed breakdown.
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.
- 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
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.