IT OPS

Cloudflare WAF Change Slack Approval Gate

Intercepts every proposed Cloudflare WAF ruleset edit, posts a diff to Slack for human sign-off, and only pushes the change to Cloudflare after an approver clicks Approve.

CategoryIT Ops
Enginesim
Difficultyintermediate
Triggerwebhook
Steps6
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerProposed WAF rule change receivedHTTP webhook
  • LogicFetch current ruleset and compute diffCloudflareCloudflare
  • ActionPost diff to Slack with Approve/Reject buttonsSlack
  • LogicWait for approval decision and branch
  • ActionApply ruleset update to CloudflareCloudflareCloudflare
  • OutputPost final result to Slack threadSlack

What it does

This workflow puts a human approval gate in front of Cloudflare WAF custom ruleset changes. When a proposed rule edit arrives via webhook, it renders a readable before/after diff, posts it to a Slack approvals channel with Approve/Reject buttons, and blocks the actual Cloudflare write until someone signs off.

When to use it

Use it when your team edits WAF rules directly in the dashboard or via API and you want a paper trail plus a second pair of eyes before anything touches production traffic. Ideal for teams under change-management or SOC 2 controls.

How it works

  1. 1A webhook receives the proposed ruleset payload (zone, ruleset ID, new expression).
  2. 2A logic step fetches the current ruleset from Cloudflare and computes a field-level diff.
  3. 3The diff and risk notes are posted to Slack with interactive Approve/Reject buttons.
  4. 4A logic gate waits for the button response and branches.
  5. 5On approval, the workflow calls Cloudflare to apply the ruleset update.
  6. 6The final outcome (applied or rejected, with the approver name) is posted back to the Slack thread.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect HTTP webhookTrigger any URL on agent actions.
  2. 2
    Connect CloudflareWorkers, Pages, R2, KV — the edge stack.
  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.