IT OPS
DNS Manifest PR Preflight Drift Check
When someone opens a pull request that edits the DNS manifest, this fetches the live Cloudflare zone and comments on the PR showing the exact records the merge will create…
How it runs
The automated pipeline, trigger to output.
- TriggerPull request opened touching DNS manifestGitHub
- ActionRead proposed manifest from PR branchGitHub
- ActionFetch live DNS records from CloudflareCloudflare
- LogicCompute apply plan (create/change/delete + unmanaged live records)
- OutputPost apply plan as PR commentGitHub
What it does
This workflow turns every DNS manifest change into a reviewable plan. The moment a pull request touches the manifest file, it compares the proposed manifest against the live Cloudflare zone and writes a human-readable preview of the resulting changes directly on the PR.
When to use it
Use it when DNS changes go through pull-request review and you want reviewers to see the real-world impact before approving. It surfaces the difference between what the PR claims and what is actually live right now, catching cases where the live zone already drifted from main, so a merge would silently revert an out-of-band fix.
How it works
- 1A GitHub pull-request event triggers when the manifest path changes.
- 2The flow reads the proposed manifest from the PR branch.
- 3It fetches the current live DNS records from the Cloudflare zone.
- 4A logic step builds an apply plan: records the merge would add, modify, or remove, plus any live records the manifest does not account for.
- 5The plan is posted back as a PR comment so reviewers approve with full context.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect CloudflareWorkers, Pages, R2, KV — the edge stack.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, 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.