IT OPS
Validate a proposed Cloudflare zonefile against Coda before apply
On demand, exports the live Cloudflare zonefile via the API, diffs it against a Coda-rendered intended zonefile using shell tooling.
How it runs
The automated pipeline, trigger to output.
- TriggerManual validation run
- ActionExport live zonefile from CloudflareCloudflare
- ActionRender intended zonefile from Coda registryCoda
- ActionRun normalized zonefile diff in shellShell
- LogicClassify diff: clean vs changed, count deltas
- OutputPost dry-run pass/fail report to DiscordDiscord
What it does
This workflow gives operators a dry-run gate before any DNS apply. It pulls the current zonefile from Cloudflare, renders an intended zonefile from the Coda registry, and uses a shell step to run a structured diff between them. The result is a clear pass/fail: if the live zone already matches the registry the change is a no-op, and if it differs the report shows the exact added, removed, and modified lines an apply would produce. Nothing is written to Cloudflare — this is purely a validation and review step.
When to use it
Run it before promoting registry edits, during change-review, or in a pull-request-style approval flow where a human wants to see the precise diff a reconcile would make before authorizing it.
How it works
- 1An operator triggers a validation run.
- 2Export the live zonefile for the target zone from Cloudflare.
- 3Read the intended records from Coda and render them to zonefile format.
- 4A shell step runs a normalized diff between the live and intended zonefiles.
- 5Classify the diff as clean or changed and count the deltas.
- 6Post the pass/fail dry-run report with the diff to Discord.
Set it up
What you configure once, before turning it on.
- 1Connect CloudflareWorkers, Pages, R2, KV — the edge stack.
- 2Connect CodaDocs, packs, automations.
- 3Connect ShellRun sandboxed commands inside the workspace.
- 4Connect DiscordCommunity channels + voice + bots.
- 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
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.