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.

14239+

Templates

50+

Integrations

50k+

Downloads

Latest n8n Templates

Freshly updated automation workflows to keep your n8n stack current

View All

Optimize RFx supplier awards with Groq, Notion, and Slack alerts

Quick overview This workflow receives an RFx completion webhook, scores suppliers against cost, risk, lead time, and rating constraints, generates award scenarios, and uses Groq (LangChain agent) to produce a structured procurement recommendation, then stores results in Notion and posts success or failure alerts to Slack. How it works Receives an HTTP POST webhook with an RFx ID, a suppliers array, and optional evaluation constraints. Validates that at least one supplier is provided, and if not, posts an error to Slack and returns an “invalid input” webhook response. Filters and scores suppliers using weighted cost, risk, lead time, and rating factors, then selects three scenarios (best cost, lowest risk, and balanced) and returns a ranked supplier list. Sends the scenario data to a Groq-hosted LLM via a LangChain agent to generate a JSON-only executive summary, insights, trade-off analysis, and a final recommendation. Parses and validates the AI JSON output, and if it fails, posts an error to Slack and returns an “AI error” webhook response. Stores the recommendation and insights in a Notion database, posts a completion message to a Slack channel, and returns a success response to the original webhook request. Setup Copy the webhook URL from the Webhook trigger and configure your RFx system to POST rfx_id, suppliers[] (with cost, risk, lead_time, rating), and optional constraints to that endpoint. Add Groq API credentials for the LangChain Groq Chat Model used by the AI analysis step. Add Notion credentials and select the target database, ensuring it has properties for RFx ID, Best Supplier, Executive Summary, Cost Insight, Risk Insight, Trade-off, and Final Recommendation. Add Slack credentials and set the target channel for both success and failure notifications. Review and adjust the scoring weights and constraint defaults in the supplier scoring logic to match your award criteria. Additional info Customization Change scoring weights in code node Add new constraints (e.g., location, certifications) Modify AI prompt Customize Slack message format Extend Notion fields Add-ons Email alerts ERP integration Approval workflows Historical supplier tracking Dashboard reporting Use Cases RFQ supplier selection Vendor comparison automation Risk-based sourcing Procurement analytics AI-driven decision making Troubleshooting Guide | Issue | Possible Cause | Solution | | -------------------------- | ----------------------- | ------------------------------------------ | | No suppliers processed | Empty suppliers array | Ensure suppliers are passed correctly | | Workflow stops early | Validation failure | Check webhook payload | | Incorrect scoring | Missing supplier fields | Ensure cost, risk, lead_time, rating exist | | AI output invalid | Improper JSON response | Adjust AI prompt formatting | | Slack not sending messages | Invalid credentials | Reconnect Slack API | | Notion not saving data | Wrong database mapping | Verify database fields | | API returns error | AI validation failed | Check AI output node | | Unexpected results | Constraints too strict | Relax constraints | Need Help? WeblineIndia can help you build advanced automation workflows, integrate AI, scale procurement systems and provide n8n workflows developers for hire. Contact us to build smarter automation solutions.

IntermediateManual Trigger

by WeblineIndia

Scrape Google Maps places to Google Sheets with Apify

Quick overview This workflow takes a city and search query, scrapes matching Google Maps places using Apify’s Google Maps Scraper, and writes the results (name, rating, reviews, category, address, website, and link) into a newly created Google Sheets spreadsheet. How it works Starts when you manually execute the workflow. Sets the search parameters (city, query, and maximum number of places to collect). Creates a new Google Sheets spreadsheet with a “Places” tab named after the search. Runs the Apify Google Maps Scraper actor to collect places matching the query in the specified city. Appends one row per place to Google Sheets with key details including rating, reviews, address, website, category, and Google Maps URL. Setup Open Scrape Google Maps with Apify and connect your Apify account with OAuth2. A free Apify account is enough to run the Google Maps Scraper Actor (compass/crawler-google-places). Open Create the spreadsheet and sign in with Google. Add places to the sheet reuses the same Google Sheets credential. In Search settings, set city, query, and maxPlaces. Click Execute workflow, then open spreadsheetUrl in the output of Create the spreadsheet to see your results. Requirements An Apify account (the free plan works). A Google account with access to Google Sheets. Customization Raise maxPlaces for longer lists. Add a Schedule Trigger to refresh the sheet every week. Swap in any other Actor from Apify Store.

BeginnerManual Trigger

Book home care assessments by phone with Vapi, Google Gemini and Google Calendar

Quick overview This workflow provides two Vapi webhook tools to check care assessment availability and book appointments, using Google Calendar for scheduling, Google Gemini to translate busy times into human-friendly availability, Google Sheets to log enquiries, and SMTP email to send booking confirmations. How it works Receives a POST webhook from Vapi with a requested assessment date to check availability. Pulls that day’s busy time ranges from Google Calendar in the configured timezone. Sends the busy slots to Google Gemini, which returns plain-language available 1-hour booking windows (Mon–Sat, 9am–5pm) or refuses Sundays. Responds to Vapi with the availability text mapped to the original tool call ID. Receives a second POST webhook from Vapi containing the confirmed booking details. Parses the booking payload defensively across multiple Vapi tool-call formats, normalizes the contact and date/time fields, and creates a 1-hour event in Google Calendar. Appends the enquiry details to Google Sheets, emails a confirmation to the provided address via SMTP, and returns a success message to Vapi for the voice agent to read. Setup In Vapi, create two server tools that point to this workflow’s production webhook URLs (one for availability and one for booking) and ensure the tool arguments match the fields used by the workflow. Add a Google Calendar credential in n8n and select the target booking calendar in both calendar steps (adjust the timezone if you are not using Europe/London). Add a Google Gemini (Google AI) credential for the chat model used to generate human-readable availability. Add an SMTP email credential, set the From address, and update the confirmation email branding/content as needed. Add a Google Sheets credential, create an enquiries spreadsheet with the expected columns, and select the document, sheet, and any required IDs in the append step. Requirements A Vapi account with an assistant configured with two server tools — check_assessment_availability (argument: date) and book_care_assessment (arguments listed on the canvas) A Google Calendar credential and a booking calendar (selected in both calendar nodes) A Google Gemini (Google AI) API key for the availability analysis An SMTP credential (e.g. your workspace mailbox) for the confirmation emails A Google Sheet for enquiry logging with the headers listed on the canvas Customization Edit working days, hours and slot length in the AI agent's system message (default Mon–Sat, 9am–5pm, 1-hour assessments) Replace the agency name, colours and footer in the confirmation email HTML Add or rename booking fields — update the Vapi tool, the parser and the sheet columns together Swap Gemini for any chat model n8n supports Adapt the two-tool pattern to any appointment business — clinics, salons, surveyors, trades call-outs Additional info About the creator: Built and maintained by Ali Amin, founder of IhsanOps (https://ihsanops.ai) — a UK AI automation consultancy building voice agents and automations for SMEs. This template is based on a production voice-booking system built for a UK home care provider. Want it adapted to your business — different booking rules, CRM integration, SMS confirmations? Email ali@ihsanops.ai or see https://linkedin.com/in/ali-tm-amin.

Answer visitor questions and grow the FAQ with OpenAI, Google Sheets and Gmail

FAQ chatbot that grows its own answers — with owner approval Who it's for: site owners and support leads who want a public chat that answers from a known FAQ, never hallucinates, and gets smarter every week. How it works Visitors chat via the hosted webchat (Chat Trigger). The bot loads the FAQ sheet from Google Sheets and OpenAI answers only from it. Every turn is routed three ways: answered (reply sent), unanswered (logged to the Unanswered tab and the owner notified by Gmail), or lead (visitor left an email — captured in Leads and the owner notified). Repeats never duplicate rows. Every Monday a second lane clusters the unanswered log, ranks gaps by frequency, has OpenAI draft candidate FAQ entries, emails the owner a digest, and appends proposals to FAQ-Pending. The owner copies approved rows into FAQ — the bot only learns what a human signs off. Setup Click Test workflow — the demo lane runs six visitor turns (answerable, unanswered, lead, empty, repeat, bad AI answer) through every route with zero credentials. Attach credentials: Google Sheets, Gmail, OpenAI. Press play on the SETUP node (Lane D) — it creates the spreadsheet with all four tabs, headers and example rows, then prints the spreadsheet_id. Open the Workflow Config node and paste the id plus your owner_email. Then delete the setup lane, activate the workflow and embed the Chat Trigger's public URL in your site. Note: the Google Sheets and Gmail nodes are enabled — once credentials are attached they write real rows and send real emails.

BeginnerManual Trigger

Answer currency rate questions from Gmail and chat with Gemini and Frankfurter API

Quick Overview This workflow answers exchange-rate questions coming from Gmail or an n8n chat trigger using a Google Gemini AI agent that calls the Frankfurter exchange-rate API, caches successful rate responses in n8n Data Tables to avoid repeated model calls, logs usage metrics, and replies back on the originating channel. How it works Triggers when a new Gmail message matching the exchange-rate search filter arrives or when an n8n chat message is received. Normalizes incoming email and chat messages into a common format (session ID, user text, source channel, sender email) and processes them one at a time. Extracts two ISO 4217 currency codes from the message to build a per-day cache key and looks up a previously saved response in an n8n Data Table. If a fresh cached response exists (within the configured TTL), uses it directly without calling the AI model. If there is no fresh cache hit, runs a Google Gemini-powered AI agent that calls the Frankfurter API to fetch the latest reference exchange rate and generates a one- or two-sentence plain-text reply. Stores valid rate answers back into the cache, logs the query details (source, pair, cache hit, latency) to a second Data Table, and replies via n8n chat or Gmail depending on where the question originated. Setup Add credentials for Gmail OAuth2 (for the Gmail trigger and email replies) and a Google Gemini (PaLM) API credential for the chat model. Create or select two n8n Data Tables: one for the rate cache with columns cache_key (string), pair (string), response (string), cached_at (number) and one for the query log with columns logged_at (string), source (string), pair (string), cache_hit (boolean), latency_ms (number). Update the Data Table selections in the cache lookup/save nodes and the log node, then review the Config values (cache TTL, email subject, fallback message) and adjust the Gmail search filter to match the senders and subjects you want to handle.

Beginner

Approve or reject Inistate entries via email using SMTP

Quick overview This workflow triggers when an Inistate entry changes into a chosen approval state, emails an approver with Approve/Reject buttons via SMTP, and then performs the corresponding Inistate activity if the entry is still actionable. How it works Triggers when an Inistate entry changes into the selected state (for example, “Pending Approval”). Fetches the full entry details from Inistate and checks whether the configured “Approve” activity is currently available. Builds an approval email containing the entry metadata and field values, then sends it via SMTP with Approve/Reject buttons and waits up to the configured number of days for a response. If no response arrives before the timeout, the workflow stops without updating Inistate. After a response, re-reads the entry from Inistate and verifies that the selected approve/reject activity is still available (so it does not overwrite changes made while waiting). Performs the matching Inistate activity to approve or reject the entry. Setup Add an Inistate credential and select the same Inistate workspace and module in every Inistate node, then choose the trigger state to monitor. Add an SMTP email credential for sending messages and set the approver email address and sender (“from”) address. Set the approve and reject activity names to exactly match the activity names in Inistate and configure the wait timeout in days. In the Inistate activity steps, select the correct approve/reject activities and fill any required activity fields for your module.

BeginnerManual Trigger

Send missed call text-backs with Twilio and email dispatcher approvals

Quick overview This workflow receives missed-call webhook events, validates and normalizes the caller number, looks up the caller in an n8n Data Table, and sends an appropriate Twilio SMS text-back, while logging outcomes and emailing a dispatcher (with approval required after hours). How it works Receives a POST webhook request for a missed call event. Normalizes the incoming caller number, sets the call timestamp, and determines whether the call is after business hours. If the phone number is missing or invalid, it responds with HTTP 400, logs the rejected event to an n8n Data Table, and emails the dispatcher. If the phone number is valid, it immediately responds with HTTP 202, looks up the caller in an n8n Data Table, and checks whether the call happened outside business hours. For after-hours calls, it sends an approval email to the dispatcher and proceeds only if the dispatcher approves sending the text. Builds a different SMS message for known customers versus first-time callers and sends the text-back via Twilio. Logs the SMS result to an n8n Data Table and emails the dispatcher either a confirmation (sent) or an action-required alert (failed). Setup Create two n8n Data Tables named demo_contacts (with phone and name) and demo_missed_calls (with phone, caller_type, status, detail, and called_at). Add a Twilio credential, verify/provision the sending phone number, and set the correct “from” number in the workflow settings. Add an SMTP email credential and set the dispatcher and sender email addresses used for approvals and alerts. Update the business name, scheduling URL, timezone, and open/close hours used to decide after-hours behavior. Copy the webhook URL from the Missed Call trigger and configure your phone system to POST missed-call events with a from field (optionally include simulate_after_hours for testing).

BeginnerManual Trigger

Analyze event scans and kit pickups with HTTP webhooks

Quick overview This starter workflow for n8n Community Challenge 04 fetches case, scan, and kit datasets from an n8n-hosted HTTP API, then guides you to compute three answers (first accepted scan, busiest session, and uncollected kits) and optionally submit them back to the API for validation. How it works Runs manually to start the challenge workflow. Stores your participant username, participant key, and the challenge API base URL. Retrieves the case data and the scans dataset from the challenge API via HTTP requests. Splits the scans dataset into individual rows so you can filter and aggregate to find the earliest ACCEPTED scan for Stage 1 and the busiest session for Stage 2. Uses your Stage 2 session result to request the kits dataset for that session from the challenge API and splits it into individual kit rows. Expects you to filter and summarize the kit rows to count CONFIRMED attendees who requested a kit but have not picked it up for Stage 3. Optionally posts each stage answer to the challenge API check endpoint (disabled by default) to validate your results. Setup Enter your challenge username and participant key in the Settings values used by the HTTP requests. If you are using the private preview environment, add an HTTP Basic Auth credential to each HTTP Request node. Build the missing filter/sort/grouping logic with native n8n nodes and map your computed results into the Stage 1/2/3 answer fields before enabling the stage check requests. Requirements Create an account here: https://community.n8n.io/ Customization Swap Your Username & Participant Key to Proceed

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

Optimize RFx supplier awards with Groq, Notion, and Slack alerts

IntermediateManual Trigger

by WeblineIndia