IT OPS
Cloudflare WAF Drift Severity Triage → PagerDuty + ClickUp
Diffs live Cloudflare WAF rules against the baseline, classifies each drift by severity (security-weakening vs cosmetic), pages on-call via PagerDuty for high-risk changes.
How it runs
The automated pipeline, trigger to output.
- TriggerSchedule fires severity triage run
- ActionPull live WAF rules and actions from CloudflareCloudflare
- ActionLoad approved baseline from GitHubGitHub
- LogicDiff and classify drift by security severity
- ActionPage on-call via PagerDuty for high-severity driftPagerDuty
- OutputFile ClickUp ticket for low-severity driftClickUp
What it does
Not all WAF drift is equal. This detects changes against the approved baseline and routes them by risk: a rule that was disabled, set to log-only, or had its block action weakened pages on-call immediately, while low-risk edits become a tracked ClickUp ticket for normal triage.
When to use it
Use this when you need drift detection that distinguishes a dangerous security regression (someone turned off SQLi blocking) from a harmless description tweak — and want the dangerous case to wake someone up.
How it works
- 1A schedule fires the triage run.
- 2Cloudflare returns the live WAF rules and their actions for the zone.
- 3A GitHub action loads the approved baseline.
- 4A logic step diffs and scores each drift: weakened action or disabled protective rule = high severity, else low.
- 5High-severity drift triggers a PagerDuty incident with the offending rule and delta.
- 6Low-severity drift opens a ClickUp ticket for scheduled follow-up.
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 PagerDutyIncidents, on-call, escalations.
- 4Connect ClickUpDocs + tasks + chats in one workspace.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, 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.