The Ultimate n8n TemplatesLibrary & Marketplace

Discover 7000+ premium n8n templates with AI-powered generation. The largest n8n templates marketplace enabling anyone to have a running workflow in 5 minutes

Start AI Generation Browse Templates

Or browse our extensive n8n templates collection. Try the AI generator to create custom n8n templates instantly.

10524+

Templates

50+

Integrations

50k+

Downloads

Latest n8n Templates

Freshly updated automation workflows to keep your n8n stack current

View All

Automatic AI reply when mentioned in a Liveblocks comment

Automatic AI reply when mentioned in a Liveblocks comment This example uses Liveblocks Comments, collaborative commenting components for React. When an AI assistant is mentioned in a thread (e.g. "@AI Assistant"), it will automatically leave a response. Using webhooks, this workflow is triggered when a comment is created in a thread. If the agent's ID ("__AI_AGENT") was mentioned, an AI agent is given the entire thread context, and asked to create a response. This response is then added, and users will see it appear in their apps in real time. Set up This workflow requires a Comments app installed and webhooks set up in the Liveblocks dashboard. You can try it with a demo application: Download the Next.js comments example, and run it with a secret key. Find database.ts inside the example and uncomment the AI assistant user. Insert the secret key from the project into n8n nodes: "Get a comment", "Get a thread", "Create a comment". Go to the Liveblocks dashboard, open your project and go to "Webhooks". Create a new webhook in your project using a placeholder URL, and selecting "commentCreated" events. Copy your webhook secret from this page and paste it into the "Liveblocks Trigger" node. Expose the webhook URL from the trigger, for example with localtunnel or ngrok. Copy the production URL from the "Liveblocks Trigger" and replace localhost:5678 with the new URL. Your workflow is now set up! Tag @AI Assistant in the application to trigger it. Localtunnel The easiest way to expose your webhook URL: npx localtunnel --port 5678 --subdomain your-name-here This creates a URL like: https://honest-months-fix.loca.lt The URL you need for the dashboard looks like this: https://honest-months-fix.loca.lt/webhook/9cc66974-aaaf-4720-b557-1267105ca78b/webhook `

BeginnerManual Trigger

by Liveblocks

Analyze Liveblocks comment attachments with Anthropic Claude AI

Analyzing uploaded Liveblocks comments attachments with AI This example uses Liveblocks Comments, collaborative commenting components for React. When an AI assistant is mentioned in a thread (e.g. "@AI Assistant"), it will automatically leave a response. Additionally, it will analyze any PDf or image attachments in the comments, and use them to help it respond. Using webhooks, this workflow is triggered when a comment is created in a thread. If the agent's ID ("__AI_AGENT") it will create a response. If a PDF or image file is uploaded, these will be analyzed by Anthropic and used as context. This response is then added, and users will see it appear in their apps in real time. Set up This workflow requires a Comments app installed and webhooks set up in the Liveblocks dashboard. You can try it with a demo application: Download the Next.js comments example, and run it with a secret key. Find database.ts inside the example and uncomment the AI assistant user. Insert the secret key from the project into n8n nodes: "Get a comment", "Get a thread", "Create a comment". Go to the Liveblocks dashboard, open your project and go to "Webhooks". Create a new webhook in your project using a placeholder URL, and selecting "commentCreated" events. Copy your webhook secret from this page and paste it into the "Liveblocks Trigger" node. Expose the webhook URL from the trigger, for example with localtunnel or ngrok. Copy the production URL from the "Liveblocks Trigger" and replace localhost:5678 with the new URL. Your workflow is now set up! Tag @AI Assistant in the application and add attachments to trigger it. Localtunnel The easiest way to expose your webhook URL: npx localtunnel --port 5678 --subdomain your-name-here This creates a URL like: https://honest-months-fix.loca.lt The URL you need for the dashboard looks like this: https://honest-months-fix.loca.lt/webhook/9cc66974-aaaf-4720-b557-1267105ca78b/webhook `

BeginnerManual Trigger

Audit workflow credential usage to Google Sheets using Google Drive and SQLite3

Workflow Introduction This workflow is specifically for Self-Hosted N8N Docker users. The purpose of this workflow is to: Take an inventory of all workflows with credentials (Workflow -> Credential 1, Credential 2, etc.), connecting credential names to workflow names Create a credentials impact map (Credential -> Workflow 1, Workflow 2, etc.), connecting workflow names to credential IDs and names This workflow drastically minimizes the amount of time spent trying to figure out which workflows will break if a credential is updated or deleted by bridging the gap between the public API (workflow metadata) and the internal sqlite database (hidden version labels and credential mappings). In essence this tool audits your n8n environment without touching your sensitive encrypted data, keeping you API Keys 100% secure. It features dynamic time saving trackers, set for what I estimate to be the amount of time it would take to manually complete every individual thing this workflow does in less than 5 minutes. Limitations This workflow is optimized for the Standard N8N Execution Mode. Due to the high-frequency data lookups required for this tool, it is not compatible with Task Runners (N8N_RUNNERS_ENABLED=true). For maximum stability and to prevent "Database Locked" errors, please ensure your instance is running in the default configuration. Setting it up - Requirements Environment Variables Required: These enviornment variables are required in order for the version_labels and flow_names code nodes to work. NODE_FUNCTION_ALLOW_BUILTIN=* NODE_FUNCTION_ALLOW_EXTERNAL=sqlite3 Note: If you need access to multiple external functions across your n8n instance, add them as a string like this: NODE_FUNCTION_ALLOW_EXTERNAL=sqlite3, better-sqlite3 Credentials Needed: n8n account > n8n self-hosted API key Google Sheets account Google Drive account The nodes that need manually inputted credentials or node parameter information are: Create folder, flowsList, credsList, and finalFlowEdits Note: If you create your credentials before openning any process nodes, your credentials will be auto connected to the associated nodes. However, this will not happen for the n8n self-hosted API keys. If you have multiple Google Sheets or Google Drive accounts you will need to point the associated nodes to the specific one you want to use. API Key Instructions How to get: Setting > API > Create API key Copy the API key and save it somewhere secure. You won't be able to see it again!!**_ How to use: In the flowsList and credsList nodes: Authorization: None Sender Headers > field name : X-N8N-API-KEY value: <your n8n API key> Queries and Body aren't needed. Endpoints: flowsList: http://localhost:5678/api/v1/workflows or https://<your webhook domain>/api/v1/workflows credsList: http://localhost:5678/api/v1/credentials or https://<your webhook domain>/api/v1/credentials The Workflow Processes Global Actions Executes on on a set schedule (weekly on Fridays at 2pm) 1a. A deactivated execute on command node is included for testing, or for when updated files are needed before the scheduled date/time Creates a Drive folder to house the resulting spreadsheets using the current date and time as the name 2a. This workflow creates the folders inside a specified parent folder. 2b. This node also sets the folder color You are welcome to change this to your preferred color. Branch 1: Workflow Credentials Inventory Process Creates a google spreadsheet with the current date in the name Gets the list of all workflows from the public API Splits the list into individual items for easier processing Gets the version labels for active workflows from the internal sqlite database Sets fields for the workflow's name, id, published status, latest published version label, current version's id (whether the workflow is published or not) Filters out the workflows that don't have any nodes with credentials Splits out the list of nodes for easier processing Filters out the nodes that don't have associated credentials Sets fields for the node names, and credential names Summarize the output from the Nodes editor, based on workflows 10a. Append nodeNames 10b. Append credetntials 10c. Count the nodes Clean up the summarized information, converting it back to recognizible clean json format Set fields for spreadsheet aethestics This step can be skipped, however, I didn't like the visual look of the direct from CleanJson to credInventory Appends header row and data rows to the spreadsheet created in Step 1. Move the file into the folder created at the start of the workflow from whereever google put it by default Track the estimated time it would have taken to manually do every step, in a time saved node Branch 2: Credential Impact Map Process Creates a spreadsheet with the current date in the name Gets a list of all credentials from the public API Splits the list into individual items for easier processing Sorts the credentials by name in ascending order (A->Z) in case they come from the split out of order Gets a list of all workflows with nodes associated with each credential ID from the internal sqlite database Set fields for the credential name, id, type, created and updated timestamps, and list of workflow names Appends the header row and data rows to the spreadsheet created in Step 1 of this branch Move the file into the folder created at the start of the workflow from whereever google put it by default Track the estimated time it would have taken to manually do every step, in a time saved node

Monitor AWS WAF-protected product prices with CapSolver, schedule, and webhook

How it works Triggers at a regular interval or via a webhook request. Solves AWS WAF challenge then makes a request to fetch the product page. Extracts product data from the retrieved HTML page. Compares the current and previously stored data to detect any changes. Sends an alert if data has changed; else logs no change. Returns results if triggered via webhook. Setup steps [ ] Configure schedule settings in 'Every 6 Hours' node. [ ] Set up AWS WAF credentials in 'Solve AWS WAF' nodes. [ ] Input target URL in 'Fetch Product Page' nodes. [ ] Configure webhook URL in 'Receive Monitor Request' node. Customization Adjust the target site URL in 'Fetch Product Page' and related nodes to match different sites or specific pages.

BeginnerManual Trigger

Process refund requests from Gmail using Shopify and Google Sheets

How it works This workflow monitors incoming Gmail messages for refund requests and uses AI to extract the order ID and reason. It then retrieves order details from Shopify to evaluate refund eligibility. Based on the order status, it automatically approves or routes the request for manual review. Customers and internal teams are notified accordingly, and all actions are logged in Google Sheets. Step-by-step Capture refund requests from email** Gmail Trigger – Detects unread emails with “Refund Request” in the subject. AI Agent2 – Extracts order ID and reason using AI. Groq Chat Model – Provides the language model used by the AI agent. Code in JavaScript – Converts AI output into structured JSON. Fetch order details from Shopify** Get an order – Retrieves order information using the extracted order ID. Evaluate refund eligibility** If – Checks whether the order status is “Delivered” to allow auto-approval. Handle responses and logging** Send a message to customer – Sends approval confirmation if eligible. Send a message to the team – Notifies team for manual review cases. Send a message to customer for "Pending" Status – Updates customer about manual review. Logs to Sheet – Records all refund actions and details in Google Sheets. Why use this? Automates repetitive refund handling tasks and reduces workload Improves customer experience with faster response times Ensures consistent decision-making based on order status Keeps a centralized log for auditing and reporting Easily extendable with additional validation rules or integrations

IntermediateManual Trigger

Publish AI-written newsletters and LinkedIn posts from WordPress with Gemini, Google Sheets and Gmail

How it works This workflow fetches the latest blog post from a WordPress API and checks against a Google Sheets tracker to prevent duplicate processing. If a new post is found, the workflow updates the tracker and cleans the blog data. The cleaned content is then sent to a Gemini-powered AI agent to generate a newsletter and LinkedIn teaser. Finally, the workflow distributes the content via LinkedIn and Gmail to subscribers. Step-by-step Detect new blog content** Schedule Trigger – Runs the workflow automatically at intervals. HTTP Request – Fetches the latest blog post from WordPress. Last ID – Retrieves the last processed blog ID from Google Sheets. If – Compares IDs to check if the blog is new. Update Last ID – Updates the sheet with the latest blog ID. Clean and generate AI content** data cleanse – Cleans HTML, extracts title, content, and image. AI Agent2 – Generates newsletter and teaser content. Google Gemini Chat Model – Provides AI model for content generation. Distribute content across channels** Format Response – Parses and structures AI output. Create a post – Publishes content on LinkedIn. Email List – Fetches subscriber emails from Google Sheets. Loop Over Items – Iterates through each recipient. Send Email – Sends HTML newsletter via Gmail. Why use this? Automates end-to-end blog promotion workflow Prevents duplicate publishing using ID tracking Uses AI to generate engaging content instantly Saves time on manual posting and emailing Easily scalable for growing audiences

IntermediateManual Trigger

Score and auto-reply to new leads with OpenAI and Gmail

++Who is this for++ Small business owners, freelancers, and agencies who receive inbound leads through a web form and want instant, personalized follow-up — without manually reading every submission. ++What it does++ When someone fills out your lead intake form, this workflow instantly: Scores the lead 1-100 using OpenAI based on budget, project fit, and clarity Classifies them as Hot, Warm, or Cold Sends a personalized email reply that references what they actually wrote Logs everything to Google Sheets with the score and AI reasoning Hot leads get an enthusiastic reply with a calendar booking link. Warm leads get a helpful response with suggested next steps. Cold leads get a polite acknowledgment. Every lead gets a response within seconds. ++How to set up++ Fill in the "Configure Your Settings" node with your business name, email, calendar link, and description Connect your Gmail and Google Sheets credentials Add your OpenAI API key Create a Google Sheet with the column headers listed in the workflow's sticky notes Paste your Sheet URL into the "Log Lead with Score" node Activate the workflow and share the form URL Requirements n8n account (cloud or self-hosted) OpenAI API key Gmail account (OAuth2) Google Sheets (one blank sheet) How to customize Edit the OpenAI system prompt to adjust scoring criteria for your industry Modify the tier thresholds (currently Hot 70+, Warm 40-69, Cold 0-39) Customize the email tone by editing each Gmail node Add or remove form fields to match your intake need

BeginnerManual Trigger

Automatically solve reCAPTCHA v2 with CapSolver

reCAPTCHA v2 Solver (CapSolver + n8n) How it works • Receives reCAPTCHA v2 solving requests via webhook • Sends tasks to CapSolver and returns solved tokens in real time • Runs a scheduled check to validate solving performance • Submits tokens to target endpoint and verifies success/failure • Supports manual trigger for quick testing and debugging Set up steps • Add your CapSolver API key to all CapSolver nodes • Configure the webhook endpoint for incoming requests • Adjust target website URL and site key if needed • Review or modify the hourly schedule trigger • Run a quick manual test to confirm everything works ⏱️ Setup time: ~5–10 minutes

BeginnerManual Trigger

Why Choose Us?

AI-Powered n8n Templates

GPT-4 powered intelligent engine that generates custom n8n templates from simple descriptions

Premium Quality n8n Templates

Every n8n template is tested and verified to ensure reliability and practical automation value

One-Click Import

Support one-click import to n8n, start using immediately

Ready to Get Started?

Start using AI to generate n8n templates now, or explore our comprehensive n8n templates library with 7000+ proven workflows

Start AI Generation Browse Templates