IT OPS
Daily Cloudflare DNS Snapshot to Postgres History
Each day it snapshots the entire live Cloudflare zone into a Postgres history table and flags records that changed since the previous snapshot.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily schedule fires
- ActionFetch full live DNS zone from CloudflareCloudflare
- ActionLoad latest prior snapshot from PostgresPostgres
- LogicDiff current vs prior, tag each record's change type
- ActionWrite timestamped snapshot + change tags to PostgresPostgres
- OutputSend daily change summary to SlackSlack
What it does
This workflow builds a durable, queryable history of your DNS. Daily it captures the full live Cloudflare zone, stores it as a timestamped snapshot in Postgres, and diffs it against the most recent prior snapshot to record exactly what changed and when.
When to use it
Use it when you need an audit trail for compliance or incident forensics: answering "what did this record point to last Tuesday" or "who changed this and when" after an outage. Unlike a manifest comparison, this captures drift even when there is no source-of-truth file, giving you a self-recording change log of the zone itself.
How it works
- 1A daily schedule starts the snapshot run.
- 2The flow fetches all live DNS records from the Cloudflare zone.
- 3It loads the latest prior snapshot rows from Postgres for comparison.
- 4A logic step diffs current versus prior and tags each record as unchanged, new, modified, or deleted.
- 5An action writes the new snapshot plus the per-record change tags into the Postgres history table.
- 6The diff summary is delivered to Slack so the team sees the day's churn at a glance.
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.