IT OPS

Cloudflare WAF Change Event → Slack Approval Gate

Receives a Cloudflare audit-log webhook when a WAF rule is edited, checks whether the change matches an open approved change request in GitHub.

CategoryIT Ops
Enginesim
Difficultyadvanced
Triggerwebhook
Steps5
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerCloudflare audit-log webhook on WAF editCloudflareCloudflare
  • ActionFetch full changed rule definitionCloudflareCloudflare
  • ActionSearch GitHub for matching approved change requestGitHubGitHub
  • LogicBranch: approved vs unapproved change
  • OutputPost unapproved-change alert to SlackSlack

What it does

Reacts in near-real-time to WAF edits in Cloudflare. For each rule change event it determines whether a matching approved change request exists in your Git workflow. Changes without an approval get flagged to Slack so an on-call engineer can confirm or revert.

When to use it

Use this when speed matters more than a daily sweep — you want to know within minutes if someone modifies a WAF rule outside the change process, especially during freezes or incident windows.

How it works

  1. 1A Cloudflare audit-log webhook triggers on WAF ruleset modification events.
  2. 2An action enriches the event by fetching the full current rule definition from Cloudflare.
  3. 3A GitHub action searches open/merged PRs and issues for a matching approved change reference.
  4. 4A logic branch splits approved versus unapproved changes.
  5. 5Approved changes are logged silently; unapproved ones continue.
  6. 6A Slack message posts the actor, zone, rule, and diff with approve/revert context to the security channel.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect CloudflareWorkers, Pages, R2, KV — the edge stack.
  2. 2
    Connect GitHubRepos, issues, pull requests, actions.
  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.