Run weekly WAF security audits with WAFtester and Slack alerts

Open on n8n.io

$20/month : Unlimited workflows

2500 executions/month

Try free

THE #1 IN WEB SCRAPING

Scrape any website without limits

Try free

HOSTINGER

Early Deal
DISCOUNT 20%

Self-hosted n8n

Unlimited workflows - from $4.99/mo

Try free

#1 hub for scraping, AI & automation

6000+ actors - $5 credits/mo

Try free

1. Workflow Overview

What it does Automated weekly WAF security assessments with Slack reporting. Detects your WAF vendor, runs a security assessment, grades your protection, and alerts your team when the grade drops b...

Best for

SecOps automation workflows
intermediate n8n builders looking for reusable templates

Tools used

n8n-nodes-base.scheduletrigger, n8n-nodes-base.httprequest, n8n-nodes-base.wait, n8n-nodes-base.if, n8n-nodes-base.slack, n8n-nodes-base.stickynote

Source and attribution

This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Qandil.

Original n8n.io source

1.1 Workflow description

Title: Run weekly WAF security audits with WAFtester and Slack alerts
Workflow name: Run weekly WAF security audits with WAFtester and Slack alerts

What it does

Automated weekly WAF security assessments with Slack reporting. Detects your WAF vendor, runs a security assessment, grades your protection, and alerts your team when the grade drops below threshold.

About WAFtester

WAFtester is an open-source CLI for testing Web Application Firewalls. It ships 27 MCP tools, 2,800+ attack payloads across 18 categories (SQLi, XSS, SSRF, SSTI, command injection, XXE, and more), detection signatures for 26 WAF vendors and 9 CDNs, and enterprise-grade assessment with F1/MCC scoring and letter grades (A+ through F).

GitHub: github.com/waftester/waftester
Docs: Installation | Examples | Commands

Who it's for

Security teams needing continuous WAF monitoring
DevOps engineers tracking WAF configuration drift
Compliance teams requiring regular security assessments

How it works

The workflow has seven nodes:

Weekly Schedule — Triggers every Monday at 3 AM (configurable)
Detect WAF — Calls WAFtester's detect_waf tool to fingerprint the WAF vendor and CDN
Start Assessment — Launches an async assess task testing SQLi, XSS, traversal, cmdi, and SSRF
Wait — Pauses to let the assessment run
Poll Results — Calls get_task_status to retrieve completed results
Check Results — Routes based on the WAF grade (pass if "A" or better, fail otherwise)
Slack (Pass/Fail) — Posts a summary to your Slack channel with grade, detection rate, and bypass count

How to set up

Start WAFtester MCP server: docker run -p 8080:8080 ghcr.io/waftester/waftester:latest mcp --http :8080
Set environment variables: WAF_TARGET_URL (required), WAFTESTER_MCP_URL, SLACK_CHANNEL
Add Slack OAuth2 credentials and select them in both Slack nodes
Activate the workflow

Alternatively, use the included docker-compose.yml to run both n8n and WAFtester together.

Requirements

Requirement	Details
WAFtester MCP server	Docker image (`ghcr.io/waftester/waftester:latest`) or binary install
Slack	Workspace with OAuth2 bot credentials
Authorization	Only test targets you have explicit written permission to test

How to customize

Adjust schedule in the Weekly Schedule node
Change grade threshold in the Check Results node
Add attack categories in Start Assessment's categories array
Swap Slack for email, Teams, or any n8n notification node

1.2 Logical Blocks

This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.

2. Block-by-Block Analysis

Block 1 - Weekly Schedule

Type / Role: n8n-nodes-base.scheduleTrigger - scheduleTrigger
Config choices: Version 1.2

Block 2 - Detect WAF

Type / Role: n8n-nodes-base.httpRequest - httpRequest
Config choices: Version 4.2

Block 3 - Start Assessment

Type / Role: n8n-nodes-base.httpRequest - httpRequest
Config choices: Version 4.2

Block 4 - Wait for Assessment

Type / Role: n8n-nodes-base.wait - wait
Config choices: Version 1.1

Block 5 - Poll Task Status

Type / Role: n8n-nodes-base.httpRequest - httpRequest
Config choices: Version 4.2

Block 6 - Check Results

Type / Role: n8n-nodes-base.if - if
Config choices: Version 2.2

Block 7 - Slack Alert

Type / Role: n8n-nodes-base.slack - slack
Config choices: Version 2.2

Block 8 - Slack OK

Type / Role: n8n-nodes-base.slack - slack
Config choices: Version 2.2

Block 9 - Sticky Note

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Block 10 - Sticky Note1

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Block 11 - Sticky Note2

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

3. Summary Table

Workflow	Run weekly WAF security audits with WAFtester and Slack alerts
Complexity	intermediate
Nodes	11
Categories	SecOps
Author	Qandil
Published	16 Feb 2026

4. Reproducing the Workflow from Scratch

1. Download the workflow JSON

Use the JSON export at /data/workflows/13444/13444.json as the source template for this automation.
2. Import the template into n8n

Open n8n, import the downloaded JSON, and review each node before activating the workflow.
3. Configure credentials and variables

Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
4. Test with sample data

Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
5. Activate and monitor

Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.

5. General Notes & Resources

Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.

Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.

Download workflow JSON Original n8n.io source SecOps workflows

Frequently asked questions

What does Run weekly WAF security audits with WAFtester and Slack alerts do?

What do I need before importing this workflow?

Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.

Can I customize this workflow?

Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your SecOps use case.

Qandil

3 workflows

Nodes

n8n-nodes-base.scheduletrigger n8n-nodes-base.httprequest n8n-nodes-base.wait n8n-nodes-base.if n8n-nodes-base.slack n8n-nodes-base.stickynote

Complexity

intermediate

Published 16 Feb 2026

Likes 0

View on n8n.io Download Workflow

Install path: /data/workflows/13444/13444.json

Share Your Workflow

Have a useful automation to share? Publish it and help the community.

Submit Your Template How to Submit

Related Workflows

Generate incident response reports with Supabase, Gemini and Claude

## Quick Overview This workflow ingests incident and playbook content from GitHub into Supabase (including pgvector embeddings with Google Gemini) and, on a webhook trigger, enriches a test incident with historical matches, a routed response playbook, and live web threat intel (via Tavily + OpenRouter) to generate a validated incident response report. ## How it works 1. Receives a POST webhook containing the incident payload (including an encrypted OpenRouter API key) and decrypts the key for downstream LLM calls. 2. Creates a tracking row in a Supabase table and loads configuration values used by the retrieval and report-generation steps. 3. Retrieves similar resolved incidents from a Supabase pgvector store using Google Gemini embeddings and returns structured historical patterns. 4. Retrieves the best-matching reference playbook from a Supabase pgvector store and fetches the full playbook text from Supabase, falling back to a built-in generic playbook when no match is found. 5. Uses Tavily Search plus an OpenRouter-backed agent to gather external threat intelligence, IOCs, and phased mitigation guidance when the incident is classified as security-relevant. 6. Merges the three intelligence branches and uses an OpenRouter LLM to synthesize a structured JSON output and an 11-section Markdown incident response report. 7. Validates that required report fields exist and, if valid, writes the structured output and Markdown report back to the Supabase test incident record; otherwise it skips the write. ## Setup 1. Create Supabase tables for test incidents and vector stores (for resolved incidents and reference playbooks) and configure the matching SQL functions used for retrieval (for example, `match_resolved_incidents_v1` and `match_reference_playbooks_v1`). 2. Add Supabase credentials in n8n and set the correct table names and query function names in the workflow’s configuration nodes. 3. Add Google Gemini (PaLM) API credentials and ensure the embedding model name used in the config (for example, `models/gemini-embedding-001`) is available to your account. 4. Add an OpenRouter API credential for the chat models used by the agents and synthesizer, and ensure your webhook caller sends an `encrypted_openrouter_key` value that matches the workflow’s decryption format. 5. Add a Tavily API credential for web search, then copy the webhook URL and configure your incident source to POST the incident JSON to it.

View

Check JWT security of API endpoints with HTTP requests and Google Sheets

## Quick Overview This workflow reads API endpoints and JWTs from Google Sheets, tests each endpoint with multiple token scenarios using HTTP requests, and writes a risk-scored security summary back to Google Sheets. ## How it works 1. Triggers manually (or on an optional daily schedule). 2. Loads the target Google Sheets document ID and the endpoint/results tab names. 3. Reads endpoint definitions from Google Sheets and keeps only rows marked as active. 4. For each endpoint, decodes the provided JWT and generates test variants (no auth, tampered payload, and alg:none). 5. Sends HTTP requests to the endpoint using the valid token and, if that succeeds, repeats the request with each test token variant and captures the response status codes. 6. Evaluates the status codes and token metadata to flag issues (for example, unauthenticated access, tampered token acceptance, alg:none acceptance, or missing exp) and assigns a risk level. 7. Appends the timestamped results and summary to the results tab in Google Sheets. ## Setup 1. Create a Google Sheet with an endpoints tab containing columns like `label`, `endpoint_url`, `method`, `token`, and `active`, and a results tab with columns like `timestamp`, `label`, `risk_level`, `t1_valid`, `t2_no_auth`, `t3_tampered`, `t4_alg_none`, and `summary`. 2. Add a Google Sheets Service Account credential in n8n and share the spreadsheet with the service account email. 3. Update the Sheet ID and tab names in the workflow’s variables (Sheet ID, endpoints sheet name, and results sheet name). 4. Ensure each endpoint row includes a valid JWT in the `token` column and set `active` to TRUE for endpoints you want to test. 5. If you want it to run automatically, enable the schedule trigger and adjust the cron expression as needed.

View

Monitor SSL certificate expiry with Google Sheets, Slack, Gmail and Jira

## Quick Overview This workflow runs daily to check SSL certificate expiry for domains listed in Google Sheets, using ssl-checker.io to fetch certificate details, then creating Jira issues and sending Slack and Gmail alerts for risky certificates while logging results and posting a daily Slack digest. ## How it works 1. Runs every day at 08:00 on a schedule trigger. 2. Reads the domain list from a Google Sheets “Domains” sheet and filters out blank rows or domains marked as disabled. 3. Processes domains one by one, calling the ssl-checker.io API to retrieve each site’s live SSL certificate details. 4. Calculates days remaining until expiry, assigns a status (Expired, Critical, Warning, Healthy, or Unknown), and flags items that require attention. 5. For certificates that need attention, creates a Jira task and sends an alert to Slack and an email via Gmail with the certificate details. 6. For healthy certificates, writes the latest check results to a Google Sheets “Log” sheet. 7. Aggregates all results from the run into a single summary message and posts the daily digest to Slack. ## Setup 1. Create a Google Sheet with a “Domains” sheet containing at least a `domain` column (and optionally an `enabled` column) and a “Log” sheet to store results, then add your Google Sheets credentials and set the spreadsheet ID. 2. Add an API key for ssl-checker.io (or a compatible SSL lookup endpoint) and place it in the HTTP Authorization header. 3. Add your Jira credentials and set the target project key for ticket creation. 4. Add your Slack credentials and set the channel ID used for alerts and the daily digest. 5. Add your Gmail credentials and set the recipient address for email alerts. 6. (Optional) Adjust the warning and critical thresholds (30 and 7 days) in the expiry calculation code if your policy differs.

View

Need Custom Automation?

Get help designing a custom n8n workflow that connects your stack and fits your process.

Run weekly WAF security audits with WAFtester and Slack alerts

Workflow preview

1. Workflow Overview

Best for

Tools used

Source and attribution

1.1 Workflow description

What it does

About WAFtester

Who it's for

How it works

How to set up

Requirements

How to customize

Links

1.2 Logical Blocks

2. Block-by-Block Analysis

Block 1 - Weekly Schedule

Block 2 - Detect WAF

Block 3 - Start Assessment

Block 4 - Wait for Assessment

Block 5 - Poll Task Status

Block 6 - Check Results

Block 7 - Slack Alert

Block 8 - Slack OK

Block 9 - Sticky Note

Block 10 - Sticky Note1

Block 11 - Sticky Note2

3. Summary Table

4. Reproducing the Workflow from Scratch

1. Download the workflow JSON

2. Import the template into n8n

3. Configure credentials and variables

4. Test with sample data

5. Activate and monitor

5. General Notes & Resources

Frequently asked questions