IT OPS
Cloudflare audit-log sentry: flag out-of-band zone edits in real time
On a webhook or short schedule, ingests new Cloudflare audit-log entries and alerts Slack when DNS or security settings were changed outside the GitOps pipeline by a human…
How it runs
The automated pipeline, trigger to output.
- TriggerPolling schedule or webhook fires
- ActionFetch new Cloudflare audit-log entriesCloudflare
- LogicKeep human-origin DNS/security mutations only
- ActionAlert each out-of-band change to SlackSlack
- OutputOpen GitHub issue to reconcile the changeGitHub
What it does
Turns Cloudflare's audit log into an early-warning feed for unauthorized or undocumented changes. It reads recent audit entries, isolates the ones that mutate DNS records or zone security settings, and decides whether each change came from your automation service token or from a human clicking in the dashboard.
When to use it
Use it when only the CI pipeline is supposed to touch the zone, but you need to catch the inevitable emergency hand-edit before it drifts the manifest. It gives security and on-call a real-time trail of who changed what, by which actor, and when.
How it works
- 1A short polling schedule (or inbound webhook) fires the run.
- 2Fetch audit-log entries since the last checkpoint from the Cloudflare API.
- 3A logic step filters to record/setting mutations and splits automated actor tokens from human dashboard actors.
- 4Automation-origin changes are logged and dropped; human-origin changes continue.
- 5Post each out-of-band change to Slack with the actor, action, and old/new value.
- 6Open a GitHub issue so the change gets reconciled into the manifest.
Set it up
What you configure once, before turning it on.
- 1Connect CloudflareWorkers, Pages, R2, KV — the edge stack.
- 2Connect SlackChannels, DMs, threads, mentions.
- 3Connect GitHubRepos, issues, pull requests, actions.
- 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.