IT OPS

Multi-Zone Cloudflare WAF Drift Snapshot → R2 Archive + Slack Digest

Sweeps every Cloudflare zone in the account, snapshots each zone's WAF rules to R2 for an immutable history, diffs against the prior snapshot.

CategoryIT Ops
Enginesim
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerMorning schedule starts multi-zone sweep
  • ActionEnumerate zones and pull WAF rulesCloudflareCloudflare
  • ActionWrite timestamped snapshot to R2CloudflareCloudflare R2
  • LogicDiff today's snapshot against prior R2 snapshot
  • OutputPost consolidated drift digest to SlackSlack

What it does

Builds a tamper-evident change history of your WAF posture across all zones. Each run snapshots current rules to object storage, compares them to the previous snapshot, and rolls up everything that changed into one daily Slack digest instead of per-zone noise.

When to use it

Use this when you operate many Cloudflare zones and need both an audit trail ("what did the WAF look like on June 1?") and a single morning summary of overnight drift across the whole estate.

How it works

  1. 1A morning schedule starts the sweep.
  2. 2The Cloudflare action enumerates all zones and pulls WAF rules for each.
  3. 3An R2 action writes today's snapshot as a timestamped object per zone.
  4. 4A logic step loads the most recent prior snapshot from R2 and diffs zone by zone.
  5. 5Diffs are aggregated into a single digest grouped by zone.
  6. 6A Slack output posts the consolidated digest, linking each zone's snapshot in R2.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect CloudflareWorkers, Pages, R2, KV — the edge stack.
  2. 2
    Connect Cloudflare R2Object storage, S3-compatible.
  3. 3
    Connect SlackChannels, DMs, threads, mentions.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.