IT OPS
Reconcile Cloudflare DNS to match the Coda registry
On a schedule, applies the Coda DNS registry to Cloudflare — creating missing records, updating mismatched ones, and deleting unauthorized extras.
How it runs
The automated pipeline, trigger to output.
- TriggerHourly schedule
- ActionRead managed DNS records from CodaCoda
- ActionList current Cloudflare recordsCloudflare
- LogicBuild change plan: create / update / scoped delete
- ActionApply create/update/delete via Cloudflare APICloudflare
- OutputPost applied-changes summary to DiscordDiscord
What it does
This is the write counterpart to a drift audit: it makes Cloudflare conform to Coda. After computing the diff it creates records that exist in Coda but not in Cloudflare, updates records whose value, TTL, or proxy flag disagree, and removes records in Cloudflare that are not in the registry. Deletions only target records explicitly marked as managed in Coda, so unmanaged vendor records are left alone. Every applied change is logged and summarized.
When to use it
Use it once your Coda registry is trusted and complete, and you want DNS to self-heal rather than just alert. Good for environments where the registry is the change-control system and the dashboard should never be edited by hand.
How it works
- 1A schedule (e.g. hourly) starts the reconcile.
- 2Read the managed-records table from Coda and list current records from Cloudflare.
- 3Compute the change plan: creates, updates, and scoped deletes.
- 4Apply each change through the Cloudflare API, capturing success or failure per record.
- 5Post a Discord summary of what was created, updated, deleted, and any errors.
Set it up
What you configure once, before turning it on.
- 1Connect CodaDocs, packs, automations.
- 2Connect CloudflareWorkers, Pages, R2, KV — the edge stack.
- 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.