IT OPS
Vercel vs Cloudflare DNS Drift Reconciler
Compares the DNS targets Vercel expects for each configured domain against the live records in Cloudflare and alerts when an A, CNAME, or apex record has drifted out of alignment.
How it runs
The automated pipeline, trigger to output.
- TriggerTwice-daily schedule
- ActionFetch expected DNS config from VercelVercel
- ActionRead live records from Cloudflare zoneCloudflare
- LogicDiff expected vs actual records
- ActionLog drift event to AxiomAxiom
- OutputSend Slack report of drifted recordsSlack
What it does
This workflow reconciles intent versus reality for your DNS. It reads each Vercel domain's required verification and routing records, queries the matching zone in Cloudflare for the live record values, and flags any mismatch — a CNAME pointing at the wrong target, a missing apex A record, or a stale value left behind after a migration.
When to use it
Use it when domains are managed in Cloudflare but served by Vercel and the two can quietly diverge. DNS drift is the most common root cause of failed certificate renewal and intermittent 404s, and it rarely throws an error until traffic breaks.
How it works
A twice-daily schedule starts the run. One action fetches each domain's expected configuration from Vercel; a second action reads the live records from the corresponding Cloudflare zone. A logic step diffs expected against actual, normalizing for trailing dots and proxied flags. When drift is found, an action writes a structured event to Axiom for trend analysis, and an output sends a Slack message listing each drifted record with both the expected and observed value so the fix is unambiguous.
Set it up
What you configure once, before turning it on.
- 1Connect VercelDeploys, runtime logs, analytics.
- 2Connect CloudflareWorkers, Pages, R2, KV — the edge stack.
- 3Connect AxiomLog streams, queries, dashboards.
- 4Connect SlackChannels, DMs, threads, mentions.
- 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
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.