IT OPS
Weekly Cloudflare WAF Compliance Report → Confluence + Slack
Each week, compares live Cloudflare WAF rules against the IaC baseline across zones and publishes a compliance report to Confluence summarizing in-sync vs drifted rules.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule starts report build
- ActionPull WAF rules per zone from CloudflareCloudflare
- ActionRead approved baselines from GitHubGitHub
- LogicCompute per-zone compliance and drift details
- ActionPublish dated report page to ConfluenceConfluence
- OutputPost report link and compliance figure to SlackSlack
What it does
Produces a recurring, shareable compliance artifact. It measures how closely your live WAF configuration matches the approved baseline, counts in-sync versus drifted rules per zone, and publishes a dated report page to Confluence for auditors and leadership.
When to use it
Use this when you need evidence for audits (SOC 2, ISO, PCI) showing WAF change control is enforced and tracked over time — not just point-in-time alerts. The Confluence page becomes the record; Slack notifies the team it's ready.
How it works
- 1A weekly schedule starts the report build.
- 2Cloudflare returns WAF rules for each in-scope zone.
- 3A GitHub action reads the approved baseline definitions.
- 4A logic step computes per-zone compliance: total rules, in-sync count, drifted rules with details, and an overall compliance percentage.
- 5A Confluence action publishes a dated report page under the compliance space.
- 6A Slack output posts the report link and the headline compliance figure.
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 ConfluenceSpaces, pages, blueprints.
- 4Connect SlackChannels, DMs, threads, mentions.
- 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.