Workflow Templates

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)

This template demonstrates how to combine n8n, OpenAI agents, and the new Xano Node to build an intelligent support-ticket routing system — without writing a single API call. Start your Xano journey with the downloadable snippet here! When a ticket arrives, the workflow: Receives the ticket via Webhook Classifies the issue using an n8n Agent with an OpenAI model Searches Xano to check whether the user already exists Creates or updates records using the native Xano Node (no headers or manual HTTP setup) Triggers backend logic in Xano, where escalation rules and agent workflows process the ticket Returns a structured response to n8n for further routing (Slack, CRM, inbox, etc.) This template highlights how Xano can act as your backend intelligence layer while n8n orchestrates everything else — making it easy to automate support operations, apply escalation policies, and unify your data across tools. Use this as a foundation to build more advanced automation: customer enrichment, billing checks, account risk detection, SLA enforcement, and more. Happy building! 🚀

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

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

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

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.

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.

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.

Automate syncing of offline donor data from Google Sheets into SinergiaCRM for fast, error-free face-to-face fundraising tracking. Who is this workflow for? This workflow is perfect for nonprofit organizations that run face-to-face fundraising campaigns and collect donor data offline (e.g. via tablets or spreadsheets). It helps fundraising and CRM teams ensure donor records are correctly and automatically stored in SinergiaCRM, a popular CRM platform used by NGOs. What it does / How it works Watches a Google Sheet for new rows (also works offline if synced later). Filters rows marked To CRM = Yes and Processed = No. Checks if the donor already exists in SinergiaCRM (based on NIF). If the contact exists: creates a “member” relationship and a payment commitment. If not: creates the contact first, then adds the relationship and commitment. Finally, updates the original row as “Processed” to prevent re-importing. Requirements An active Google Sheets account with the donor spreadsheet. A SinergiaCRM account with API/OAuth access. Fields First name, Last name, Email, NIF, To CRM, Processed must exist in the sheet. SinergiaCRM modules enabled: Contacts, stic_Contacts_Relationships, stic_Payment_Commitments. How to set up Connect your Google Sheets account and set the correct Document ID and Sheet name in the trigger and update nodes. Connect your SinergiaCRM account using OAuth credentials. Adjust the assigned_user_id field if required by your CRM instance. How to customize the workflow Change the filter conditions in the IF nodes to match your business logic. Customize fields like relationship type, amount, and periodicity to suit your campaign. Add or remove nodes if you want additional steps (like sending Slack notifications). 📌 Category: CRM & Customer Management 📘 Learn more about SinergiaCRM

Eventbrite → Pipedrive Lead‑Sync Bring your Eventbrite attendee data into Pipedrive automatically—no spreadsheets, CSVs, or manual uploads. 🚀 What the Workflow Does Polls Eventbrite* on a schedule (default 30 min) for *new registrations. Creates or updates* matching *Person* and *Deal** records in Pipedrive. Deduplicates** by email and stores a timestamp so each attendee is processed only once. Easily configurable** field‑mapping lets you decide exactly which attendee data lands in Pipedrive. 📋 Key Features | Feature | Benefit | |---------|---------| | Incremental Sync | Processes only registrations created since the last run. | | Person + Deal Linking | Keeps contacts and sales opportunities in one place. | | No Community Nodes | 100 % official n8n nodes—simple to import and run. | | Fully Editable Code Node | Swap your Eventbrite token, organization ID, and field mappings in seconds. | 🔑 Prerequisites Eventbrite Personal OAuth Token** Eventbrite Organization ID** Pipedrive API Token** n8n 1.25 or later 🛠 Quick Start Import the workflow JSON. Open the Code node → paste your Eventbrite token and organization ID. Add your Eventbrite and Pipedrive credentials in their respective nodes. Activate the workflow and watch new registrants appear in Pipedrive within minutes. Contact Email:** rbreen@ynteractive.com Website:** https://ynteractive.com YouTube:** https://www.youtube.com/@ynteractivetraining LinkedIn:** https://www.linkedin.com/in/robertbreen

📊 n8n Workflow: Email Validation & Google Sheets Update This workflow automates the process of validating email addresses stored in a Google Sheet. It reads each email, checks if it's disposable or fake using Email Validator AI via RapidAPI, and updates the same row with the result. All interactions with Google Sheets are done securely using a Google Service Account. ✅ Node-wise Overview 🔘 Manual Trigger Starts the workflow manually from the n8n editor. 📄 Google Sheets (Read) Reads all rows (including emails) from a specified Google Sheet. 🔁 Split In Batches Processes each row (email) one at a time. 🌐 HTTP Request (RapidAPI) Sends the email to Email Validator AI for validation. 🟩 Google Sheets (Update Row) Updates the corresponding row in the sheet with the validation result. 📋 Google Sheet Columns Required Make sure your Google Sheet contains the following columns: | Column Name | Purpose | |------------------|----------------------------------------------| | email | Email address to validate | | is_disposable | Flags if the email is a disposable address | > 📝 You can rename columns, but ensure the node mappings in n8n match accordingly. 💡 Use Cases 📧 Email List Cleanup Keep your lead or contact lists free of fake, temporary, or disposable emails. 🧼 Data Quality Enhancement Ensure your Google Sheets contain only validated, high-quality email addresses. 🔁 Automated Data Enrichment Add metadata (like is_disposable) to your contacts without manual review. 📥 Lead Qualification Filtering Automatically flag or remove junk leads before importing into CRMs or email tools. 🚀 Benefits of This Workflow (for You) 🧼 Cleans Your Email Data Automatically Detects fake or throwaway email addresses using Email Validator AI and flags them right in your spreadsheet. ⏳ Saves You Time Fully automates email validation — no more copy-pasting into online tools. 📈 Improves Marketing & Outreach Accuracy Focuses your efforts on real contacts, improving delivery, open, and conversion rates. 💡 Lets You Focus on High-Value Leads Filters out low-quality leads so you can prioritize those with actual potential. 🔄 Works Seamlessly Within Google Sheets No import/export headaches — updates happen directly in your existing sheet. 🔐 Runs Securely Without Manual Intervention Uses a Google Service Account for safe access and can be scheduled to run automatically. 🛠️ Requirements to Use A Google Sheet with the required columns listed above A RapidAPI key for Email Validator AI A Google Service Account with access to the sheet Proper credentials configured in your n8n instance 🧪 Tips for Enhancement Add a status or note column for better tracking Filter only unvalidated rows to improve performance Send a Slack or Email notification when invalid emails are found Schedule this workflow using a Cron Trigger to run daily/weekly

This workflow is a user-friendly tool that automates the creation of high-quality advertising images for products. It takes a simple product image uploaded by a user and uses AI to transform it into a professional, photorealistic advertisement featuring a fashion model actively using the product. The final image is then made available for the user to download. Step-by-Step Breakdown: Here is a breakdown of the automated process: Form Submission: The workflow is triggered by a public form. The user uploads a product image and selects a character model (male or female) from a dropdown menu. Image Processing: The uploaded image file is extracted and prepared for the AI. This includes converting the binary file data into a format that the AI model can understand. AI Image Generation: An HTTP request is sent to a large language model (Google's Gemini via OpenRouter). The request includes a prompt that combines the user's selected character model and the uploaded product image. The AI is instructed to generate a new, photorealistic image of the model using the product. Data Conversion: The AI's output, which is a base64 encoded image string, is then processed. The workflow separates the image data from its metadata. Final Image Delivery: The base64 data is converted back into a binary file, which is then provided to the user for automatic download via a completion form.