Audit website security and send AI reports via Claude, Gmail, Slack and WhatsApp

Workflow preview

100%

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

Who it's for This advanced n8n workflow is designed for web developers , system administrators , security analysts , and agency owners who need to automate the monitoring of website security postur...

Best for

SecOps automation workflows
AI Summarization automation workflows
advanced n8n builders looking for reusable templates

Tools used

n8n-nodes-base.httprequest, n8n-nodes-base.aggregate, n8n-nodes-base.gmail, n8n-nodes-base.scheduletrigger, n8n-nodes-base.googlesheets, n8n-nodes-base.converttofile, n8n-nodes-base.splitinbatches, n8n-nodes-base.slack

Source and attribution

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

Original n8n.io source

1.1 Workflow description

Title: Audit website security and send AI reports via Claude, Gmail, Slack and WhatsApp
Workflow name: Audit website security and send AI reports via Claude, Gmail, Slack and WhatsApp

Who it's for

This advanced n8n workflow is designed for web developers, system administrators, security analysts, and agency owners who need to automate the monitoring of website security posture. It acts as a virtual security auditor, automatically scanning webpages for security misconfigurations, analyzing headers, and identifying potential client-side vulnerabilities using advanced AI.

Features

Multi-Source Triggering: Supports three different input methods—Manual execution, scheduled scans from Google Sheets, or on-demand checks via a Form Trigger.
Deep Security Analysis: Uses LangChain Agents (powered by Anthropic/Claude) to audit both HTTP headers (Config Audit) and HTML content (Vulnerability Audit) for security flaws.
Smart Grading System: Automatically calculates a security grade (A+ to F) based on the presence and configuration of critical security headers like CSP, HSTS, and X-Frame-Options.
AI-Generated Reporting: Creates a detailed, professional HTML report highlighting critical vulnerabilities, information leakage, and configuration warnings with specific fix recommendations.
Automated Notifications: Sends the final security report via Gmail (as an attached file), Slack, and WhatsApp simultaneously.
Sheet Integration: When triggered by a schedule, it reads URLs from a Google Sheet and updates the sheet with the audit status upon completion.

Requirements

Anthropic API: A valid API key (configured in the "Anthropic Chat Model" node) is required for the LangChain Agents to analyze security data and generate insights.
Gmail & Google Sheets: Google OAuth2 credentials are needed to send the audit report via email and manage the list of websites to be audited.
Slack API: OAuth2 credentials are required to send security status notifications to a Slack channel.
Rapiwa (WhatsApp): API credentials to send the audit summary via WhatsApp messages.

Important Notes

Manual Input: If using the "Clicking Trigger" or "Form Trigger", ensure the URL is provided in the Landing Page Url field.
Sheet Setup: For scheduled scans, ensure your Google Sheet contains columns for Links, Check, and SL.
Cost Management: Using advanced AI models (like Claude) for extensive HTML and Header analysis can consume significant tokens depending on the size of the webpage.
Safety First: This tool performs client-side analysis. For a complete penetration test, always engage a professional security professional.

Support & Help

WhatsApp: Chat on WhatsApp
Discord: SpaGreen Community
Facebook Group: SpaGreen Support
Website: spagreen.net
Developer Portfolio: Codecanyon SpaGreen

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 - Scrape Website

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

Block 2 - Aggregate Audit Results

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

Block 3 - Send Security Report

Type / Role: n8n-nodes-base.gmail - gmail
Config choices: Version 2.1

Block 4 - Schedule Trigger

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

Block 5 - Get row(s) in sheet

Type / Role: n8n-nodes-base.googleSheets - googleSheets
Config choices: Version 4.7

Block 6 - Convert to File

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

Block 7 - Scrape Website1

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

Block 8 - Loop Over Items

Type / Role: n8n-nodes-base.splitInBatches - splitInBatches
Config choices: Version 3

Block 9 - Send a message

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

Block 10 - Edit Fields

Type / Role: n8n-nodes-base.set - set
Config choices: Version 3.4

Block 11 - Scrape Website2

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

Block 12 - Sticky Note

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

Block 13 - Sticky Note1

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

Block 14 - Clicking Trigger

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

Block 15 - Sticky Note2

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

Block 16 - Form Trigger

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

Block 17 - Sticky Note3

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

Block 18 - Sticky Note4

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

Block 19 - Sticky Note5

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

Block 20 - Website Security Vulnerabilities Audit

Type / Role: @n8n/n8n-nodes-langchain.agent - agent
Config choices: Version 1.7

Block 21 - Website Security Configur Audit

Type / Role: @n8n/n8n-nodes-langchain.agent - agent
Config choices: Version 1.7

Block 22 - Code (Extract Headers for Debuging)

Type / Role: n8n-nodes-base.code - code
Config choices: Version 2

Block 23 - Anthropic Chat Model

Type / Role: @n8n/n8n-nodes-langchain.lmChatAnthropic - lmChatAnthropic
Config choices: Version 1.3

Block 24 - Message a model in Anthropic

Type / Role: @n8n/n8n-nodes-langchain.anthropicTool - anthropicTool
Config choices: Version 1

Showing the first 24 of 32 workflow blocks. Download the JSON for the full node graph.

3. Summary Table

Workflow	Audit website security and send AI reports via Claude, Gmail, Slack and WhatsApp
Complexity	advanced
Nodes	32
Categories	SecOps, AI Summarization
Author	SpaGreen Creative
Published	21 May 2026

4. Reproducing the Workflow from Scratch

1. Download the workflow JSON

Use the JSON export at /data/workflows/15871/15871.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 AI Summarization workflows

Frequently asked questions

What does Audit website security and send AI reports via Claude, Gmail, Slack and WhatsApp 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, AI Summarization use case.

SpaGreen Creative

60 workflows

Nodes

n8n-nodes-base.httprequest n8n-nodes-base.aggregate n8n-nodes-base.gmail n8n-nodes-base.scheduletrigger n8n-nodes-base.googlesheets n8n-nodes-base.converttofile n8n-nodes-base.splitinbatches n8n-nodes-base.slack

Complexity

advanced

Published 21 May 2026

Likes 0

View on n8n.io Download Workflow

Install path: /data/workflows/15871/15871.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.

Audit website security and send AI reports via Claude, Gmail, Slack and WhatsApp

Workflow preview

1. Workflow Overview

Best for

Tools used

Source and attribution

1.1 Workflow description

Who it's for

Features

Requirements

Important Notes

Support & Help

1.2 Logical Blocks

2. Block-by-Block Analysis

Block 1 - Scrape Website

Block 2 - Aggregate Audit Results

Block 3 - Send Security Report

Block 4 - Schedule Trigger

Block 5 - Get row(s) in sheet

Block 6 - Convert to File

Block 7 - Scrape Website1

Block 8 - Loop Over Items

Block 9 - Send a message

Block 10 - Edit Fields

Block 11 - Scrape Website2

Block 12 - Sticky Note

Block 13 - Sticky Note1

Block 14 - Clicking Trigger

Block 15 - Sticky Note2

Block 16 - Form Trigger

Block 17 - Sticky Note3

Block 18 - Sticky Note4

Block 19 - Sticky Note5

Block 20 - Website Security Vulnerabilities Audit

Block 21 - Website Security Configur Audit

Block 22 - Code (Extract Headers for Debuging)

Block 23 - Anthropic Chat Model

Block 24 - Message a model in Anthropic

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