Gate deployments on WAF scan results with WAFtester
Ready for 3.0Ready for 3.0. This template uses no nodes that n8n 3.0 removes. No removed nodes, versions or helpers found. Static check, last run 2026-10-19.
What this workflow does
This workflow has 9 nodes and runs when an HTTP POST request hits its webhook URL. It uses only n8n's built-in nodes.
How it runs
Trigger: When an HTTP POST request hits its webhook URL.
- Detect WAF (HTTP Request): calls an HTTP API (POST)
- Start Scan (HTTP Request): calls an HTTP API (POST)
- Wait: waits 30 seconds
- Poll Task Status (HTTP Request): calls an HTTP API (POST)
- Parse Results (Code): runs custom JavaScript code
- Pass or Fail? (If): checks a condition and branches into true / false
- Respond Pass (Respond to Webhook): sends the response back to the webhook caller
- Respond Fail (Respond to Webhook): sends the response back to the webhook caller
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (6)
- Webhook
n8n-nodes-base.webhook - HTTP Request
n8n-nodes-base.httpRequest - Wait
n8n-nodes-base.wait - Code
n8n-nodes-base.code - If
n8n-nodes-base.if - Respond to Webhook
n8n-nodes-base.respondToWebhook
From the author
What it does A CI/CD quality gate that blocks deployments when WAF protection is insufficient. Your pipeline sends a webhook with the target URL, the workflow runs WAFtester scans, and returns a pass/fail HTTP response the pipeline can gate on. About…