Automated weekly security audit reports with Gmail delivery
🔒 N8N Security Audit Report - Automated Weekly Email
🎯 What does this workflow do?
This workflow automatically generates and emails a comprehensive security audit report for your N8N instance every week. It identifies potential security risks related to:
- Credentials 🔑 : Exposed or insecure credentials
- Nodes 🧩 : Sensitive nodes (Code, HTTP Request, SSH, FTP, etc.)
- Instance settings 🏢 : Global security configuration
- Community nodes 📦 : Third-party nodes that may pose risks
The report includes direct links to affected workflows, execution statuses, and actionable recommendations.
✨ Key Features
📊 Smart Risk Assessment
- Calculates overall risk level: 🟩 Low / 🟧 Moderate / 🟥 High
- Tracks unique credentials (not just total occurrences)
- Provides detailed breakdown by node type
🔗 Direct Workflow Links
- Clickable links to each workflow mentioned
- Shows last execution status (🟢 success / 🔴 failed)
- Displays execution timestamps
🌍 Bilingual Support
- Full support for French and English
- Switch language with a single variable
📧 Beautiful HTML Email
- Clean, professional formatting
- Color-coded risk levels
- Emoji icons for easy scanning
🚀 Quick Setup (5 minutes)
1️⃣ Configure Credentials
- N8N API: Generate an API key in your N8N settings
- Gmail OAuth2: Set up OAuth2 for Gmail sending
2️⃣ Set Your Variables
Edit the "Set Config Variables" node:
{
"email_to": "your.email@domain.com",
"project_name": "My-N8N-Project",
"server_url": "https://n8n.yourdomain.com", // NO trailing slash!
"Language": "EN" // or "FR"
}
3️⃣ Test & Activate
- Click "Execute Workflow" to test
- Check your email inbox
- Activate for weekly automation
📧 Example Report Output
Subject: 🔒 Audit Report My-Project – Risk 🟧 Moderate
Content:
📊 Summary
• Credentials involved: 8 (5 unique)
• Nodes involved: 12
- 💻 code: 4
- 🌐 httpRequest: 3
- 🔐 ssh: 2
• Community nodes: 1
• Overall risk level: 🟧 Moderate
🔐 Credentials Risk Report
🔹 Credentials with full access
- 🔑 My AWS Credentials
- 🔑 Database Admin
📋 Workflow: Data Processing Pipeline 🟢 (25-10-2024 06:15 → 06:16)
- 💻 Process Data
- 🌐 API Call
🧩 Nodes Risk Report
[...detailed node analysis...]
🎨 Customization Options
Change Schedule
Modify the "Schedule Trigger" node to run:
- Daily at 8 AM
- Monthly on the 1st
- Custom cron expression
Add Recipients
Add multiple emails in the Gmail node's toList parameter
Adjust Risk Thresholds
Edit the JavaScript in "Format Audit Report" nodes to customize when risk levels change
Use Different Email Service
Replace Gmail node with:
- SMTP
- Microsoft Outlook
- SendGrid
- Any email service N8N supports
💡 Use Cases
✅ Compliance Monitoring: Track security posture for audits
✅ Team Awareness: Keep your team informed of security status
✅ Change Detection: Notice when new risky nodes are added
✅ Best Practices: Get recommendations to improve security
✅ Multi-Environment: Run separate instances for dev/staging/prod
🔧 Technical Details
Nodes Used: 8
Credentials Required: 2 (N8N API + Gmail OAuth2)
External Dependencies: None
N8N Version: Compatible with latest N8N versions
Execution Time: ~10-20 seconds
📋 Requirements
- N8N instance with API access
- Gmail account (or other email service)
- N8N API key with audit permissions
- Valid SSL certificate for workflow links (recommended)
🐛 Troubleshooting
Empty report?
→ Check your N8N API key has audit permissions
Workflow links don't work?
→ Verify server_url is correct and has no trailing slash
No execution status shown?
→ Workflows must have been executed at least once
Wrong language displayed?
→ Set Language to exactly "FR" or "EN" (uppercase)
🌟 Why This Template?
Unlike basic monitoring tools, this workflow:
- ✅ Provides context-aware security analysis
- ✅ Links directly to affected workflows
- ✅ Shows real execution data (not just theoretical risks)
- ✅ Calculates unique credential exposure (not just counts)
- ✅ Supports bilingual reports
- ✅ Delivers actionable recommendations
🤝 Feedback & Support
Found this helpful? Please rate the template!
Have suggestions? Drop a comment below.
Pro tip: Combine this with N8N's native alerting for real-time incident response!
Tags: #security #audit #monitoring #compliance #automation #email #reporting #credentials #governance
📜 License
MIT - Feel free to modify and share!
Automated Weekly Security Audit Reports with Gmail Delivery
This n8n workflow automates the generation and delivery of weekly security audit reports via Gmail. It's designed to ensure that critical security information is regularly compiled and sent to the relevant stakeholders without manual intervention.
What it does
This workflow simplifies the process of creating and distributing weekly security audit reports by:
- Triggering Weekly: The workflow is scheduled to run periodically, likely once a week, to initiate the report generation process.
- Conditional Execution: It includes a conditional check (If node) which could be used to determine if a report needs to be generated or if certain conditions are met before proceeding. (Note: The specific condition is not defined in the provided JSON, but the presence of the If node indicates this capability).
- Preparing Report Data: An "Edit Fields (Set)" node is present, suggesting that it prepares or transforms data for the report. This might involve setting report parameters, filtering information, or structuring the output.
- Generating Report Content (Placeholder): A "Code" node is included, which is typically used for custom logic or data manipulation. In the context of "security audit reports," this node would likely contain JavaScript code to:
- Fetch security audit data from various sources (e.g., APIs, databases).
- Process and analyze the data.
- Format the data into a readable report structure (e.g., HTML, plain text, or a summary).
- Sending Email via Gmail: The final step involves sending the generated report as an email using Gmail. This ensures that the report reaches its intended recipients promptly.
- Internal n8n Operations (Placeholder): An "n8n" node is included, which can be used for various internal n8n operations, such as calling other workflows, managing workflow executions, or interacting with n8n's API. Its exact function in this workflow is not specified by the JSON, but it could be for logging or advanced workflow management.
- Documentation: A "Sticky Note" is included, indicating that the workflow creator has added internal documentation or notes for clarity.
Prerequisites/Requirements
To use this workflow, you will need:
- n8n Instance: A running n8n instance.
- Gmail Account: A Google account with Gmail enabled for sending emails. You will need to configure a Gmail credential in n8n.
Setup/Usage
- Import the Workflow: Download the provided JSON and import it into your n8n instance.
- Configure Credentials:
- Set up a Gmail credential in n8n, granting it the necessary permissions to send emails.
- Customize the Workflow:
- Cron Node: Adjust the schedule in the
Cronnode to define when you want the weekly reports to be generated and sent (e.g., every Monday at 9 AM). - If Node: If the
Ifnode is intended for specific conditions, configure its logic based on your requirements. - Edit Fields (Set) Node: Customize the
Edit Fieldsnode to prepare the data for your report. - Code Node: Crucially, update the
Codenode with your specific JavaScript logic to:- Integrate with your security audit data sources (e.g., APIs, databases, log files).
- Perform the necessary data processing and analysis for your report.
- Generate the actual report content (e.g., HTML body, text summary, or attach a file).
- Gmail Node: Configure the
Gmailnode with the recipient email addresses, subject line, and ensure the email body uses the output from yourCodenode for the report content.
- Cron Node: Adjust the schedule in the
- Activate the Workflow: Once configured, activate the workflow to start automated weekly report delivery.
Related Templates
Auto-create TikTok videos with VEED.io AI avatars, ElevenLabs & GPT-4
💥 Viral TikTok Video Machine: Auto-Create Videos with Your AI Avatar --- 🎯 Who is this for? This workflow is for content creators, marketers, and agencies who want to use Veed.io’s AI avatar technology to produce short, engaging TikTok videos automatically. It’s ideal for creators who want to appear on camera without recording themselves, and for teams managing multiple brands who need to generate videos at scale. --- ⚙️ What problem this workflow solves Manually creating videos for TikTok can take hours — finding trends, writing scripts, recording, and editing. By combining Veed.io, ElevenLabs, and GPT-4, this workflow transforms a simple Telegram input into a ready-to-post TikTok video featuring your AI avatar powered by Veed.io — speaking naturally with your cloned voice. --- 🚀 What this workflow does This automation links Veed.io’s video-generation API with multiple AI tools: Analyzes TikTok trends via Perplexity AI Writes a 10-second viral script using GPT-4 Generates your voiceover via ElevenLabs Uses Veed.io (Fabric 1.0 via FAL.ai) to animate your avatar and sync the lips to the voice Creates an engaging caption + hashtags for TikTok virality Publishes the video automatically via Blotato TikTok API Logs all results to Google Sheets for tracking --- 🧩 Setup Telegram Bot Create your bot via @BotFather Configure it as the trigger for sending your photo and theme Connect Veed.io Create an account on Veed.io Get your FAL.ai API key (Veed Fabric 1.0 model) Use HTTPS image/audio URLs compatible with Veed Fabric Other APIs Add Perplexity, ElevenLabs, and Blotato TikTok keys Connect your Google Sheet for logging results --- 🛠️ How to customize this workflow Change your Avatar: Upload a new image through Telegram, and Veed.io will generate a new talking version automatically. Modify the Script Style: Adjust the GPT prompt for tone (educational, funny, storytelling). Adjust Voice Tone: Tweak ElevenLabs stability and similarity settings. Expand Platforms: Add Instagram, YouTube Shorts, or X (Twitter) posting nodes. Track Performance: Customize your Google Sheet to measure your most successful Veed.io-based videos. --- 🧠 Expected Outcome In just a few seconds after sending your photo and theme, this workflow — powered by Veed.io — creates a fully automated TikTok video featuring your AI avatar with natural lip-sync and voice. The result is a continuous stream of viral short videos, made without cameras, editing, or effort. --- ✅ Import the JSON file in n8n, add your API keys (including Veed.io via FAL.ai), and start generating viral TikTok videos starring your AI avatar today! 🎥 Watch This Tutorial --- 📄 Documentation: Notion Guide Need help customizing? Contact me for consulting and support : Linkedin / Youtube
By Dr. FirasTwo-way property repair management system with Google Sheets & Drive
This workflow automates the repair request process between tenants and building managers, keeping all updates organized in a single spreadsheet. It is composed of two coordinated workflows, as two separate triggers are required — one for new repair submissions and another for repair updates. A Unique Unit ID that corresponds to individual units is attributed to each request, and timestamps are used to coordinate repair updates with specific requests. General use cases include: Property managers who manage multiple buildings or units. Building owners looking to centralize tenant repair communication. Automation builders who want to learn multi-trigger workflow design in n8n. --- ⚙️ How It Works Workflow 1 – New Repair Requests Behind the Scenes: A tenant fills out a Google Form (“Repair Request Form”), which automatically adds a new row to a linked Google Sheet. Steps: Trigger: Google Sheets rowAdded – runs when a new form entry appears. Extract & Format: Collects all relevant form data (address, unit, urgency, contacts). Generate Unit ID: Creates a standardized identifier (e.g., BUILDING-UNIT) for tracking. Email Notification: Sends the building manager a formatted email summarizing the repair details and including a link to a Repair Update Form (which activates Workflow 2). --- Workflow 2 – Repair Updates Behind the Scenes:\ Triggered when the building manager submits a follow-up form (“Repair Update Form”). Steps: Lookup by UUID: Uses the Unit ID from Workflow 1 to find the existing row in the Google Sheet. Conditional Logic: If photos are uploaded: Saves each image to a Google Drive folder, renames files consistently, and adds URLs to the sheet. If no photos: Skips the upload step and processes textual updates only. Merge & Update: Combines new data with existing repair info in the same spreadsheet row — enabling a full repair history in one place. --- 🧩 Requirements Google Account (for Forms, Sheets, and Drive) Gmail/email node connected for sending notifications n8n credentials configured for Google API access --- ⚡ Setup Instructions (see more detail in workflow) Import both workflows into n8n, then copy one into a second workflow. Change manual trigger in workflow 2 to a n8n Form node. Connect Google credentials to all nodes. Update spreadsheet and folder IDs in the corresponding nodes. Customize email text, sender name, and form links for your organization. Test each workflow with a sample repair request and a repair update submission. --- 🛠️ Customization Ideas Add Slack or Telegram notifications for urgent repairs. Auto-create folders per building or unit for photo uploads. Generate monthly repair summaries using Google Sheets triggers. Add an AI node to create summaries/extract relevant repair data from repair request that include long submissions.
By Matt@VeraisonLabsAutomate 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.
By Le Nguyen