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.

14452+

Templates

50+

Integrations

50k+

Downloads

Latest n8n Templates

Freshly updated automation workflows to keep your n8n stack current

View All

Log recent YouTube videos to Google Sheets with RecentReborn and Telegram alerts

Quick overview YouTube removed the 'Upload Date: Last Hour' filter. This workflow fills that gap, running hourly to search YouTube via the RecentReborn Search API, deduplicating results, and logging them to Google Sheets, with Telegram alerts on failure. How it works Runs every hour on a schedule (or manually for testing). Reads your comma-separated search terms and splits them into individual queries with shared settings like upload window and video type. Calls the RecentReborn Search API for each query to retrieve recent YouTube video results uploaded within the last hour. Validates that each API response includes a results list and sends a Telegram message when the request fails or the response format is unexpected. Deduplicates videos by URL using workflow static data so only previously unseen videos from this run continue. Appends new videos to Google Sheets or updates existing rows by matching on the url column. Setup Create a RecentReborn API key and add it as an HTTP Bearer Auth credential used by the RecentReborn search request. Connect your Google Sheets OAuth credential and set the target spreadsheet and sheet tab for the append/update action. Connect a Telegram bot credential, set your Telegram chat ID in the workflow settings, and use it to receive error alerts. Update the search terms (comma-separated) and optional filters (upload window, type, duration) in the configuration step, then run once manually before enabling the hourly schedule. Requirements A RecentReborn API account (app.recentreborn.com) with an API key Additional info Visit https://recentreborn.com/developers for more tutorials and templates.

BeginnerManual Trigger

by Felix M

Extract recruiting call insights from NUACOM with Gemini and HubSpot

Quick overview This workflow triggers on NUACOM calls, fetches the AI-generated transcript, and uses Google Gemini to extract structured recruiting insights. It writes the Q&A back to the NUACOM call notes and updates a HubSpot contact property with the candidate’s salary expectation. How it works Triggers when a NUACOM call event is received for the configured extension. Checks the call duration and continues only if it is longer than 5 seconds. Waits 30 seconds, then retrieves NUACOM’s AI-generated call analysis including the transcription. Sends the transcript to Google Gemini with instructions to answer 11 recruiting questions and return a JSON-structured result. Reformats the structured answers into a simple JSON object and adds a formatted note to the NUACOM call with the extracted details. Searches HubSpot for a contact whose phone number matches the call recipient and, if the salary expectation field is empty, updates the contact with the extracted salary expectation. Setup Add your NUACOM API credentials, set the extension to monitor, and ensure NUACOM AI Call Analysis is enabled for your calls. Configure access to Google Gemini (Google PaLM/Gemini credentials via n8n’s AI integration) for the AI Agent. Add your HubSpot OAuth2 credentials and ensure the custom contact property ain8n_salary_expectation exists (and adjust the property name if yours differs).

BeginnerManual Trigger

Log German VAT-ready expense receipts via Telegram with OpenAI and Google Sheets

Quick overview This workflow lets you send receipt photos to a Telegram bot, extracts key fields with OpenAI Vision, stores the image in Google Drive, and logs a German tax-ready expense row to Google Sheets with deductible amount and VAT handling, including optional voice-note refinements and duplicate detection. How it works Triggers on incoming Telegram messages or button callbacks and allows only chat IDs listed in the workflow’s Config. When you send a receipt photo, it downloads the image from Telegram and uses OpenAI (GPT-4o-mini vision) to extract structured receipt data such as merchant, date, gross/net, VAT, currency, and payment method. If the receipt is unreadable or missing required fields, it sends an error back to Telegram asking for a clearer photo. For readable receipts, it creates a descriptive filename, uploads the image to Google Drive, and calls OpenAI again to classify the expense into a cost center with German tax notes, deductibility, and VAT recoverability flags. It calculates deductible amounts and VAT fields in-code using German rules (for example, net vs. gross deduction base and VAT blocking cases), generates a tracking ID, and checks Google Sheets for likely duplicates. If a duplicate is suspected, it posts a Telegram warning with “Add anyway” or “Ignore”; otherwise it appends the row to the Ausgaben tab in Google Sheets and sends a confirmation message with buttons. When you tap buttons or reply with a voice note, it can prompt for context, transcribe the voice note with OpenAI Whisper, reclassify/update the existing Google Sheets row, or delete the row and edit the Telegram message accordingly. Setup Create a Telegram bot with BotFather, add the Telegram credentials in n8n, and start a chat with the bot so it can receive your messages. Add an OpenAI API credential (used for both GPT-4o-mini vision/classification and Whisper transcription). Add Google Sheets OAuth credentials and select a spreadsheet that contains an Ausgaben sheet with the columns expected by the workflow’s mapping. Add Google Drive OAuth credentials and choose the target Drive and folder where receipt images should be uploaded. In the ⚙️ Config node, set owner_chat_ids to your Telegram chat ID(s) and set sheet_url to the Google Sheet link used by the “View Sheet” buttons.

Score B2B account hiring signals with OpenAI, JobsPipe MCP, Sheets and Slack

Quick overview This workflow opens an n8n chat where an OpenAI-powered agent uses the JobsPipe MCP server to answer questions about who is hiring, returning job-posting-backed results with source links and optional monitoring signals. How it works Receives a message in an n8n chat trigger. Applies default search context such as your persona, default country, and the maximum number of jobs to return per search. Uses an OpenAI chat model and the last 10 chat messages as memory to interpret the user’s question. Calls JobsPipe MCP tools (for example, searching postings, fetching full job details, detecting company tech stacks, or creating monitoring signals) to gather live job data. Responds in the chat with results that cite the original job posting URLs and notes when no matches are found. Setup Create a free JobsPipe account at jobspipe.dev. In the JobsPipe MCP node, create an MCP OAuth2 credential named "JobsPipe MCP (OAuth)": Server URL https://mcp.jobspipe.dev, Resource https://mcp.jobspipe.dev/mcp, dynamic client registration on, then click Connect and sign in. An API key also works: switch to Header Auth with Authorization: Bearer jp_live_... Add an OpenAI credential named "OpenAI account" (or pick another chat model), then open each node once after importing so n8n attaches the credentials. Update the default persona, country, and max_jobs_per_search values to match your use case, then open the chat and start asking hiring-market questions. Requirements A JobsPipe account (the free tier includes 1,000 credits; each job returned costs 1 credit) and an OpenAI API key Customization Edit the agent's system prompt or the Set node to focus on a role, region or industry, raise max_jobs_per_search, or swap the chat model Additional info Ask the agent to watch a search and it can create a JobsPipe Signal that alerts you when new matching jobs appear. Docs: https://docs.jobspipe.dev/integrations/n8n

Intermediate

Monitor website HTTPS and certificate health from Google Sheets with Slack and Gmail alerts

Quick overview This workflow runs weekly (or manually) to read a list of client websites from Google Sheets, check each site’s HTTPS and certificate status via weio.ai, write results back to the sheet, and send Slack and Gmail alerts for new or ongoing problems. How it works Runs every Monday at 08:00 (or when executed manually) and loads alert thresholds and the digest email address. Reads website rows from Google Sheets and keeps only rows with a non-empty website and not marked inactive. Calls the weio.ai HTTPS check API for each website (batched one at a time with a delay) to evaluate reachability, HTTPS redirect behavior, and certificate validity/expiry. Classifies each result as ok, warning, or critical, compares it to the previous status stored in the sheet, and timestamps the check. Updates the matching rows in Google Sheets with the latest severity and HTTPS status details. Sends an urgent Slack message for any critical issue that is new or has changed since the last run, and emails a single Gmail digest listing all non-ok sites. If the workflow execution fails, posts an error notification to Slack via an Error Trigger. Setup Create a Google Sheet with columns like website, active (set to "no" to skip), owner (optional), and output columns severity, https_status, https_detail, cert_expires, and checked_at. Add Google Sheets OAuth credentials and select the target document and sheet in both the read and update steps. Add a Slack credential and choose the channel for both the urgent alert and the workflow-failed notification. Add a Gmail OAuth credential for sending the email digest. Update the Settings values (email_to, warn_days, critical_days) to match your recipients and certificate warning windows, and (optionally) add an Authorization bearer token to the weio.ai request if you need higher throughput. Requirements Google Sheets, Slack and Gmail accounts connected as n8n credentials. No account is needed for the weio.ai HTTPS check: the free tier allows 5 checks a minute, and the workflow spaces requests 15 seconds apart (about 240 sites an hour). Customization Change warn_days and critical_days in Settings to move the expiry thresholds. For bigger lists, add a Header Auth credential (Authorization: Bearer ) on Check HTTPS and shorten the batch interval. Additional info API docs and keys: https://weio.ai/services/site-check-api.html?utm_source=n8n&utm_medium=templates&utm_campaign=https-watch . Built and maintained by Weio, Inc.; AI operators did most of the work.

Approve vendor invoices from Gmail with Claude, Google Sheets, Slack and QuickBooks

Quick overview Turn vendor invoices from Gmail into approved QuickBooks bills. Claude reads each PDF, code checks it against your vendors, POs, log and QuickBooks, Slack approvers decide, and every outcome is logged, labelled and followed up. How it works A Gmail trigger catches each email with a PDF and calls this workflow once per email, so every invoice runs and waits for approval on its own. The PDF is saved to a Google Drive folder, then one Anthropic API call reads it and returns vendor, invoice number, dates, amounts, PO number, bank details and line items as fixed JSON. It reads your Vendors, Purchase orders and Invoice log tabs and searches QuickBooks Online for a bill with the same number. Code checks the vendor, sender domain, bank details, arithmetic, open PO balance and duplicates, then picks auto-approve, approve or hold. Small, clean, PO-matched invoices approve themselves. Others go to a Slack approver by direct message with a time limit, plus a second approver above your limit. Whoever raised the PO never approves its invoice. Every outcome is logged and posted to your AP channel. Approved invoices become QuickBooks bills with one line per invoice line. Changed bank details alert finance and never reply to the sender. Fixable problems get a reply asking the vendor for a corrected invoice, and Gmail labels show the result. Each weekday morning a digest lists approved bills coming due and invoices still waiting on a person. An error trigger posts any failure to Slack. Setup Create a Google Sheet with the tabs Vendors, Purchase orders and Invoice log, using the column headers in the canvas note, and add each vendor's QuickBooks vendor ID and expense account ID. Fill in the Settings node: sheet ID, Drive folder ID, Slack user and channel IDs, Gmail label IDs, QuickBooks company ID, and your approval limits. Connect Gmail, Google Drive, Google Sheets, Slack and QuickBooks Online credentials, and add a Header Auth credential named x-api-key with your Anthropic API key. Choose this workflow as its own error workflow in Workflow settings. Test from Each invoice starts here with the pinned sample (run it twice to see the duplicate hold), then unpin Read the invoice with Claude and activate. Requirements Gmail, Google Drive, Google Sheets, Slack and QuickBooks Online accounts, plus an Anthropic API key Customization Change limits and tolerances in Settings, add your own checks in Check and route, or point Create the bill in QuickBooks at Xero or another accounting API. Additional info Built by Amplence (amplence.com), an n8n automation agency. The checks and the design choices behind them: amplence.com/blog/n8n-invoice-approval-workflow

Orchestrate sequential Notion task execution for participants with webhooks

Quick overview This workflow retrieves all child blocks from a Notion page or block ID, handling Notion API pagination by recursively calling itself until all content is collected. How it works Receives an input containing the Notion page or block ID (and optional accumulated results and cursor for pagination). Calls the Notion API to fetch up to 100 child blocks for the given block ID, using the provided cursor when present. Checks the Notion response field has_more to determine whether additional pages of blocks exist. If more blocks exist, re-runs the same workflow with next_cursor and the blocks accumulated so far to continue pagination. When no more pages exist, merges all retrieved blocks into a single results array and outputs the consolidated content. Setup Add a Notion API credential and ensure it has access to the target page or block. Create an n8n variable named Notion_Version and set it to the Notion API version you want to use. In the “Buscar Próxima Página” step, select this same workflow so it can call itself recursively.

BeginnerManual Trigger

Reply to missed calls and book appointments with Twilio, Google, and GPT-4o

Quick overview Never miss a lead again: this workflow texts back missed callers via Twilio SMS and turns voice AI call summaries into Google Calendar bookings — with Sheets logging and owner alerts. How it works Twilio call-status webhooks arrive here; missed inbound calls get an immediate SMS reply, are logged to Google Sheets, and trigger an owner alert. Your voice AI posts its end-of-call summary; the workflow extracts caller name, phone, service and time with AI and builds the event times. The workflow creates a Google Calendar event, texts the caller a confirmation, logs the call, and notifies the owner. Setup Connect your Twilio, Google Sheets, Google Calendar and OpenAI credentials. Fill the two CONFIG nodes (business name, numbers, sheet ID, calendar ID, booking link). Point your Twilio number's voice webhook at the workflow's production URL. Point your voice AI's end-of-call report at the second webhook. Create the MissedCalls and VoiceCalls sheet tabs. Requirements Twilio account with a phone number, a Google account, an OpenAI API key, and — for the voice layer — a Vapi or Retell voice agent. Customization Edit the SMS copy in the Twilio nodes, change the CONFIG fields per client, swap the Sheets logger for your CRM, or extend the AI extraction schema with extra fields. Additional info Who's it for: Local service businesses — plumbers, clinics, salons, contractors — that lose jobs when calls go to voicemail, and anyone running a voice AI receptionist (Vapi, Retell) who wants bookings to land in the calendar automatically.

IntermediateManual 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