by WeblineIndia
📝 Compliance Report Collector (Google Form → Drive + MySQL) This n8n workflow automates the collection and archival of compliance reports submitted via Google Forms. Uploaded documents (PDF, DOCX, etc.) are archived into Google Drive and submission metadata is logged into a MySQL database. It ensures compliance documentation is properly stored, searchable and auditable without manual effort. ⚡ Quick Implementation Steps Import the JSON file into n8n. Set up a Google Form to POST file + metadata (reporter, category, etc.) to the /submit-report webhook. Update the Set Config node with your: MySQL connection details Google Drive folder ID Deploy and test a form submission with a file upload. Each report is stored in Drive and logged to your DB. 🎯 Who’s It For Compliance officers handling environmental or safety reports. Admins managing documentation for inspections. Renewable energy companies required to maintain audit-ready records. Any org needing structured report archival & metadata logging. 🛠 Requirements | Tool | Purpose | |------|---------| | n8n Instance | Workflow automation | | Google Drive | To archive uploaded reports | | MySQL Database | To log submission metadata | | Google Forms / HTML Form | Report submission source | 🧠 What It Does Listens for incoming POST requests with a file and metadata. Uploads the file to a specified Google Drive folder. Extracts metadata like: Reporter name Category/type Timestamp File name, MIME type Logs that metadata into a MySQL table for auditing or reporting. 🧾 Sample MySQL Table Schema CREATE TABLE report_logs ( id INT AUTO_INCREMENT PRIMARY KEY, reporter VARCHAR(100), category VARCHAR(100), timestamp DATETIME, file_name VARCHAR(255), mime_type VARCHAR(50), folder_id VARCHAR(100) ); 🔧 How To Set Up – Step-by-Step Import the JSON into n8n. Configure the following in the Set Config node: MySQL: dbHost, dbUser, dbPassword, dbName, dbTable Google Drive: driveFolderId Update the webhook URL in your Google Form (via Apps Script or middleware). Test submission with a file upload. Confirm: File lands in your Drive folder Log entry appears in your database ✨ How To Customize | Customization | How | |---------------|-----| | Add more form fields | Extend the metadata mapping in the Function node | | Rename files before upload | Modify filename in Google Drive node | | Add email confirmation | Add an Email Send node after DB insert | | Filter file types | Add IF node before upload to validate MIME type | ➕ Add‑ons (Optional Extensions) | Add-on | Description | |--------|-------------| | 📤 Email Acknowledgment | Email sender a confirmation with Drive link | | 🧾 PDF Parser | Auto-parse content using PDF.co or OpenAI | | 📊 Admin Dashboard | Display logs in Supabase or Metabase | | 🗃 File Backup | Copy files to Dropbox or S3 after Drive upload | 📈 Use Case Examples Collect monthly safety audits from plant staff into a Drive archive. Accept vendor compliance declarations via Google Form and auto-log to DB. Capture field inspection reports and tag by category for audit. Store weekly environmental reports for long-term access. 🧯 Troubleshooting Guide | Issue | Possible Cause | Solution | |-------|----------------|----------| | File not uploaded | Drive ID is invalid | Check permissions and folder ID | | DB not logging | Connection or table issue | Verify DB credentials and schema | | Webhook not triggered | Form not integrated correctly | Ensure form POSTs file to n8n webhook | | Wrong file type | MIME mismatch | Validate acceptable types via Function/IF node | 📞 Need Help? Want to integrate this with audit dashboards or add Google Sheet exports? 👉 Contact WeblineIndia — Experts in compliance automation and renewable energy workflows.
by Miha
New to n8n? This simple tutorial is the perfect way to get started. In just a few minutes, you’ll build your first automation that runs on a schedule, fetches fresh data from the internet and delivers it straight to your inbox. What you’ll do Run the workflow to grab a random inspirational quote. See how data flows through each node as it moves from an API call to processing results. Connect Gmail and send the quote directly to your email. What you’ll learn How to trigger workflows manually and on a schedule ⏰ How to connect to external APIs and fetch data 🌐 How to use the Set node to structure and map data 🔧 How to connect Gmail to send the data 📩 Why it matters This workflow shows you the n8n basics step by step - no code required. By the end, you’ll know how to build, test, and share automations that run on their own, giving you the confidence to explore more advanced use cases. 🚀
by Ziad Adel
What This Workflow Does This workflow transforms Google Sheets into a lightweight productivity engine and connects it to Slack for automated reminders and daily recaps. No extra SaaS, no extra cost – just a simple system that keeps you on track and accountable. Pre-conditions / Requirements Before you start, make sure you have: A Google account with access to Google Sheets. A Slack workspace where you can post reminders and summaries. An n8n instance (self-hosted or cloud) with: Google Sheets credentials connected. Slack credentials connected. How It Works Task Tracking in Google Sheets Add tasks with columns: Task ID, Task Name, Due Date, Status, and Why it matters. The workflow checks for tasks that are due soon or overdue. Automated Slack Reminders Every 15 minutes, the workflow scans for tasks due in the next 30 minutes. Slack sends a ping with the task name, deadline, and reason. Daily Recap at 6 PM Slack posts a summary of how many tasks you completed vs how many are still pending. Encourages reflection and accountability. Duplicate Protection Each task has a "Last Reminder Sent" column so you don’t get spammed with repeat messages. Customization Options Reminder Frequency**: Change the Cron node to check tasks every 5, 10, 30 minutes, or hourly. Daily Recap Time**: Adjust the daily Cron node (default: 6 PM) to match your schedule. Slack Channel**: Point reminders and recaps to a private DM, a public channel, or multiple channels. Task Fields**: Add columns like Priority, Assigned To, or Category and adjust Slack messages accordingly. Weekly Review**: Extend the workflow with another Cron node on Sundays to send a weekly productivity score. Reflection Logs**: Add automation to write daily results into a second tab for trend tracking. Benefits ✅ Eliminate missed deadlines with proactive reminders. ✅ Daily accountability inside Slack – no extra dashboards. ✅ Zero SaaS costs – only Sheets, Slack, and n8n. ✅ Fully customizable to match your workflow, team, or habits. ✅ Scales easily from solo use to team task tracking. Use Cases Solo founders or freelancers who want a cheap but powerful task manager. Small teams who live in Slack and want lightweight accountability. Productivity enthusiasts who want flexibility and control without being locked into another SaaS.
by Muhammad Anas Farooq
n8n Self-Updater Workflow An automated n8n workflow originally built for DigitalOcean-based n8n deployments, but fully compatible with any VPS or cloud hosting (e.g., AWS, Google Cloud, Hetzner, Linode, etc.) where n8n runs via Docker. This workflow checks for the latest Docker image of n8n, notifies you via email for approval, and securely updates your n8n instance via SSH once approved. How It Works Trigger: The workflow runs automatically every 3 days at 4 PM UTC (or manually if triggered). Check Version: It retrieves your current n8n Docker version and image digest via SSH. Compare: Fetches the remote digest from Docker Hub and compares it with the local one. Notify via Email: If a new update is available, an approval email is sent with details: Current version Local digest Remote digest What will happen after approval Approval Logic: Approve → Workflow connects via SSH and updates the n8n container automatically. Decline → Workflow ends; next check occurs in the next cycle. Auto Update Execution: Creates (if missing) a update_docker.sh script on the server. Runs it in the background (nohup) to: cd /opt/n8n-docker-caddy docker compose pull docker compose down docker compose up -d The delay ensures n8n restarts only after workflow completion. Requirements SSH Access** to your server (where n8n runs). Add your credentials in n8n under Credentials → SSH Password. SMTP Connection** for email notifications. Configure in Credentials → SMTP. Fill in: From Email → e.g., info@yourdomain.com To Email → your email for receiving approvals Docker-based n8n Deployment**, e.g., n8n-docker-caddy setup. Docker and docker-compose** installed on the server. How to Use Import the Workflow: Copy the provided JSON file. In your n8n instance → click Import Workflow → paste the JSON. Set Up Credentials: Create two credentials in n8n: SSH Password → Your server's SSH credentials. SMTP → Your email provider's SMTP credentials. Edit the Email Node: Replace: fromEmail: info@yourdomain.com → with your email. toEmail: youremail@yourdomain.com → with your desired recipient. Enable Auto Trigger (optional): Go to the Schedule Trigger node and set your desired interval/time. Run the Workflow: Test manually first. Once verified, activate it for automatic checks. Notes Originally designed for DigitalOcean VPS setups, but can run on any Docker-based n8n server. The workflow avoids duplicate updates by comparing digests instead of version tags. If the update_docker.sh file already exists, it reuses it safely. Approval emails include full details for transparency. Background execution ensures no interruptions during restart. Example Behavior Day 1**: Workflow checks → detects update → sends email → user approves. 30 seconds later**: Workflow runs update script → n8n restarts with latest Docker image. Day 4**: Workflow checks again → digests match → silently completes (no email sent). Author: Muhammad Anas Farooq
by Yaron Been
This workflow provides automated access to the Fofr Any Comfyui Workflow AI model through the Replicate API. It saves you time by eliminating the need to manually interact with AI models and provides a seamless integration for other generation tasks within your n8n automation workflows. Overview This workflow automatically handles the complete other generation process using the Fofr Any Comfyui Workflow model. It manages API authentication, parameter configuration, request processing, and result retrieval with built-in error handling and retry logic for reliable automation. Model Description: Run any ComfyUI workflow. Guide: https://github.com/replicate/cog-comfyui Key Capabilities Specialized AI model with unique capabilities** Advanced processing and generation features** Custom AI-powered automation tools** Tools Used n8n**: The automation platform that orchestrates the workflow Replicate API**: Access to the Fofr/any-comfyui-workflow AI model Fofr Any Comfyui Workflow**: The core AI model for other generation Built-in Error Handling**: Automatic retry logic and comprehensive error management How to Install Import the Workflow: Download the .json file and import it into your n8n instance Configure Replicate API: Add your Replicate API token to the 'Set API Token' node Customize Parameters: Adjust the model parameters in the 'Set Other Parameters' node Test the Workflow: Run the workflow with your desired inputs Integrate: Connect this workflow to your existing automation pipelines Use Cases Specialized Processing**: Handle specific AI tasks and workflows Custom Automation**: Implement unique business logic and processing Data Processing**: Transform and analyze various types of data AI Integration**: Add AI capabilities to existing systems and workflows Connect with Me Website**: https://www.nofluff.online YouTube**: https://www.youtube.com/@YaronBeen/videos LinkedIn**: https://www.linkedin.com/in/yaronbeen/ Get Replicate API**: https://replicate.com (Sign up to access powerful AI models) #n8n #automation #ai #replicate #aiautomation #workflow #nocode #aiprocessing #dataprocessing #machinelearning #artificialintelligence #aitools #automation #digitalart #contentcreation #productivity #innovation
by Zil Money
Create Digital Checks with OnlineCheckWriter using Forms This workflow automates the process of creating and sending digital checks through OnlineCheckWriter's API using user-friendly forms. Perfect for businesses that need to process one-off payments or integrate check payments into their automation workflows. Prerequisites Before using this template, ensure you have: OnlineCheckWriter Account: Sign up at onlinecheckwriter.com API Key: Generate from your OCW dashboard under Settings > API Verified Bank Account: Add and verify at least one bank account in OCW Bank Account ID: Found in your OCW dashboard under Bank Accounts How It Works This workflow uses a two-step form process: API Configuration Form: One-time setup to store your OCW credentials Check Details Form: Collects recipient and payment information for each check The workflow then automatically: Validates all required fields Sends the check request to OnlineCheckWriter's API Returns a confirmation with the check ID and tracking information Setup Instructions Step 1: Import the Workflow Copy this workflow template to your n8n instance Activate the workflow Step 2: Configure API Credentials Access the first form at: [your-n8n-url]/webhook/e4f29ca4-5982-42ae-950c-e4d1d7b10a93 Enter your API Key from OnlineCheckWriter Enter your Bank Account ID Provide a friendly Account Name for reference Step 3: Create Checks Access the check form at: [your-n8n-url]/webhook/72ea8a5d-4655-4ad3-bde2-024dd3dadd9f Fill in recipient details: Payee Name (required) Company Name (optional) Complete Address (required) Contact Information (phone & email required) Enter payment details: Amount (in USD) Memo (appears on check) Internal Note (for your records) Reference ID (optional tracking) Issue Date Submit to create and send the check Customization Options Switch to Production By default, this workflow uses the OCW test environment. To switch to production: Edit the Send Check via OCW API node Change URL from https://test.onlinecheckwriter.com/api/v3/quickpay/check to https://app.onlinecheckwriter.com/api/v3/quickpay/check Add Custom Fields You can extend the forms with additional fields: Invoice numbers Department codes Project references Custom metadata Integrate with Other Systems Connect this workflow to: Google Sheets: Track payments in a spreadsheet Slack: Send notifications when checks are created Email: Send confirmations to recipients Accounting Software: Update your books automatically Error Handling To add error notifications: Add an Error Trigger node Connect to email or Slack for alerts Log failed attempts to a database Workflow Components OCW API Configuration Form Collects and stores API credentials securely One-time setup per account Validates connection to OnlineCheckWriter Check Details Form User-friendly interface for payment entry Field validation ensures data accuracy Optional fields for flexibility Send Check via OCW API Handles API authentication Formats data according to OCW specifications Includes error handling with 30-second timeout Success Response Confirms check creation Provides check ID for tracking Returns status information Security Considerations API Keys: Store securely and never share Test Mode: Always test in OCW's sandbox environment first Access Control: Restrict form URLs to authorized users Data Validation: All inputs are validated before API submission Troubleshooting Common Issues: 401 Error: Invalid API key - verify in OCW dashboard 400 Error: Missing required fields - check form data 404 Error: Invalid bank account ID - verify in OCW Timeout: Network issues - check connectivity Support OnlineCheckWriter API Docs: developer.onlinecheckwriter.com n8n Community: community.n8n.io Template Issues: Contact via n8n template comments Use Cases This workflow is ideal for: Freelancers: Send client payments Small Businesses: Process vendor payments Property Management: Issue rent refunds Non-Profits: Distribute grants or donations HR Departments: Process reimbursements Version History v1.1: Added sticky notes, improved node naming, enhanced error handling v1.0: Initial release
by Zane
This workflow automates a batch upload of multiple videos to YouTube, spacing each upload 12 hours apart in Japan Standard Time (UTC+9) and automatically adding them to a playlist. ⚙️ Workflow Logic Manual Trigger — Starts the workflow manually. List Video Files — Uses a shell command to find all .mp4 files under the specified directory (/opt/downloads/单词卡/A1-A2). Sort and Generate Items — Sorts videos by day number (dayXX) extracted from filenames and assigns a sequential order value. Calculate Publish Schedule (+12h Interval) — Computes the next rounded JST hour plus a configurable buffer (default 30 min). Staggers each video’s scheduled time by order × 12 hours. Converts JST back to UTC for YouTube’s publishAt field. Split in Batches (1 per video) — Iterates over each video item. Read Video File — Loads the corresponding video from disk. Upload to YouTube (Scheduled) — Uploads the video privately with the computed publishAtUtc. Add to Playlist — Adds the newly uploaded video to the target playlist. 🕒 Highlights Timezone-safe:** Pure UTC ↔ JST conversion avoids double-offset errors. Sequential scheduling:** Ensures each upload is 12 hours apart to prevent clustering. Customizable:** Change SPAN_HOURS, BUFFER_MIN, or directory paths easily. Retry-ready:** Each upload and playlist step has retry logic to handle transient errors. 💡 Typical Use Cases Multi-part educational video series (e.g., A1–A2 English learning). Regular content release cadence without manual scheduling. Automated YouTube publishing pipelines for pre-produced content. Author: Zane Category: Automation / YouTube / Scheduler Timezone: JST (UTC+09:00)
by Paul I
Error workflow alert This workflow sends an alert to the channel of your choice when an execution fails. How to use Connect the tool where you want alerts to be sent (eg. Gmail, Slack, Teams, etc.) Save the workflow Turn on error notification in the workflows you want to monitor Help Step-by-step tutorial
by Automate With Marc
Auto-Edit Images from Google Drive with (Wavespeed) Nano Banana and Send via Gmail When a new image is uploaded to a specific Google Drive folder, this workflow sends it to Wavespeed’s Google Nano Banana image editing API, waits for the edited version, and then emails the result automatically. Perfect for creators, marketers, and ops teams who want hands-off, consistent image edits with instant delivery to a stakeholder inbox. 👉 Watch step-by-step video tutorials of workflows like these on: www.youtube.com/@automatewithmarc Highlights Google Drive trigger detects new image uploads Wavespeed API (Google Nano Banana) performs automated image editing Polling loop checks job status until complete Gmail auto-sends the edited image to your chosen recipient Great for social media pipelines, product photo retouching, or team approvals Apps & Nodes Used Trigger: Google Drive Trigger (fileCreated in folder) HTTP Request: POST to Wavespeed (submit edit job) Wait: Delay before first status check (15s) HTTP Request: GET result (poll prediction status) IF: Status == completed → proceed, else wait & recheck Gmail: Send edited image output to recipient Prerequisites n8n account (Cloud or Self-hosted) Google Drive folder for uploads Wavespeed API key (HTTP Header Auth) Gmail account with OAuth2 connected to n8n Configuration (5 Steps) Google Drive Trigger – set to your image upload folder. POST Image Edit Request – sends file URL + prompt (default: “Change the lighting to night scene”). Wait 15s – lets the job start. GET Image Edit Request – checks prediction status/result. IF → Gmail – once status = completed, send edited image to your chosen email. Customization Change the prompt (e.g., “remove background”, “enhance product lighting”). Set Gmail recipient dynamically or statically. Adjust polling wait times based on job length. Save results to Drive/S3 instead of email if needed. Error Handling Add IF nodes to catch API errors. Set a retry limit to avoid infinite loops. Use Drive “Share File” if API can’t access the uploaded file link.
by Meelioo
How it works This workflow automatically handles errors in your n8n workflows by: Detecting when an error occurs and capturing the error details Sending an email notification with the error message and affected node Allowing you to deactivate the workflow or ignore the error via email response Optionally rerouting the error notification to another user for approval The workflow includes two templates: a basic version with simple deactivate/ignore options, and an advanced version that allows error rerouting to a second user. Set up steps Estimated time: 5-10 minutes You'll need to configure SMTP credentials for sending emails, set up n8n API access for workflow management, and update email addresses and workflow URLs throughout the nodes. Choose which template (basic or reroute logic) fits your needs, then activate the workflow to start monitoring for errors.
by Jose Bossa
n8n Workflow Backup System 👥 Who's it for This workflow is perfect for n8n users who want to automatically backup all their workflows 💾 to Google Drive with zero manual effort. Perfect for teams managing multiple workflows or anyone who values data safety! 🔒 🤖 What it does It automatically creates daily backups of all your n8n workflows to Google Drive in readable JSON format, organizes them in dated folders, and cleans up old backups to save storage space. Set it and forget it! ✨ ⚙️ How it works Spanish Version (Español) 🇪🇸 ⏰ Schedule Trigger – Runs automatically every day at 4:00 AM 📁 Create New Folder – Creates a timestamped backup folder in Google Drive 🔌 n8n API Connection – Fetches all workflows from your n8n instance 🔄 Loop Over Items – Processes each workflow individually through two paths: Upper Path (Cleanup): 🗂️ Get Folders – Retrieves all existing backup folders 🔍 Filter – Excludes the current folder 🗑️ Delete Folder – Permanently removes old backups Lower Path (Backup): 📄 Convert to File – Transforms workflow to formatted JSON ☁️ Google Drive – Saves JSON file to backup folder English Version 🇬🇧 Identical functionality with English interface 📋 Requirements n8n instance** with API access enabled Google Drive account** with sufficient storage n8n API credentials** configured Google Drive OAuth2 credentials** configured 🛠️ How to set up Configure n8n API credentials: Format: https://your-instance.n8n.io/api/v1 Generate API key from your n8n instance settings Set up Google Drive credentials: Connect your Google account via OAuth2 Grant necessary permissions for folder creation and file management Configure target folder: Create a parent folder in Google Drive (e.g., "N8N Backups") Copy the folder ID from the URL Update the folderId in "create new folder" nodes Adjust schedule (optional): Default: 4:00 AM daily Modify triggerAtHour in Schedule Trigger node Test manually: Use the Manual Trigger to test before scheduling Verify folders are created and files are saved correctly Activate the workflow ✅ 🎨 How to customize Change backup frequency:** Modify Schedule Trigger settings (hourly, weekly, monthly) Keep multiple backup versions:** Remove or modify the cleanup path to retain more history Change folder naming:** Edit the folder name format in "create new folder" node (default: Workflow Backups [day] [time] [date]) Backup to different location:** Change the parent folder ID Add notifications:** Include email/Slack nodes to get backup completion alerts Filter specific workflows:** Add Filter node after n8n node to backup only certain workflows ⚠️ Important Notes Old backups are permanently deleted by default to save space Ensure sufficient Google Drive storage for your workflow size API credentials must have read access to all workflows The workflow processes items sequentially to avoid rate limits
by InfraNodus
Build an embeddable AI chatbot with an access to a knowledge base This is an example of a simple AI chatbot that has access to external knowledge to augment its responses. The knowledge can be added manually or imported from multiple sources (text and PDF files, websites, CSVs, Google search results, AI generated, YouTube search results, RSS feeds, etc) using InfraNodus. • no OpenAI account needed • no vector store needed • easy data import: PDF, text, CSV, Google / YouTube results, RSS feeds, websites, or AI-generated How it works First, you add your data into your InfraNodus graph — this will be your knowledge base. You can import this data from multiple sources or add it manually. You will have a visual interface available that will show the main concepts and topics in your knowledge base, so you can have an overview of its structure and know how to improve it, if necessary. Your data is represented as a knowledge graph which contains information about relations and topical clusters in your data, making the LLM responses much more precise. How to use Copy the template Add your InfraNodus API key to the HTTP AI response node Create a new graph in InfraNodus with your data (or import from an external source) Add the name of this graph into the name field of the AI response HTTP node. That's it! You can query it using the embeddable web form available via a URL Requirements You only need an InfraNodus account to set this workflow up. Free 14-day trials are available.