IT OPS
Cloudflare DNS drift audit against Coda registry
Every morning, compares live Cloudflare DNS records to the source-of-truth Coda registry and posts a drift report to Discord listing every record that is missing, extra…
How it runs
The automated pipeline, trigger to output.
- TriggerDaily schedule (e.g. 7:00 AM)
- ActionList all DNS records for configured zonesCloudflare
- ActionRead intended DNS records tableCoda
- LogicDiff live vs intended: missing / extra / mismatched
- LogicDrift found? Skip notification if clean
- OutputPost grouped drift report to DiscordDiscord
What it does
This workflow treats a Coda table as the single source of truth for your DNS and audits Cloudflare against it on a schedule. It pulls every record from your Cloudflare zones, pulls the intended records from Coda, diffs them by name and type, and reports three buckets: records present in Cloudflare but not in Coda (drift in), records in Coda but missing from Cloudflare (drift out), and records whose value, TTL, or proxy status disagree. It is read-only — it never changes DNS, so it is safe to run continuously as an early-warning monitor.
When to use it
Use it when DNS changes can happen out of band (a teammate editing the dashboard, an automation, a vendor) and you want to know within a day rather than during an outage. Ideal for teams that already maintain a Coda registry and want it kept honest.
How it works
- 1A daily schedule fires the run.
- 2Fetch all DNS records for the configured zones from Cloudflare.
- 3Read the intended-records table from Coda.
- 4Diff the two sets, classifying each record as match, missing, extra, or mismatched.
- 5If any drift exists, format a grouped report and post it to the ops Discord channel; otherwise stay silent.
Set it up
What you configure once, before turning it on.
- 1Connect CloudflareWorkers, Pages, R2, KV — the edge stack.
- 2Connect CodaDocs, packs, automations.
- 3Connect DiscordCommunity channels + voice + bots.
- 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.