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.

13907+

Templates

50+

Integrations

50k+

Downloads

Latest n8n Templates

Freshly updated automation workflows to keep your n8n stack current

View All

Generate and host SubmitRax chat-built forms with Claude and GitHub Pages

Quick overview This workflow lets you generate SubmitRax form HTML via an Anthropic Claude agent (using the SubmitRax MCP server) and then publish the form as an HTML file to a GitHub Pages repository, returning a comment, form key, and hosted URL. How it works Chat with an AI form builder: the n8n Chat Trigger takes a plain-language request such as "create a contact form with name, email and message". You don't need to write any HTML or code. Generate the form with Claude AI and MCP: an Anthropic Claude Sonnet AI agent calls the SubmitRax MCP server to create a live form endpoint. It returns structured output with a short comment, a unique form key and ready-to-embed HTML form code. Check for an existing form page: the GitHub node looks for forms/.html in your GitHub Pages repository to decide whether to create a new page or update the existing one. Publish the HTML form to GitHub Pages: the workflow commits the generated HTML file, which gives you free static site form hosting with every change versioned in Git. Get the live form URL back in chat: the reply includes the agent's summary, the form key and the public GitHub Pages URL. SubmitRax, a form backend for static sites and JAMstack apps, collects every submission and can route it to email, Slack, Discord or webhooks with no backend code. Setup Create a SubmitRax (Here) API token and add it to an n8n HTTP Bearer Auth credential used by the SubmitRax MCP Tool. Add an Anthropic API credential for the Claude Sonnet chat model. Create a public GitHub repository with GitHub Pages enabled (deploying from the branch used by the workflow, default main) and ensure a forms/ folder path is acceptable for your Pages configuration. Create a GitHub Personal Access Token (or fine-grained token) with access to the target repository and connect it to the GitHub nodes. Update the GitHub username and repository name in the GitHub Hosting Config step so the workflow publishes to the correct repo and builds the correct hosted URL. Requirements An n8n instance (n8n Cloud or self-hosted) with the MCP Client Tool and AI Agent nodes available A SubmitRax account and API token (submitrax.com) for the form backend and MCP server An Anthropic API key to run the Claude Sonnet AI agent A GitHub account with a public repository and GitHub Pages enabled for free static form hosting A GitHub personal access token (classic or fine-grained) with contents read/write access to that repository Customization Swap the trigger: replace the Chat Trigger with a Webhook, Slack, Telegram or Form Trigger to generate forms from any channel Change the AI model: use another Claude model or switch the AI Agent to OpenAI, Gemini or a local LLM Brand your forms: edit the agent's system prompt to enforce your CSS, fonts, colors, field rules or language for every generated HTML form Change the hosting path or target: adjust the forms/ folder, branch or custom domain, or send the HTML to Netlify, Vercel, Cloudflare Pages or S3 instead of GitHub Pages Extend the workflow: post the live form URL to Slack or email, log each form to Google Sheets or Notion, or add SubmitRax webhooks to route submissions into your CRM

IntermediateManual Trigger

by PollupAI

Generate social media posts and images with Groq, OpenAI and Google Drive

Quick overview This workflow collects an image idea via an n8n Form, uses Groq to generate an optimized image prompt, creates an image with OpenAI, uploads it to Google Drive, then generates Instagram/LinkedIn/X copy and returns an HTML page showing the posts and image link. How it works Receives an image idea and a target resolution from an n8n Form submission. Uses Groq (openai/gpt-oss-120b) to turn the user input into a structured image-generation prompt. Generates an image with OpenAI (gpt-image-1-mini) using the prompt and selected resolution. Uploads the generated image to a specified Google Drive folder and captures a shareable link. Uses Groq to generate platform-specific posts for Instagram, LinkedIn, and X (Twitter) based on the image prompt. Uses Groq to convert the social posts plus the Google Drive image link into a structured HTML page. Displays the generated HTML as the form completion response. Setup Add Groq API credentials for the prompt generator, post generator, and HTML generator steps. Add OpenAI API credentials (or enable the managed AI gateway) for the image generation step. Connect Google Drive OAuth2 credentials and select the target Drive and folder ID where images are uploaded. Review the Form fields (input and resolution options) and update the Google Drive folder selection if you want to store images elsewhere.

BeginnerManual Trigger

Monitor Entra ID high-risk users with Microsoft Graph, TheHive and Slack

Quick Overview This workflow polls Microsoft Entra ID Protection for new high-risk risk detections, aggregates them per user, enriches them with risky-user and recent sign-in context from Microsoft Graph, then creates or updates matching alerts in TheHive and posts a summary to a Slack security channel. How it works Runs every 30 minutes on a schedule. Queries Microsoft Graph Identity Protection for risk detections with risk level set to high from the last 20 minutes, following @odata.nextLink pagination. Groups detections by user and aggregates key context such as detection types, risk states, IP addresses, locations, and first/last detection timestamps. Retrieves additional user context from Microsoft Graph by fetching the risky user record and the user’s five most recent sign-in events. Correlates deterministic signals (for example privileged roles, multiple countries, confirmed compromise state, or non-compliant devices) to classify severity and build a detailed incident description. Queries TheHive for existing open alerts of type entra-id-risk and either updates the matching alert (by sourceRef) or creates a new alert with observables. Posts a formatted alert summary and TheHive reference to a chosen Slack channel. Setup Create a Microsoft Entra ID (Microsoft Graph) OAuth2 credential with permissions for IdentityRiskEvent.Read.All, IdentityRiskyUser.Read.All, and AuditLog.Read.All. Add a TheHive 5 credential with permission to query, create, and update alerts, and ensure your TheHive instance is reachable from n8n. Add a Slack OAuth2 credential and select the security/SOC channel to post notifications to. Review and adjust the lookback filter (currently last 20 minutes) and schedule interval (every 30 minutes) to match your monitoring requirements.

BeginnerManual Trigger

Fill any PDF from JSON data with JustFill and Google Gemini vision

Quick overview This workflow collects a PDF and a JSON payload via an n8n form, uses JustFill to detect fields and render previews, then uses Google Gemini Vision to map data to field IDs and visually review the filled result before generating a downloadable filled PDF. How it works Receives a PDF upload and a “Data JSON” object through an n8n form. Requests an upload slot from JustFill, uploads the PDF, and opens it to detect fillable fields and create a workspace. Renders labelled page previews for all pages with detected fields using JustFill. Sends the labelled previews plus the user’s JSON keys to Google Gemini to map each data key to a specific JustFill field ID. Renders filled previews with the proposed values and asks Google Gemini to independently review the placement and readability across pages. If Gemini approves with no issues, fills the PDF in JustFill and returns a redirect link to download the completed document. Setup Add a JustFill API key and a Google Gemini API key, then paste them into the Config step (including the model name, if you want to change it). Ensure your JustFill account can access the MCP tools used by the workflow (request_file_upload, open_pdf, render_preview, render_filled_preview, and fill_pdf). Customize the n8n form fields (and any sample JSON) to match the kinds of data you plan to submit, then copy the form URL for users who will upload PDFs. Requirements A JustFill API key. The free plan works for testing, downloads are watermarked. You also need a Google Gemini API key for the vision model set in Config. Customization Swap the n8n form for a webhook, a Google Sheets row or your CRM, and change the model name in Config if you prefer another Gemini model. For a form you fill often, save it as a JustFill template and use the simpler template-based workflow instead.

BeginnerManual Trigger

Reply to WhatsApp leads with Google Gemini and Cal.com booking

Quick overview This workflow listens for incoming WhatsApp messages and uses Google Gemini plus optional TinyFish web research to draft concise replies, including offering and booking Cal.com meeting slots when requested, then sends the response back to the same WhatsApp contact. How it works Triggers when a new WhatsApp message is received. Checks that the incoming message contains text and ignores non-text messages. Adds booking and context fields (Cal.com link, event type, timezone, sender details, and message text) to the incoming payload. Uses a Google Gemini-powered agent with short-term chat memory to draft a reply, optionally calling TinyFish Search/Web Agent for lead research and Cal.com Slots/Book to propose and confirm meeting times. Sanitizes the generated response to ensure it is never empty and stays within a safe length limit. Sends the final reply back to the original sender via WhatsApp. Setup Connect WhatsApp Cloud API credentials for both the WhatsApp Trigger and WhatsApp send action, and ensure your WhatsApp app is configured to deliver message webhooks to n8n. Add a Google Gemini (PaLM) API credential for the chat model used by the agent. Add a Cal.com API key credential and set your Cal.com booking URL, eventTypeId, timezone, and lookahead days in the Booking Config step. (Optional) Add TinyFish credentials if you want the agent to perform web research about people or companies mentioned in chats.

BeginnerManual Trigger

Track weekend flight prices with Google Flights, SerpAPI, OpenAI and Telegram

Quick overview This workflow lets you create, list, cancel, and check weekend flight price alerts via Telegram (text or voice) and runs a daily schedule to price active routes using Google Flights results from SerpAPI, storing alert state in n8n Data Tables and sending deal digests back to Telegram. How it works Triggers either when a Telegram message/voice note is received or every day at 08:00 (server timezone). For Telegram voice messages, downloads the audio from Telegram and transcribes it with OpenAI, then normalizes all inputs into a single request format. Uses OpenAI to parse the user’s intent (create/list/cancel/status) and route preferences (airports, budget, window, weekend pattern, cadence) and converts them into concrete search dates and airport lists. For new alerts, fetches a sample Google Flights result via SerpAPI to validate the budget, generates an alert card, saves the alert to an n8n Data Table, and confirms creation in Telegram. For list/cancel/status requests, reads the alerts or run log from n8n Data Tables, applies the requested action (including marking an alert cancelled), and replies in Telegram. On scheduled runs, loads active alerts from the Data Table, queries Google Flights via SerpAPI for the relevant weekend date pairs, aggregates the cheapest option per weekend, and formats a ranked digest with booking links. Sends the digest to Telegram when results meet the notification rules, then logs the run and updates each alert’s last checked and last seen price in the Data Table. Setup Create a Telegram bot with @BotFather, add a Telegram credential in n8n, and enable the Telegram Trigger so it can receive updates. Add an OpenAI credential for both intent parsing and voice transcription. Add a SerpAPI credential with Google Flights access and ensure your plan/quota can cover the number of searches your alerts generate. Create two n8n Data Tables (for alerts and for the run log) with the required columns, then select their table IDs in all Data Table nodes used by the workflow. Update the Config values (home airport, max searches per run, and the admin_chat_id for error notifications) before activating the workflow.

Review content drafts for repetition, substance, tone and style using code

Quick overview Before you publish, this compares each draft in your content calendar against your last 30 published posts and flags the ones that will read as more of the same, then writes the reason back into the sheet. How it works Runs every morning at 09:00 on a schedule trigger, or on demand with the manual trigger. Reads rows marked ready from a Drafts tab in Google Sheets, and your last 30 posts from a Published tab. Compares wording with bigram overlap (Jaccard). Word bigrams for languages with spaces, character bigrams for Chinese, Japanese and Thai, chosen automatically. Compares structure on four signals: opening pattern, ending type, line and paragraph rhythm, and filler-phrase set. These are what make posts feel identical even when the words differ. Flags a draft only when both trip: wording overlap above the threshold AND at least two structural signals match. Either one alone is normal and does not flag. Writes approved or needs rework back to the sheet. A flagged row gets the offending past post plus the exact signals that matched, then goes to Slack. Setup Create a Google Sheet with two tabs: Drafts with columns id, text, status, note; and Published with columns text, published_at. Connect your Google Sheets credential on the three Sheets nodes and pick your document. Connect Slack on the last node, or replace it with Telegram, Discord or Gmail. The message is already built for you in the previous node. Put ready in a draft's status column, then activate the workflow. Requirements A Google Sheets credential, and a Slack credential or any other notifier you swap in. No AI model call and no paid API. A record of what you already published, in the Published tab. The repetition check has nothing to compare against without it. Customization Three numbers at the top of the Compare node: WORD_OVERLAP (0.18), STRUCTURE_HITS (2) and HISTORY (30). Raising either of the first two makes the gate quieter. Add your own autopilot phrases to the FILLERS list, and your own ending patterns to endingType. Plain text, no regex needed. Additional info Most duplicate checks compare words, which misses the real problem: you can write thirty posts that share no vocabulary and still feel identical, because every one opens the same way, ends the same way and runs the same rhythm. Readers get bored by the shape, not the nouns. That is why this requires both signals before it flags anything: two posts that merely share a rhythm are not a problem.

Process Stripe refunds with Allowly approval and reviewer checks

Quick overview This workflow runs a Stripe test-mode refund only after an Allowly policy check allows it or a reviewer approves it via a secure callback, then creates the refund in Stripe and fetches the Allowly decision receipt as evidence. How it works Starts manually and builds a refund request containing the Allowly authorization ID, Stripe PaymentIntent ID, amount, currency, reason, and a frozen resource string for approval binding. Validates the request format and reads the Stripe PaymentIntent via the Stripe API to ensure it is a succeeded test payment with sufficient captured funds. Sends the frozen resource and context to Allowly for a refund.create decision check. If Allowly allows immediately, proceeds; if Allowly requires confirmation or escalation, waits for an authenticated HTTP callback with an approval decision and resolves the confirmation/escalation in Allowly before re-checking for a final allow. If the final decision is allow, creates the Stripe refund using an idempotency key tied to the refund request ID. Validates the Stripe refund response and then retrieves the Allowly receipt via the Allowly API to export the refund evidence (marking it pending if not yet signed). Setup Add Stripe API credentials for a Stripe test account and select the same credential for both Stripe HTTP requests. Add Allowly API credentials and select them on all Allowly nodes and the receipt-fetching HTTP request. Create and store an Allowly authorization ID, then replace authorizationId, paymentIntentId, and other fields in the refund request payload as needed (this template only supports USD with reason requested_by_customer). Configure the Wait for reviewer step to require header authentication, then copy its resume webhook URL and send POST reviews in the form {"approved": true|false, "resource": ""} within 4 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

Generate and host SubmitRax chat-built forms with Claude and GitHub Pages

IntermediateManual Trigger

by PollupAI