IT OPS
Cloudflare manifest apply-on-merge: push approved DNS changes and verify
When a DNS manifest pull request merges, applies the changed records to the Cloudflare zone, re-reads the zone to confirm the update took.
How it runs
The automated pipeline, trigger to output.
- TriggerManifest PR merged on GitHubGitHub
- LogicParse merged diff into record create/update/delete set
- ActionApply changed records to Cloudflare zoneCloudflare
- ActionRe-fetch zone records to verify the writeCloudflare
- LogicDecide pass/fail from verification read
- OutputReport apply result to SlackSlack
What it does
Closes the GitOps loop in the apply direction. When a pull request that touches the DNS manifest merges to the main branch, it pushes exactly the changed records into the Cloudflare zone, then reads the zone back to verify the live state now matches what was merged.
When to use it
Use it when you want reviewed-and-merged manifest changes to reach production automatically instead of waiting for the next reconcile, and you need an immediate confirmation that the API write actually landed. It pairs naturally with the scheduled drift sentry, which handles the detect direction.
How it works
- 1A GitHub merge event on the manifest path triggers the run.
- 2A logic step parses the merged diff into a set of record creates, updates, and deletes.
- 3Apply each change to the Cloudflare zone through the API.
- 4Re-fetch the affected records from Cloudflare and compare them to the merged manifest values.
- 5A logic step decides pass or fail based on the verification read.
- 6Post the apply result — confirmed live or failed-and-reverted — to Slack with per-record status.
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.
- 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.