IT OPS
Agentic Cloudflare WAF Drift Investigation with Confluence Writeup
When WAF drift is detected, an agent investigates who changed what, correlates it with recent incidents and deploys, drafts a plain-English root-cause writeup in Confluence.
How it runs
The automated pipeline, trigger to output.
- TriggerDrift signal or schedule starts investigation
- ActionRead WAF diff and audit log from CloudflareCloudflare
- LogicAgent judges if change weakened protection and was justified
- ActionPublish root-cause writeup to ConfluenceConfluence
- OutputPage on-call via PagerDuty if change looks maliciousPagerDuty
What it does
Goes beyond detecting drift to explaining it. When a Cloudflare WAF change is found, an agent gathers the diff, the audit-log actor, and surrounding context, reasons about whether the edit was a legitimate response to an incident or something suspicious, and publishes a readable investigation page in Confluence. If the change weakens protection without justification, it pages the on-call engineer.
When to use it
Use it when raw diffs aren't enough and you want a judgment call plus documentation. Good for lean security teams who need an analyst-style writeup of every firewall change without a human staring at audit logs.
How it works
- 1A scheduled trigger or upstream drift signal starts the investigation.
- 2The agent reads the WAF diff and audit log from Cloudflare to establish what changed and who did it.
- 3It reasons over the change to decide whether the edit reduced protection and whether it maps to a known, justified incident.
- 4The agent drafts a root-cause writeup and publishes it as a Confluence page.
- 5If the change looks malicious or unjustified, it triggers a PagerDuty incident for on-call.
Set it up
What you configure once, before turning it on.
- 1Connect CloudflareWorkers, Pages, R2, KV — the edge stack.
- 2Connect ConfluenceSpaces, pages, blueprints.
- 3Connect PagerDutyIncidents, on-call, escalations.
- 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.