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.

11773+

Templates

50+

Integrations

50k+

Downloads

Latest n8n Templates

Freshly updated automation workflows to keep your n8n stack current

View All

Send weekly overdue invoice reminders with Google Sheets and Gmail

Quick Overview This workflow runs every Monday at 08:00, reads invoices from Google Sheets, filters for unpaid invoices with no prior follow-up and more than 7 days overdue, sends an HTML reminder email via Gmail, and updates the sheet to mark the invoice as followed up. How it works Runs every Monday at 08:00 on a schedule. Reads all invoice rows from a Google Sheets spreadsheet. Keeps only invoices where the status is “Impayé” and the “Date de relance” field is empty, then calculates the number of days overdue from the invoice date. Filters to invoices that are more than 7 days overdue. Sends a formatted HTML payment reminder email via Gmail with the invoice date, amount, and days overdue. Updates the matching Google Sheets row to set the status to “Relancé” and writes today’s follow-up date. Setup Add Google Sheets credentials and ensure the target spreadsheet contains columns like Statut, Date de relance, Date_Facture, Client, and Montant. Add Gmail credentials for the mailbox that sends reminders. Update the Google Sheets document URL/sheet selection and set the recipient address in the Gmail “sendTo” field (and optionally adapt the subject/body text).

BeginnerManual Trigger

by nexum

Monitor website changes with PolyDoc screenshots and email alerts

Quick Overview This workflow checks a website URL every 6 hours, detects content changes by hashing the normalized HTML, and when a change is found it uses PolyDoc to capture a full-page screenshot and emails the PNG as an attachment. How it works Runs every 6 hours on a schedule. Sets the target URL to monitor and fetches the page HTML with an HTTP request. Normalizes the HTML (removing scripts/styles/comments), hashes it, and compares it with the previous run stored in workflow static data. If the hash changed, PolyDoc captures a full-page PNG screenshot of the URL. Sends an email with the screenshot attached and the monitored URL in the subject and body. Setup Update the monitored website URL in the Settings step. Add your PolyDoc API credentials to the PolyDoc screenshot step. Configure an SMTP email credential and set the to/from email addresses in the email step.

BeginnerManual Trigger

Fetch and parse Amazon SP-API reports into structured TSV rows

Quick Overview This workflow manually requests an Amazon Selling Partner (SP-API) report, polls until it is ready, downloads the report document, optionally decompresses it if it is GZIP, and parses the TSV contents into one n8n item per row. How it works Starts when you run the workflow manually. Uses Login with Amazon (LWA) to exchange your refresh token, client ID, and client secret for an access token. Calls the Amazon SP-API Reports API to create a report for the configured report type and marketplace. Polls the Amazon SP-API until the report processing status is DONE (or errors if it fails or times out). Fetches the report document metadata and downloads the report file from the provided URL. If the document is GZIP-compressed, decompresses the file and then parses the TSV into structured JSON items, outputting one item per row. Setup Create and authorize Amazon SP-API (Login with Amazon) credentials, then fill in the refresh_token, client_id, and client_secret values in the Config step. Set the correct SP-API endpoint region (EU/NA/FE), report_type, and marketplace_ids values in the Config step. If you want to store or route results, add downstream nodes after the parsed rows output to send the items to your database, spreadsheet, or other destination.

BeginnerManual Trigger

Create work4all incoming invoices from Microsoft Outlook supplier emails

Quick Overview This workflow polls a Microsoft Outlook folder for new supplier emails, sends each message to a companion n8n sub-workflow that creates an incoming invoice in work4all, and then categorizes the email (green/yellow/red) and emails errors via Outlook. How it works Runs every minute on a schedule. Fetches all emails from a specified Microsoft Outlook folder that are not already categorized as Red or Green, downloading any attachments. Sends each email to a companion sub-workflow that extracts invoice data from attachments and creates the incoming invoice in work4all. If the sub-workflow returns errors, sends an error notification email via Microsoft Outlook and categorizes the original message as Red. If no errors occur, categorizes the message as Green when booking is clean, or as Yellow + Green when a supplier was created or an account/tax key was set automatically. Setup Import and publish the companion workflow "Create a work4all incoming invoice from email attachments using AI" and select it in the Execute Workflow step. Add Microsoft Outlook credentials with permission to read the target mailbox and send emails. Update the Outlook folder ID to monitor and ensure the mailbox has the categories "Red category", "Green category", and "Yellow category". Set the error notification recipient address(es) in the configuration value (errorRecipients). Adjust the schedule interval if you don’t want it to poll every minute.

BeginnerManual Trigger

Publish weekly SMB blog posts with Perplexity, Claude, Gemini, Supabase, and Gmail

Quick overview This workflow runs weekly to generate, research, write, illustrate, and publish a new blog post by combining Supabase (content + storage), Perplexity (topic + research), Anthropic Claude (writing), Google Gemini (cover image), and Gmail (notification). How it works Runs every Friday at 10:00 (cron: 0 0 10 * * 5). Fetches titles of already published posts from Supabase and builds a rotating topic focus that avoids repeating prior angles. Uses Perplexity to propose one fresh, SEO-relevant blog topic and then research it with trends, examples, and SMB-focused insights. Sends the topic and research notes to Anthropic Claude to write a complete post with title, excerpt, meta description, category, read time, and HTML body. Parses the generated text into structured fields, generates a slug, and prepares a published blog post record. Uses Google Gemini to generate a 16:9 cover image, uploads it to Supabase Storage, and attaches the public cover image URL to the post. Inserts the finished post into the Supabase blog_posts table with status set to published and emails the team via Gmail with the publication details. Setup Create a Supabase project with a blog_posts table and a Storage bucket/path for covers (social-images/blog-covers), then replace YOUR-PROJECT.supabase.co in both Supabase HTTP requests. Add credentials for Supabase, Perplexity, Anthropic (Claude), Google Gemini (Google PaLM/Gemini), and Gmail OAuth2. Update the notification recipients (To/CC) in the Gmail message node. (Optional) Replace YOUR-COST-LOG-SUBWORKFLOW-ID with your cost-logging workflow ID or delete the cost-logging sub-workflow calls. Adjust the schedule cron expression if you want a different publish cadence. Requirements Supabase project: a blog_posts table plus a public Storage bucket for cover images Perplexity API key (topic + research) Anthropic Claude API key (writing) Google Gemini key (cover image) Gmail OAuth, or any email node, for the notification Customization Rewrite the Claude prompt to match your brand voice, tone, and post length Change the schedule cron to publish daily, weekly, or on demand Swap Gmail for Slack, Telegram, or Outlook to get notified your way Publish to your own CMS or WordPress instead of Supabase by editing the publish node Tweak the Gemini cover prompt and aspect ratio for your brand look Add a human approval step before publishing if you want a person in the loop Additional info The topic picker reads your already-published titles before choosing the next one, so your blog keeps a varied, non-repetitive editorial calendar on autopilot. The cost-logging nodes are optional and safe to delete.

Manage inventory reorders with Google Sheets, Slack, and Gmail

Quick Overview This workflow monitors inventory from Google Sheets on a schedule, calculates reorder quantities using vendor lead times, logs pending reorders back to Google Sheets, and posts grouped reorder requests to Slack, then sends vendor reorder emails via Gmail when an authorized Slack user approves. How it works Runs on a schedule and reads product inventory and vendor catalog data from Google Sheets. Calculates stock runway and a reorder quantity per product using recent sales and vendor average delivery time. Filters to only items that need reordering and aggregates reorder lines into a vendor-level request. Checks the existing reorder log in Google Sheets to avoid reordering items that are pending/sent or were completed within the last 14 days, then groups remaining items by vendor. Writes each vendor reorder request to a Google Sheets reorder log with status set to pending and posts a formatted restock notification to a Slack channel. Triggers on a Slack reaction event, verifies the reacting user matches the configured approver, extracts the Reorder ID from the Slack thread, and looks up the matching row in Google Sheets. Sends the reorder email to the vendor via Gmail and updates the reorder status in Google Sheets to SENT. Setup Configure a Google Sheets Service Account credential and set the document IDs and sheet names for the inventory sheet, vendor catalog sheet, and reorder log sheet. Configure a Slack credential, set the Slack channel ID for posting reorder alerts, and enable the Slack trigger on the channel where approvals happen. Replace enter-your-authoritive-person-slack-id-here with the Slack user ID allowed to approve reorder emails. Configure a Gmail OAuth2 credential and update the email template fields (for example, company name) as needed. Ensure your reorder log Google Sheet includes the columns used by the workflow (for example, product_reorder_id, Vendor ID, Email Address, products_with_quantity, status, and reorder_date).

Beginner

Book, reschedule and confirm WhatsApp appointments with Claude and Sheets

Quick overview This workflow receives WhatsApp messages via a Meta webhook, uses Anthropic Claude to detect booking intents and extract appointment details, writes updates to Google Sheets, and sends a confirmation or error reply back to the customer on WhatsApp. How it works Receives incoming WhatsApp messages through a Meta webhook endpoint and normalizes key fields like sender phone number, display name, message text, and timestamps. Filters out empty messages and sends the text to Anthropic Claude to classify the intent (book, reschedule, confirm, or unknown) and extract structured appointment details. Validates the request based on intent, including required fields and simple rules like weekday-only appointments and business hours. Appends a new row to the Google Sheets Appointments tab for valid bookings, or updates the appointment status/date/time in Google Sheets for reschedules and confirmations. Builds a personalized WhatsApp reply message describing the result (success, required missing details, or supported actions). Sends the reply back to the customer via the WhatsApp Cloud API and appends the interaction details to the Google Sheets ActivityLog tab. Setup Create a Meta WhatsApp Business (Cloud API) app, register the workflow webhook URL as the WhatsApp callback URL, and complete webhook verification. Add an Anthropic API credential in n8n and ensure the Anthropic Claude model node is connected to your account. Add a Google Sheets OAuth2 credential in n8n and create a spreadsheet with Appointments and ActivityLog tabs and the expected header columns. Replace YOUR_SHEET_ID in all Google Sheets HTTP request URLs with your spreadsheet ID. Replace YOUR_PHONE_NUMBER_ID in the WhatsApp API URL and set the WhatsApp Authorization bearer token (preferably via an n8n credential) in the request headers.

BeginnerManual Trigger

Grade system prompts in Google Sheets with a Gemini LLM judge

Quick overview This workflow manually grades a system prompt by running it against a sample user task with Google Gemini, then has a second Gemini judge score the prompt (1–10) and write the grade and reason back to Google Sheets. How it works Starts when you run the workflow manually. Reads the prompt list from a Google Sheets spreadsheet and keeps only the last row as the system prompt under test. Sets a fixed sample customer-support task and sends it to a Google Gemini-powered agent using the sheet prompt as its system instructions. Sends the original prompt, the sample task, and the agent’s response to a second Google Gemini judge that returns a structured grade and short justification. Updates the same Google Sheets row with the returned grade and reason. Setup Connect a Google Sheets OAuth2 credential with access to the target spreadsheet. Connect a Google AI Studio (Gemini) credential for the candidate model, grader model, and parser-fixer model. Ensure your sheet has columns for at least prompt, grade, and reason, and that the workflow can match rows using the row_number field. Update the spreadsheet ID/sheet and edit the sample task text if you want to test prompts against a different scenario.

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