IT OPS
Cloudflare DNS drift sentry: diff zone against manifest, open correction PR
On a schedule, compares live Cloudflare zone records against a Git-tracked DNS manifest and, when they diverge, opens a pull request that rewrites the manifest to match (or flags…
How it runs
The automated pipeline, trigger to output.
- TriggerDaily schedule fires
- ActionFetch live DNS records from Cloudflare zoneCloudflare
- ActionRead DNS manifest from GitHub repoGitHub
- LogicDiff live records vs manifest; exit if identical
- ActionOpen correction PR updating the manifestGitHub
- OutputPost drift summary and PR link to SlackSlack
What it does
Keeps your declared DNS source-of-truth and your live Cloudflare zone in sync. It pulls every record from the zone, normalizes it, diffs it against the manifest file in your repo, and when there is drift it opens a correction pull request with the exact added, removed, and changed records spelled out.
When to use it
Use it when DNS is supposed to be managed as code but humans still make emergency dashboard edits. The recurring diff turns silent, undocumented changes into reviewable PRs so the manifest never rots and on-call always knows the real state of the zone.
How it works
- 1A daily schedule fires the run.
- 2Fetch all DNS records for the configured zone from the Cloudflare API.
- 3Read the committed manifest file from the GitHub repo and normalize both sides (sort, strip TTL noise, canonicalize record types).
- 4A logic step computes the diff; if there is no drift the run exits quietly.
- 5On drift, open a GitHub pull request that updates the manifest to reflect live records, with the diff in the PR body.
- 6Post a Slack summary linking the PR and listing the changed record names.
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.