HumationHuman + Automation
Back to Catalog

Audit Website Security Headers with AI Remediation and Google Sheets Reporting

Ari NakosAri Nakos
32 views
2/3/2026
GitHubAutomationWebhooksPull RequestDevelopment
Official Page

What It Is

An automated workflow for auditing website security headers and generating comprehensive security reports.

The workflow consists of three main phases:

  1. Perform Security Scan
  2. Save Results in Table
  3. Email Report

Perform Security Scan

This phase analyzes a website's security headers and generates a security grade.

Form Input

A form trigger collects user inputs:

  • Site: The website URL to audit (e.g., example.com)
  • Report Recipient: Email address to receive the security report

URL List & Fetch Headers

  • Prepares the URL for analysis and timestamps the audit
  • Sends an HTTP HEAD request to retrieve security headers
  • Timeout set to 10 seconds for reliable results

Parse Headers & Security Scorer

  • Extracts and normalizes HTTP headers for analysis
  • Evaluates 7 critical security headers:
    • Strict-Transport-Security (HSTS) - HTTPS enforcement
    • Content-Security-Policy (CSP) - XSS protection
    • X-Frame-Options - Clickjacking prevention
    • X-Content-Type-Options - MIME sniffing protection
    • Referrer-Policy - Information leakage control
    • Permissions-Policy - Feature access control
    • Cache-Control - Authentication page caching

Grade Calculator

  • Calculates security score (0-70 points) and assigns letter grade (A-F)
  • Identifies missing headers and configuration issues
  • Flags critical security vulnerabilities

Save Results in Table

This phase exports audit results to a structured Google Sheets database.

Format Report

  • Structures audit data for spreadsheet export
  • Creates checkmark/X indicators for header presence
  • Summarizes issues and security recommendations

Export to Sheets

  • Appends results to Google Sheets for tracking trends
  • Includes timestamp, URL, grade, scores, and detailed findings
  • Supports historical analysis and compliance reporting

Email Report

This phase generates AI-powered remediation instructions and sends detailed security reports.

AI Remediation Agent

  • Uses AI to create copy-paste instructions for non-technical users
  • Generates platform-specific implementation guidance
  • Provides step-by-step remediation for AI code editors (GitHub Copilot, Cursor, etc.)

Email Formatting & Delivery

  • Creates visually rich HTML email reports with:
    • Security grade and score breakdown
    • Missing headers analysis
    • Configuration warnings
    • AI-generated remediation instructions
    • Implementation checklist
  • Sends comprehensive report via Gmail

Setup

To run this workflow, configure the following credentials in n8n:

OpenRouter

  • Generate an API key from your OpenRouter account for AI remediation features

Google Sheets

  • Uses OAuth 2.0 authentication
  • Create a spreadsheet for audit results storage
  • Update the spreadsheet ID in 'Export to Sheets' node

Gmail OAuth2

  • Configure Gmail credentials for automated report delivery
  • Authenticate with your Google account

Audit Website Security Headers with AI Remediation and Google Sheets Reporting

This n8n workflow automates the process of auditing website security headers, generating AI-powered remediation suggestions, and reporting the results to Google Sheets. It's designed to help maintain and improve website security posture efficiently.

What it does

  1. Triggers on Form Submission: The workflow starts when a new website URL is submitted via an n8n form.
  2. Fetches Security Headers: It makes an HTTP request to the submitted website URL to retrieve its security headers.
  3. Evaluates Header Presence: It checks if common security headers (e.g., Strict-Transport-Security, Content-Security-Policy, X-Frame-Options, X-Content-Type-Options) are present in the response.
  4. Generates AI Remediation: For any missing or misconfigured security headers, it uses an AI agent (powered by OpenRouter) to generate detailed remediation instructions.
  5. Formats Remediation Output: The AI-generated remediation steps are formatted into a clear, readable string.
  6. Records to Google Sheets: All audit results, including the website URL, header status, and AI-generated remediation, are appended as a new row in a specified Google Sheet.
  7. Sends Email Notification (Optional): If remediation suggestions are generated, an email is sent with the audit summary and remediation steps.

Prerequisites/Requirements

  • n8n Instance: A running n8n instance to host the workflow.
  • Google Sheets Account: A Google Sheets credential configured in n8n with access to the target spreadsheet.
  • OpenRouter API Key: An OpenRouter credential configured in n8n for the AI agent.
  • Gmail Account (Optional): A Gmail credential configured in n8n if you want to receive email notifications.

Setup/Usage

  1. Import the Workflow:

    • Download the provided JSON file.
    • In your n8n instance, click "Workflows" in the left sidebar, then "New Workflow".
    • Click the three dots menu (...) in the top right corner and select "Import from JSON".
    • Paste the workflow JSON or upload the file.

  2. Configure Credentials:

    • Google Sheets: Locate the "Google Sheets" node (ID: 18). Click on the "Credential" field and select an existing Google Sheets OAuth2 credential or create a new one. Ensure it has write access to your target spreadsheet.
    • OpenRouter Chat Model: Locate the "OpenRouter Chat Model" node (ID: 1281). Click on the "Credential" field and select an existing OpenRouter API Key credential or create a new one.
    • Gmail (Optional): Locate the "Gmail" node (ID: 356). If you wish to receive email notifications, configure a Gmail OAuth2 credential.

  3. Configure Google Sheet:

    • In the "Google Sheets" node, specify the Spreadsheet ID and Sheet Name where you want the audit results to be recorded.
    • Ensure the sheet has columns corresponding to the data being sent (e.g., "URL", "Strict-Transport-Security", "Content-Security-Policy", "X-Frame-Options", "X-Content-Type-Options", "Remediation Suggestions").

  4. Configure n8n Form Trigger:

    • Locate the "On form submission" node (ID: 1225).
    • Activate the workflow by toggling the switch in the top right corner.
    • Click on the "On form submission" node and then "Open Form" to get the URL for submitting website URLs. This form expects a single field, likely named url, containing the website to audit.

  5. Activate the Workflow:

    • Once all credentials and configurations are set, activate the workflow by clicking the "Active" toggle in the top right corner of the n8n editor.

Now, whenever you submit a URL to the n8n form, the workflow will execute, audit the website's security headers, generate AI-powered remediation, and log the results to your Google Sheet.

Related Templates

Track competitor SEO keywords with Decodo + GPT-4.1-mini + Google Sheets

This workflow automates competitor keyword research using OpenAI LLM and Decodo for intelligent web scraping. Who this is for SEO specialists, content strategists, and growth marketers who want to automate keyword research and competitive intelligence. Marketing analysts managing multiple clients or websites who need consistent SEO tracking without manual data pulls. Agencies or automation engineers using Google Sheets as an SEO data dashboard for keyword monitoring and reporting. What problem this workflow solves Tracking competitor keywords manually is slow and inconsistent. Most SEO tools provide limited API access or lack contextual keyword analysis. This workflow solves that by: Automatically scraping any competitor’s webpage with Decodo. Using OpenAI GPT-4.1-mini to interpret keyword intent, density, and semantic focus. Storing structured keyword insights directly in Google Sheets for ongoing tracking and trend analysis. What this workflow does Trigger — Manually start the workflow or schedule it to run periodically. Input Setup — Define the website URL and target country (e.g., https://dev.to, france). Data Scraping (Decodo) — Fetch competitor web content and metadata. Keyword Analysis (OpenAI GPT-4.1-mini) Extract primary and secondary keywords. Identify focus topics and semantic entities. Generate a keyword density summary and SEO strength score. Recommend optimization and internal linking opportunities. Data Structuring — Clean and convert GPT output into JSON format. Data Storage (Google Sheets) — Append structured keyword data to a Google Sheet for long-term tracking. Setup Prerequisites If you are new to Decode, please signup on this link visit.decodo.com n8n account with workflow editor access Decodo API credentials OpenAI API key Google Sheets account connected via OAuth2 Make sure to install the Decodo Community node. Create a Google Sheet Add columns for: primarykeywords, seostrengthscore, keyworddensity_summary, etc. Share with your n8n Google account. Connect Credentials Add credentials for: Decodo API credentials - You need to register, login and obtain the Basic Authentication Token via Decodo Dashboard OpenAI API (for GPT-4o-mini) Google Sheets OAuth2 Configure Input Fields Edit the “Set Input Fields” node to set your target site and region. Run the Workflow Click Execute Workflow in n8n. View structured results in your connected Google Sheet. How to customize this workflow Track Multiple Competitors → Use a Google Sheet or CSV list of URLs; loop through them using the Split In Batches node. Add Language Detection → Add a Gemini or GPT node before keyword analysis to detect content language and adjust prompts. Enhance the SEO Report → Expand the GPT prompt to include backlink insights, metadata optimization, or readability checks. Integrate Visualization → Connect your Google Sheet to Looker Studio for SEO performance dashboards. Schedule Auto-Runs → Use the Cron Node to run weekly or monthly for competitor keyword refreshes. Summary This workflow automates competitor keyword research using: Decodo for intelligent web scraping OpenAI GPT-4.1-mini for keyword and SEO analysis Google Sheets for live tracking and reporting It’s a complete AI-powered SEO intelligence pipeline ideal for teams that want actionable insights on keyword gaps, optimization opportunities, and content focus trends, without relying on expensive SEO SaaS tools.

Ranjan DailataBy Ranjan Dailata
161

Generate song lyrics and music from text prompts using OpenAI and Fal.ai Minimax

Spark your creativity instantly in any chat—turn a simple prompt like "heartbreak ballad" into original, full-length lyrics and a professional AI-generated music track, all without leaving your conversation. 📋 What This Template Does This chat-triggered workflow harnesses AI to generate detailed, genre-matched song lyrics (at least 600 characters) from user messages, then queues them for music synthesis via Fal.ai's minimax-music model. It polls asynchronously until the track is ready, delivering lyrics and audio URL back in chat. Crafts original, structured lyrics with verses, choruses, and bridges using OpenAI Submits to Fal.ai for melody, instrumentation, and vocals aligned to the style Handles long-running generations with smart looping and status checks Returns complete song package (lyrics + audio link) for seamless sharing 🔧 Prerequisites n8n account (self-hosted or cloud with chat integration enabled) OpenAI account with API access for GPT models Fal.ai account for AI music generation 🔑 Required Credentials OpenAI API Setup Go to platform.openai.com → API keys (sidebar) Click "Create new secret key" → Name it (e.g., "n8n Songwriter") Copy the key and add to n8n as "OpenAI API" credential type Test by sending a simple chat completion request Fal.ai HTTP Header Auth Setup Sign up at fal.ai → Dashboard → API Keys Generate a new API key → Copy it In n8n, create "HTTP Header Auth" credential: Name="Fal.ai", Header Name="Authorization", Header Value="Key [Your API Key]" Test with a simple GET to their queue endpoint (e.g., /status) ⚙️ Configuration Steps Import the workflow JSON into your n8n instance Assign OpenAI API credentials to the "OpenAI Chat Model" node Assign Fal.ai HTTP Header Auth to the "Generate Music Track", "Check Generation Status", and "Fetch Final Result" nodes Activate the workflow—chat trigger will appear in your n8n chat interface Test by messaging: "Create an upbeat pop song about road trips" 🎯 Use Cases Content Creators: YouTubers generating custom jingles for videos on the fly, streamlining production from idea to audio export Educators: Music teachers using chat prompts to create era-specific folk tunes for classroom discussions, fostering interactive learning Gift Personalization: Friends crafting anniversary R&B tracks from shared memories via quick chats, delivering emotional audio surprises Artist Brainstorming: Songwriters prototyping hip-hop beats in real-time during sessions, accelerating collaboration and iteration ⚠️ Troubleshooting Invalid JSON from AI Agent: Ensure the system prompt stresses valid JSON; test the agent standalone with a sample query Music Generation Fails (401/403): Verify Fal.ai API key has minimax-music access; check usage quotas in dashboard Status Polling Loops Indefinitely: Bump wait time to 45-60s for complex tracks; inspect fal.ai queue logs for bottlenecks Lyrics Under 600 Characters: Tweak agent prompt to enforce fuller structures like [V1][C][V2][B][C]; verify output length in executions

Daniel NkenchoBy Daniel Nkencho
601

Automate invoice processing with OCR, GPT-4 & Salesforce opportunity creation

PDF Invoice Extractor (AI) End-to-end pipeline: Watch Drive ➜ Download PDF ➜ OCR text ➜ AI normalize to JSON ➜ Upsert Buyer (Account) ➜ Create Opportunity ➜ Map Products ➜ Create OLI via Composite API ➜ Archive to OneDrive. --- Node by node (what it does & key setup) 1) Google Drive Trigger Purpose: Fire when a new file appears in a specific Google Drive folder. Key settings: Event: fileCreated Folder ID: google drive folder id Polling: everyMinute Creds: googleDriveOAuth2Api Output: Metadata { id, name, ... } for the new file. --- 2) Download File From Google Purpose: Get the file binary for processing and archiving. Key settings: Operation: download File ID: ={{ $json.id }} Creds: googleDriveOAuth2Api Output: Binary (default key: data) and original metadata. --- 3) Extract from File Purpose: Extract text from PDF (OCR as needed) for AI parsing. Key settings: Operation: pdf OCR: enable for scanned PDFs (in options) Output: JSON with OCR text at {{ $json.text }}. --- 4) Message a model (AI JSON Extractor) Purpose: Convert OCR text into strict normalized JSON array (invoice schema). Key settings: Node: @n8n/n8n-nodes-langchain.openAi Model: gpt-4.1 (or gpt-4.1-mini) Message role: system (the strict prompt; references {{ $json.text }}) jsonOutput: true Creds: openAiApi Output (per item): $.message.content → the parsed JSON (ensure it’s an array). --- 5) Create or update an account (Salesforce) Purpose: Upsert Buyer as Account using an external ID. Key settings: Resource: account Operation: upsert External Id Field: taxid_c External Id Value: ={{ $json.message.content.buyer.tax_id }} Name: ={{ $json.message.content.buyer.name }} Creds: salesforceOAuth2Api Output: Account record (captures Id) for downstream Opportunity. --- 6) Create an opportunity (Salesforce) Purpose: Create Opportunity linked to the Buyer (Account). Key settings: Resource: opportunity Name: ={{ $('Message a model').item.json.message.content.invoice.code }} Close Date: ={{ $('Message a model').item.json.message.content.invoice.issue_date }} Stage: Closed Won Amount: ={{ $('Message a model').item.json.message.content.summary.grand_total }} AccountId: ={{ $json.id }} (from Upsert Account output) Creds: salesforceOAuth2Api Output: Opportunity Id for OLI creation. --- 7) Build SOQL (Code / JS) Purpose: Collect unique product codes from AI JSON and build a SOQL query for PricebookEntry by Pricebook2Id. Key settings: pricebook2Id (hardcoded in script): e.g., 01sxxxxxxxxxxxxxxx Source lines: $('Message a model').first().json.message.content.products Output: { soql, codes } --- 8) Query PricebookEntries (Salesforce) Purpose: Fetch PricebookEntry.Id for each Product2.ProductCode. Key settings: Resource: search Query: ={{ $json.soql }} Creds: salesforceOAuth2Api Output: Items with Id, Product2.ProductCode (used for mapping). --- 9) Code in JavaScript (Build OLI payloads) Purpose: Join lines with PBE results and Opportunity Id ➜ build OpportunityLineItem payloads. Inputs: OpportunityId: ={{ $('Create an opportunity').first().json.id }} Lines: ={{ $('Message a model').first().json.message.content.products }} PBE rows: from previous node items Output: { body: { allOrNone:false, records:[{ OpportunityLineItem... }] } } Notes: Converts discount_total ➜ per-unit if needed (currently commented for standard pricing). Throws on missing PBE mapping or empty lines. --- 10) Create Opportunity Line Items (HTTP Request) Purpose: Bulk create OLIs via Salesforce Composite API. Key settings: Method: POST URL: https://<your-instance>.my.salesforce.com/services/data/v65.0/composite/sobjects Auth: salesforceOAuth2Api (predefined credential) Body (JSON): ={{ $json.body }} Output: Composite API results (per-record statuses). --- 11) Update File to One Drive Purpose: Archive the original PDF in OneDrive. Key settings: Operation: upload File Name: ={{ $json.name }} Parent Folder ID: onedrive folder id Binary Data: true (from the Download node) Creds: microsoftOneDriveOAuth2Api Output: Uploaded file metadata. --- Data flow (wiring) Google Drive Trigger → Download File From Google Download File From Google → Extract from File → Update File to One Drive Extract from File → Message a model Message a model → Create or update an account Create or update an account → Create an opportunity Create an opportunity → Build SOQL Build SOQL → Query PricebookEntries Query PricebookEntries → Code in JavaScript Code in JavaScript → Create Opportunity Line Items --- Quick setup checklist 🔐 Credentials: Connect Google Drive, OneDrive, Salesforce, OpenAI. 📂 IDs: Drive Folder ID (watch) OneDrive Parent Folder ID (archive) Salesforce Pricebook2Id (in the JS SOQL builder) 🧠 AI Prompt: Use the strict system prompt; jsonOutput = true. 🧾 Field mappings: Buyer tax id/name → Account upsert fields Invoice code/date/amount → Opportunity fields Product name must equal your Product2.ProductCode in SF. ✅ Test: Drop a sample PDF → verify: AI returns array JSON only Account/Opportunity created OLI records created PDF archived to OneDrive --- Notes & best practices If PDFs are scans, enable OCR in Extract from File. If AI returns non-JSON, keep “Return only a JSON array” as the last line of the prompt and keep jsonOutput enabled. Consider adding validation on parsing.warnings to gate Salesforce writes. For discounts/taxes in OLI: Standard OLI fields don’t support per-line discount amounts directly; model them in UnitPrice or custom fields. Replace the Composite API URL with your org’s domain or use the Salesforce node’s Bulk Upsert for simplicity.

Le NguyenBy Le Nguyen
942