IT OPS
Cloudflare WAF Drift Detector vs IaC Baseline → ClickUp Ticket
On a schedule, pulls live Cloudflare WAF rules, diffs them against the approved Terraform/IaC baseline in Git.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily schedule fires the drift check
- ActionList live WAF rules from Cloudflare zoneCloudflare
- ActionRead approved IaC baseline from GitHubGitHub
- LogicDiff live rules against baseline; stop if identical
- OutputOpen ClickUp ticket per drifted rulesetClickUp
What it does
Compares the WAF custom rules actually running on your Cloudflare zone against the version-controlled baseline that defines what *should* be deployed. When live config diverges from the approved baseline, it files a single ClickUp ticket per drifted ruleset, including the specific fields that changed.
When to use it
Run this when your WAF is managed as code but people still have console access and can hand-edit rules. It catches out-of-band changes, half-finished hotfixes, and silent reverts before they become an incident or audit finding.
How it works
- 1A daily schedule fires the workflow.
- 2The Cloudflare step lists all WAF custom rules and rulesets for the target zone.
- 3The GitHub step reads the approved baseline file (e.g. `waf/rules.tf` or exported JSON) from the main branch.
- 4A logic step normalizes both sides and computes a structured diff — added, removed, and modified rules with old/new values.
- 5If the diff is empty the run ends quietly; otherwise it continues.
- 6A ClickUp ticket is created summarizing each drifted rule, the field deltas, and the owning zone.
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 ClickUpDocs + tasks + chats in one workspace.
- 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.