IT OPS
Auto-Remediate Cloudflare DNS Drift via Manifest PR
On a schedule it detects DNS records that drifted from the manifest, and for low-risk record types it reverts Cloudflare back to the manifest value.
How it runs
The automated pipeline, trigger to output.
- TriggerSchedule fires for remediation pass
- ActionFetch live records (Cloudflare) and manifest (GitHub)Cloudflare
- LogicSplit drift into auto-revertible vs human-review
- ActionRevert low-risk records in Cloudflare to manifest valueCloudflare
- ActionOpen GitHub PR documenting correctionsGitHub
- OutputPost PR link and held-back items to SlackSlack
What it does
This workflow closes the loop on drift instead of just reporting it. It finds where the live Cloudflare zone diverges from the manifest, automatically restores the manifest-defined value for safe-to-revert record types, and records every correction in a GitHub pull request for review and history.
When to use it
Use it once you trust your manifest as the true source of record and want self-healing DNS for low-risk records (such as CNAME and TXT verification records), while keeping risky changes human-gated. It removes the toil of manually re-applying values after an out-of-band edit, while leaving an auditable paper trail of what the automation touched.
How it works
- 1A schedule fires to start the remediation pass.
- 2The flow fetches live records from Cloudflare and reads the manifest from GitHub.
- 3A logic step computes drift and splits it into auto-revertible records versus changes that require human review.
- 4For auto-revertible records, an action updates Cloudflare back to the manifest value.
- 5A second action opens a GitHub PR summarizing each reverted record and listing the human-review items.
- 6The PR link and any held-back changes are posted to Slack.
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.