IT OPS
Cloudflare DNS Drift Snapshot & Diff Alerter
Hourly snapshot of every Cloudflare zone's records compared against the last stored snapshot, alerting Slack on any added, removed, or retargeted record so unexpected DNS changes…
How it runs
The automated pipeline, trigger to output.
- TriggerHourly schedule triggers the snapshot
- ActionFetch current DNS record set from CloudflareCloudflare
- ActionStore new snapshot and read prior one from PostgresPostgres
- LogicDiff snapshots; pass only when changes exist
- OutputPost old-vs-new change report to SlackSlack
What it does
This workflow takes a recurring snapshot of all DNS records in your Cloudflare zones, stores it, and diffs it against the previous snapshot. Any change — a new CNAME, a deleted A record, a retargeted origin — is surfaced immediately. It turns silent, untracked DNS edits into an auditable change feed.
When to use it
Use it when multiple people or automation tools can edit DNS and you need a tamper-evident record of what changed and when. It is the early-warning layer that catches a record being repointed at an attacker-controlled or decommissioned origin between your slower full audits.
How it works
- 1An hourly schedule triggers the snapshot.
- 2Cloudflare returns the current record set for all zones.
- 3The snapshot is written to Postgres and the prior snapshot is read back.
- 4A diff computes added, removed, and modified records.
- 5A filter passes only runs where the diff is non-empty.
- 6A formatted change report is posted to Slack with old-vs-new values for each touched record.
Set it up
What you configure once, before turning it on.
- 1Connect CloudflareWorkers, Pages, R2, KV — the edge stack.
- 2Connect PostgresAny Postgres URL — query, write, migrate.
- 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
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.