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.

14965+

Templates

50+

Integrations

50k+

Downloads

Latest n8n Templates

Freshly updated automation workflows to keep your n8n stack current

View All

Send a weekly Crossbeam partner brief to Slack with Claude, Salesforce and HubSpot

Quick overview This workflow runs weekly and pulls overlap changes, net-new accounts, and partner suggestions from Crossbeam via MCP, uses Anthropic Claude to prioritize actions against your ICP, posts a Block Kit brief to Slack, and (after Slack approval) creates selected companies in Salesforce or HubSpot. How it works Runs every hour on a schedule and continues only at the configured weekday/hour (or when manually triggered). Queries Crossbeam MCP for recent overlap changes, net-new accounts, and partner suggestions, then deduplicates and filters results using stored history. Uses Anthropic Claude (optionally with read-only Crossbeam MCP lookups) to rank weekly priorities, score ICP fit for net-new accounts, and add rationale for partner suggestions. Formats the results into a single Slack Block Kit message (including partner invite buttons) and posts the weekly brief to the configured Slack channel. Saves the current overlap state and partner-suggestion state to n8n Data Tables so next week’s run reports only meaningful changes and enforces the re-nudge window. If net-new accounts are available, sends a Slack form in the thread to select which ones to create and waits up to the configured approval window. Creates only the approved records in Salesforce (Account or Lead) or HubSpot (Company), records outcomes to a Data Table, and replies in the Slack thread with results and record links. Setup Create and select credentials for Crossbeam MCP (OAuth2), Anthropic (Claude), and Slack (OAuth2), and invite the Slack bot to the target channel. Enable Slack Interactivity for your Slack app using n8n’s webhook URL so the approval form button can submit responses. Create three n8n Data Tables for overlap history, partner suggestion history, and net-new/CRM outcomes, then select the correct table IDs in the Data Table nodes. In the Configure step, set your timezone, brief schedule, Slack channel ID, ICP description, and Crossbeam list/settings (pages, segments, lookback, and ignore lists). Configure CRM settings by choosing Salesforce or HubSpot, setting Salesforce Account vs Lead (and Salesforce base URL or HubSpot portal ID), then test with dry_run enabled before turning dry_run off to allow record creation. Requirements Crossbeam with MCP access (credit metered: one call per page and per agent lookup, all capped in Configure me) Anthropic API key (Claude) Slack app with chat:write and interactivity for the selection form Salesforce or HubSpot (only used for the accounts you approve) Customization Filter net-new accounts by size, country and industry with employee_ranges, countries, industries_to_include and industries_to_exclude. Describe your ideal customer profile in plain words in icp_description; Claude scores fit against it. Change the brief day and hour, page counts, item caps and the re-nudge window for partner suggestions. Set crm_choice to hubspot to create HubSpot companies instead of Salesforce records. Additional info Crossbeam AI Agents and List Notifications send partner alerts one by one, and Crossbeam's native CRM push only enriches records that already exist. This template gives one weekly, prioritised view across overlaps, net-new accounts and partner suggestions, and a safe way to create only the accounts you choose. Nothing is created while dry_run is true. Partner invites stay in Crossbeam: each suggestion links to Crossbeam's own invite page. Next steps: add Claude to the channel (Claude in Slack) to draft partner intros, or enrich new accounts with Clay before creating them. Setup guide: Crossbeam MCP server https://help.crossbeam.com/en/articles/12601327-crossbeam-mcp-server-limited-availability

Manual Trigger

by Margaux Faurie

Prepare reviewable client delivery jobs from Google Sheets with Prooftask and Slack

Quick overview This workflow is manually run to create and persist a draft client delivery job in Prooftask by posting your mapped project, criteria, and delivery materials to the Prooftask Agents API. How it works Starts when you run the workflow manually. Builds a single delivery payload containing a persistent requestId, a Prooftask projectId, a workflow reference, and delivery materials mapped to agreed criterion IDs. Validates that exactly one job is being prepared and that the requestId and projectId match the required ID formats. Sends the payload to the Prooftask Agents API to create and persist a saved delivery job and returns the created job details for you to record. Setup Create or select an existing Prooftask project with agreed delivery criteria and note the project ID and criterion IDs you will reference. Create a Prooftask scoped Agent token and configure an n8n HTTP Header Auth credential with Authorization: Bearer for the Prooftask request. Replace the example values in the input payload (requestId, projectId, workflowReference, summary, materials, references, and files) with your real delivery data and keep the same requestId when retrying the same delivery preparation. Requirements An existing Prooftask project with agreed criteria, an authorized scoped Agent grant, and an n8n Header Auth credential. Prooftask service availability and pricing apply separately. Additional info Preparation creates a saved delivery job; it does not send the delivery, accept work, sign, or pay. Persist the returned job ID in your own task system and review the exact materials before deliberate submission using the separate send-job workflow. No API token or customer data is included. Export syntax and workflow graph were validated; authenticated production-engine execution has not been claimed. Setup and companion workflows: https://github.com/cognitive-emergence/prooftask-integrations/tree/main/n8n

Beginner

Draft UK property listings and flag risky claims with OpenAI and Google Sheets

Quick overview UK estate and letting agents (and anyone writing property listings) who want a first draft of portal listing copy from their own property facts, with possible claims to check flagged before anything goes live. How it works Runs every hour on a schedule (or on demand with Execute workflow). Reads a Google Sheet of property facts and keeps rows whose status is ready. Sends the facts to OpenAI with a short prompt: use only the facts given, and return a headline, a short summary, five to eight key features, and any claims that may need verifying. Writes the draft and the flags back to the same row and sets its status to draft_ready, so it isn't picked up again. Nothing is published. Setup Google Sheet with a tab named Properties and the column headings listed in the Start here note Credentials: Google Sheets, OpenAI (add your own in n8n; none are included in this template) Paste your sheet URL into "Read properties" and "Write draft to sheet" Add a property row, set its status to ready, run once, then activate Requirements A Google account with Google Sheets An OpenAI API key Customization Edit the SYSTEM_PROMPT in "AI instructions" to change style, length or output. Pick a different model in "OpenAI chat model". Add fact columns to the sheet and to the prompt in "Draft listing copy". Additional info The claim flags come from a short general prompt and are not a compliance check. Always check copy against your own facts before publishing. Made by Burnt & Toast Kits. This is a free starter. The paid Listing Writer Kit adds tuned prompts, a UK compliance checklist (CPRs/DMCCA material information), voice matching, edge cases and a setup guide: https://kits.burntandtoast.com/estate-agents/kits/listing-writer

IntermediateManual Trigger

Sync inventory across Shopify, Amazon, Flipkart with Google Sheets and Slack alerts

Quick overview This workflow syncs a single inventory count across Shopify, Amazon (SP-API), and Flipkart every 10 minutes using Google Sheets as the inventory master and ledger, then updates channel quantities with a safety buffer and posts low-stock and failure alerts to Slack. How it works Runs every 10 minutes on a schedule and reads the last orders cursor from Google Sheets with an overlap window to avoid missing updates. Loads the Inventory Master, the Processed Lines ledger, and any pending manual stock adjustments from Google Sheets. Pulls recently updated orders from Shopify via GraphQL, fetches updated Amazon orders and line items via SP-API (using an LWA token), and retrieves Flipkart pre-dispatch and cancelled shipments. Calculates per-SKU stock movements, deduplicates order lines using the Processed Lines ledger, applies cancellations and queued manual adjustments, and computes a sellable quantity by subtracting each SKU’s safety buffer. Pushes updated sellable quantities only for changed SKUs (or all SKUs during the nightly full sync) to Shopify inventory, Amazon listing availability, and Flipkart inventory. Writes updated SKU totals back to the Inventory Master, appends new ledger entries to Processed Lines, marks stock adjustments as applied, and saves the new cursor in Sync State. Posts Slack alerts for oversold/out-of-stock/low-stock SKUs (including recent sales velocity and days of cover) and sends a separate Slack alert when any channel inventory push fails. Setup Create a Google Sheet with tabs named Inventory Master, Processed Lines, Stock Adjustments, and Sync State, and ensure the Inventory Master includes your SKU mappings and channel identifiers (Shopify inventory item/location IDs, Amazon SKU, Flipkart SKU/product/location IDs) plus safety buffer fields. Add credentials in n8n for Google Sheets, Slack, Shopify Admin API (HTTP Header Auth with X-Shopify-Access-Token), and Flipkart Seller API (HTTP Basic Auth). In the configuration code, set your Shopify domain, Amazon seller ID, Amazon marketplace ID, Amazon LWA client ID/secret/refresh token for SP-API access, Flipkart location ID, and your full-sync hour. Update the Google Sheet document ID and Slack channel ID values in the Google Sheets and Slack nodes, then run once manually to validate SKU mappings and initial cursor state before activating the schedule.

Send weekly Shopify RFM win-back offers with GPT-4o-mini, Klaviyo and WhatsApp

Quick overview This workflow runs every Monday to pull the last 24 months of Shopify orders, calculate RFM segments per customer, generate segment-specific win-back copy with OpenAI, create unique Shopify discount codes, sync reachable customers into Klaviyo lists, send WhatsApp template messages, and post a weekly performance report to Slack. How it works Runs every Monday at 10 AM (cron schedule). Fetches the last 24 months of Shopify orders via the Shopify Admin REST API and loads the previous week’s customer segments from Google Sheets. Calculates each customer’s recency, frequency, and monetary scores, assigns an RFM segment, marks a deterministic 10% holdout per segment, and computes basic segment stats and week-over-week movement. For each configured target segment above the minimum size, uses OpenAI (gpt-4o-mini) to draft email and WhatsApp offer copy, applies discount cap guardrails, and creates a segment-specific Shopify discount code via the Shopify Admin GraphQL API. Bulk-imports non-holdout, email-consented customers into the matching Klaviyo list with the offer details stored as profile properties, and posts a Slack alert if a Klaviyo import fails. Sends an approved WhatsApp Business Cloud template message (prioritized by segment and capped per day) to non-holdout, opted-in customers and logs send results to a Google Sheets win-back log. Upserts the current week’s customer segments (including offer code and holdout flag) back to Google Sheets and posts a formatted weekly RFM and lift report to Slack. Setup Create a Shopify custom app with read_orders, read_customers, and write_discounts, then add an HTTP Header Auth credential for Shopify using X-Shopify-Access-Token and update the store domain and GraphQL endpoint values. Add a Klaviyo API key as HTTP Header Auth (Authorization header), create one Klaviyo list per segment you plan to target, and paste the list IDs into the configuration. Connect WhatsApp Business Cloud credentials in n8n, set your WhatsApp Phone Number ID, and ensure the winback_offer template is approved and matches the workflow’s parameter placeholders. Connect Google Sheets credentials and set the spreadsheet ID, ensuring it contains a “Customer Segments” sheet for upserts and a “Winback Log” sheet for WhatsApp send logging. Connect Slack credentials and set the target channel ID for the weekly report and failure alerts, then update the values in the RFM configuration (discount caps, min order value, holdout %, WhatsApp daily cap) before activating.

Score and route inbound leads with Gemini, website enrichment, Slack and Sheets

Quick overview This workflow receives inbound lead submissions via webhook, validates and enriches them with basic website scraping, scores fit and intent using Google Gemini, logs every lead to Google Sheets, and alerts a Slack channel when a lead scores as hot. How it works Receives a POST request on a webhook endpoint for inbound lead details and immediately returns a 200 response with a generated lead ID. Normalizes the payload into consistent fields (name, email, company, website, job title, message), flags free or disposable emails, and marks obvious spam/test submissions as junk. If the lead looks valid, calls a public email scoring API to get an email verdict/score and marks the lead as junk if the verdict is invalid or disposable. For non-junk leads, fetches the company homepage and extracts a short plain-text summary from the HTML for enrichment. Sends the lead details and extracted website text to Google Gemini and parses structured JSON containing an ICP score, tier (hot/warm/cold), key reasons, next action, and confidence. Combines the Gemini output with the lead record, appends the result to a Google Sheets tab named "Leads", and posts a formatted Slack alert when the tier is hot. Setup Add Google Gemini API credentials (Google AI Studio/Vertex Gemini connection) for the Gemini chat model used to score leads. Add Google Sheets OAuth2 credentials and replace the placeholder spreadsheet ID in the Config step, ensuring the spreadsheet has a sheet/tab named "Leads". Add Slack OAuth2 credentials with permission to post messages, and replace the placeholder Slack channel ID in the Config step. Update the ICP description and the hot/warm threshold values in the Config step to match your qualification criteria. Copy the webhook URL from the webhook trigger and configure it in your form or lead source to send JSON via HTTP POST. Additional info Need it installed? I set this up in your n8n on Fiverr, starting around $20: https://www.fiverr.com/mouwah/set-up-a-tested-n8n-invoice-approval-or-lead-routing-workflow-in-your-n8n Pro version (email typo rescue, speed-to-lead tracking, more routing tiers): https://mohabaha0.gumroad.com/l/lead-routing-pro

Score Reddit buying-intent leads with Apify, OpenAI, Google Sheets and Slack

Quick overview Every morning this workflow searches Reddit posts and comments for buying-intent phrases, scores each one from 0 to 100 with OpenAI, logs every scored lead to Google Sheets and sends only the hot ones to Slack. How it works Every morning runs at 08:00 and reads your phrases and product from Settings. Search Reddit posts and comments finds matches from the last day across Reddit (or one subreddit). One shape for posts and comments and Skip leads already scored clean up and drop items seen in earlier runs. Score buying intent asks OpenAI for a 0-100 score, the need, and a reply angle. Log to Google Sheets keeps every scored item. Hot leads only sends items at or above minScore to Slack. Setup Add the Apify node (@apify/n8n-nodes-apify, a verified node) if your n8n does not have it yet. Create an Apify API credential with the token from Apify Console → API & Integrations. No account yet? Sign up free; the free plan includes monthly credit. Add an OpenAI credential. Create a Google Sheet with a Leads tab and the columns scoredAt, score, kind, subreddit, title, need, replyAngle, author, url, text. Connect Google Sheets and pick the file. Connect Slack and pick a channel. In Settings, describe your product and edit phrases (quotes mean exact match). Customization Raise minScore to get fewer, warmer Slack alerts. Set community to one subreddit name to search only there. Reddit results cost about $2 per 1,000 on Apify. The Apify node stops each run at $2. Additional info For founders, agencies and sales teams who sell to people that ask Reddit for help. Reddit data comes from the Reddit Scraper Actor on Apify, so you need no Reddit API key or OAuth app approval.

IntermediateManual Trigger

Qualify agency leads and draft email replies with OpenAI, HubSpot, Gmail and Slack

Quick overview This workflow receives agency enquiries via an authenticated webhook, uses OpenAI to extract a structured brief and draft reply (optionally enriching with an approved company homepage), deduplicates by searching HubSpot deals, then creates or updates HubSpot records, saves a Gmail draft, and notifies the owner in Slack. How it works Receives a POST request on an authenticated webhook with lead details (requestId, name, email, company, website, message). Validates and normalises the payload, then searches HubSpot Deals for an existing deal with the same deterministic deal name to prevent duplicate processing. If the enquiry already exists, returns the existing HubSpot deal ID to the caller without creating a new deal or Gmail draft. If the website domain is allowlisted, fetches the company homepage and extracts bounded plain text to use as research evidence. Uses OpenAI to extract a structured lead brief and reply draft, then applies deterministic scoring and assigns a HubSpot owner based on budget, service fit, urgency, and verified website evidence (falling back to a manual-review payload if AI fails). Upserts the contact in HubSpot, creates an associated HubSpot deal with the qualification details, saves a personalised Gmail reply draft, posts a review notification to Slack, and returns the deal ID and score to the webhook response. Setup Add credentials for Webhook Header Auth, OpenAI, HubSpot (App Token with contacts and deals read/write scopes), Gmail OAuth2, and Slack. Update the Settings values for your agency name, supported services, scoring weights, budget threshold/currency, HubSpot owner IDs, pipeline ID and deal stage ID, Slack channel ID, and OpenAI model. If you want website enrichment, populate enrichmentAllowedDomains with the exact domains you approve for fetching; leave it as an empty array to skip research. Configure your website or form backend to POST JSON fields (requestId, name, email, company, website, message) to the webhook URL and reuse the same requestId for retries so deduplication works.

Intermediate

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

Send a weekly Crossbeam partner brief to Slack with Claude, Salesforce and HubSpot

Manual Trigger

by Margaux Faurie