Skip to main content

n8n Workflows: 25 Ideas and Where to Get Templates

n8n workflows explained: 25 n8n workflow ideas with suggested stacks, where real templates live, how to import one and what to check before you publish.

Founder of IImagined.ai

Published
May 8, 2026
Updated
Oct 13, 2026
Reading time
10 min read
Quick answer

An n8n workflow is a trigger plus the nodes that act on its data, and it runs on its own only after you publish it. This page gives 25 n8n workflow ideas in five groups, each with a suggested set of services; they are ideas, with no importable workflow JSON attached. Real templates live in the official n8n library. Import one, inspect every node, add credentials with the narrowest access that works, and test with dummy data before you publish.

n8n workflows are chains of nodes on a canvas: one trigger that starts the run, then steps that fetch, change, decide and send. Below are 25 n8n workflow ideas to build from, the places real templates live, and the checks to run before anything goes live. One thing to be clear about first: there are no importable workflow JSON files on this page.

Checked on 13 October 2026 against n8n's own pages: the template library, the docs on using templates, export and import and saving and publishing, the Sustainable Use License, the licence FAQ and the 3.0 breaking changes. An earlier version of this page claimed a much larger library than it contained. The ideas are suggestions and none has been validated as a finished integration.

What is an n8n workflow made of?

Five parts, in order. Once you can name them, every template you open reads the same way, and every idea below turns into a build list.

The five parts of an n8n workflow
  1. 01
    Trigger

    A schedule, a webhook call, a chat message or an event in a connected app.

  2. 02
    Fetch

    App nodes or an HTTP Request node pull the data the run needs.

  3. 03
    Decide

    If, Switch and Filter nodes route items. An AI model can classify or draft.

  4. 04
    Act

    Write to the CRM, post to Slack, send the email, save the file.

  5. 05
    Recover

    Retries on the risky nodes and an error workflow that alerts a person.

Two details from the n8n docs matter before you build anything. Changes save automatically as you edit, as drafts. And a workflow runs unattended only once you select Publish: production runs then use the published version, not your latest edits. If n8n itself is new to you, the n8n tutorial for beginners builds a first workflow step by step.

Where do you get n8n workflow templates?

From the official library first. On 13 October 2026 its heading read "13200 Workflow Automation Templates", grouped under AI, Sales, IT Ops, Marketing, Document Ops, Support and Other. The Templates option inside the editor opens the same library.

SourceWhat you getWatch for
Official n8n template libraryWorkflow JSON you can open in your own instance, with a description and the services it needsWritten by many different creators. Read every node before adding credentials
Templates option inside the editorThe same library, opened from the app. A company can point it at a private library insteadA private library only exists if your organisation set one up
JSON shared in a forum, repo or videoWhatever the author exportedMay hold credential names, and auth headers in HTTP Request nodes imported from cURL
An idea, like the 25 belowA trigger, a goal and a list of servicesYou build and test it yourself. Nothing is ready to import
An idea against a template
A workflow idea
  • Names a trigger, a goal and some services
  • Costs nothing to read and nothing to adapt
  • You choose every node and every field
  • Slower to a first run
  • You understand all of it, because you built it
A workflow template
  • A JSON file that opens as nodes on your canvas
  • Faster to a first run
  • Built for someone else and their accounts
  • May use nodes or versions your instance lacks
  • Needs a full read before credentials go in

Neither is finished work. A template is a faster start, and an idea is a cleaner one. The 25 below are ideas.

AI content (5 ideas)

Drafting and repurposing. Use content you own or have permission to reuse, check facts by hand, and keep a person between the draft and the publish button.

  • Blog post in, three social drafts out. stack: Webhook + AI model + Notion or Google Docs
  • New YouTube video to a blog post draft. stack: YouTube + transcription + AI model + WordPress draft
  • Daily digest from a list of RSS feeds. stack: Schedule Trigger + RSS Read + AI model + email tool
  • Long article to a week of post drafts. stack: Google Docs + AI model + Google Sheets
  • Reel script from a blog post. stack: Webhook + AI model + Notion

Lead handling (5 ideas)

Triage, enrichment and CRM sync. Check consent and retention rules before processing personal information, and treat a model score as a suggestion, not a fact.

  • Form submission scored and tagged in the CRM. stack: Webhook + AI model + HubSpot or Pipedrive
  • Inbox triage by intent. stack: Gmail Trigger + AI model + Slack
  • New lead enriched from a data provider. stack: CRM trigger + HTTP Request + Google Sheets
  • Booked call to a prepared briefing note. stack: Calendly Trigger + CRM lookup + AI model + email
  • Stale deal reminder. stack: Schedule Trigger + CRM search + Slack

Social media (5 ideas)

Scheduling, monitoring and reporting. Stay inside each platform's API terms: draft and queue with automation, and approve anything public yourself.

  • One approved post queued to several platforms. stack: Airtable or Notion + scheduling tool API
  • Comment triage with drafted replies for approval. stack: Platform API + AI model + Slack approval
  • Weekly performance summary. stack: Schedule Trigger + platform insights API + Google Sheets
  • Brand mention alert. stack: Schedule Trigger + search API + Slack
  • Content calendar gaps flagged on Monday. stack: Schedule Trigger + Notion + Slack

SaaS operations (5 ideas)

Payments, onboarding and support. Verify every incoming webhook signature and make each step safe to run twice, because payment events can arrive more than once.

  • New paying customer to an onboarding sequence. stack: Stripe Trigger + email tool + CRM
  • Failed payment to a recovery email and an alert. stack: Stripe Trigger + email tool + Slack
  • Support ticket to a drafted reply for approval. stack: Help desk trigger + AI model + Slack
  • Feedback form categorised and routed. stack: Webhook + AI model + Linear or GitHub
  • Daily revenue summary. stack: Schedule Trigger + Stripe + Slack

AI agents (5 ideas)

Multi-step model workflows with tools and memory. Restrict what each tool can do, cap iterations and spend, and require approval before anything is written outside n8n.

  • Research agent that returns a cited brief. stack: Chat Trigger + AI Agent + search tool + Notion
  • Pull request summary and review notes. stack: GitHub Trigger + AI model + GitHub comment
  • Support agent that answers from your documents. stack: Chat Trigger + AI Agent + vector store
  • Booking agent that checks a calendar first. stack: Chat Trigger + AI Agent + Google Calendar tool
  • Failed execution to a suggested diagnosis. stack: Error Trigger + AI model + Slack

Each suggested set of services is a starting point, not a parts list. n8n may have a dedicated node for a service, or you may need the HTTP Request node and the service's API. Our guide to n8n API integration covers that route, the webhook trigger guide covers the first node of most of these, and Claude and n8n covers the model step.

How do you import an n8n workflow?

A workflow travels as a JSON file. The export and import docs list the routes; the short version is below.

From a template to a published workflow
  1. 1
    Get the JSON from a source you trust

    The official library, or an author you can identify.

  2. 2
    Bring it in

    Workflow menu in the canvas header: Import from File. Or copy the nodes and paste them on the canvas.

  3. 3
    Read every node

    Code and HTTP Request nodes first. Look at URLs, headers and where data is sent.

  4. 4
    Add your own credentials

    New keys with the narrowest access that works. Never reuse a credential that came with a file.

  5. 5
    Test with dummy data

    Missing fields, duplicates, a rate limit, a permission error.

  6. 6
    Publish

    Only then. Keep customer-facing sends switched off until the test passes.

In n8n 2.x the same menu also has Import from URL. The 3.0 breaking changes page lists that option as removed, with copy and paste, file import, the CLI and the API as the replacements, so do not build a habit around it. The docs also describe an n8n CLI that packages a workflow into a portable .n8np file; it is marked as a preview and may change.

What should you check before you publish a workflow?

The same eight things every time, whether the workflow came from a template or from a blank canvas.

Before you publish
  • Every credential is yours, with the narrowest access that works
  • An Edit Fields node early on gives later nodes one predictable data shape
  • Nodes that call outside services have Retry on Fail set, with a wait between tries
  • Steps that send, charge or create are safe to run twice
  • An error workflow is published and alerts a person
  • AI output that reaches a customer passes a human first
  • You ran it on dummy data, including an empty input and a duplicate
  • The JSON is saved somewhere with a note of the n8n version it was built on

Two of those have their own guides: n8n error handling for the alert path, and five ways n8n workflows fail silently for the failures that never raise an error at all. For timed workflows, the cron expression guide covers the Schedule Trigger.

Can you use n8n workflows commercially?

For your own business, yes. n8n is published under the Sustainable Use License, which is not an open source licence: it says you may use or modify the software "only for your own internal business purposes or for non-commercial or personal use". n8n calls this model fair-code.

Client work under the licence, per the n8n licence FAQ
Not allowed
  • Hosting n8n as a service where clients build workflows
  • Letting outside users build or configure workflows through your product
  • White-labelling n8n by removing its branding
Allowed
  • Building automations for clients on your own instance
  • Running and maintaining those workflows for a fee
  • Using n8n behind the scenes in your own product
  • Installing and maintaining n8n on a server the client owns, if you do not also sell hosting

Source: n8n licence FAQ, read 13 October 2026. A summary, not legal advice.

The test n8n gives is that n8n "remains your internal tool, where clients receive outputs, not access". The FAQ does not cover selling workflow files on their own, and templates from other authors can carry their own terms, so ask n8n and the author before you resell anything. Plan limits are a separate question: see n8n's pricing page or our n8n pricing breakdown.

Where to go next

Pick one idea, build it for yourself, and run it for two weeks before you build a second. If you are still choosing a tool, n8n vs Zapier and n8n vs Make compare the three, and the AI automation library lists every related guide. If you would rather build your own AI product than run workflows for clients, AI SaaS Builder is our program on building one on Supabase, Next.js and the Claude API.

n8n workflows: FAQ

What is an n8n workflow?

An n8n workflow is a set of connected nodes on a canvas. A trigger node starts it, on a schedule, on a webhook call or on an event in a connected app, and each node after that does one job with the data it receives. Edits save automatically as drafts, and the workflow only runs on its own once you publish it.

Does this page include n8n workflow files?

No. This page has 25 workflow ideas in five categories, each with a suggested set of services. There are no importable workflow JSON files attached. The ideas describe possible designs and have not been validated as finished integrations. For real files, use the official n8n template library, then check every node before you add credentials.

Where can I find free n8n workflow templates?

The official library at n8n.io/workflows is the main source. Its heading read 13200 Workflow Automation Templates on 13 October 2026, sorted into AI, Sales, IT Ops, Marketing, Document Ops, Support and Other. The Templates option inside the n8n editor opens the same library. A template may still need paid accounts with the services it connects.

How do I import an n8n workflow?

In n8n 2.x, open the workflow menu in the canvas header and choose Import from File or Import from URL, or copy the nodes and paste them onto the canvas. n8n 3.0 removes Import from URL in the editor, leaving copy and paste, file import, the CLI and the API. Inspect the nodes, then test with dummy data before you publish.

Are n8n workflows free to run?

The ideas and most templates cost nothing to read. Running them does cost something: n8n Cloud plans are priced by workflow executions, and a self-hosted Community edition has no licence fee but needs a server and your time. The services a workflow calls, such as an AI model or an email tool, bill separately.

Can I build n8n workflows for clients?

The licence FAQ in the n8n docs says building, running and maintaining workflows on your own instance on behalf of clients is permitted, as long as n8n stays your internal tool and clients receive outputs, not access. Hosting n8n as a service where clients build their own workflows, and white-labelling it, are not allowed. Ask n8n about anything in between.

Every guide in this hub

Free · no card needed

Start with the free Starter Kit.

A unit economics calculator from AI SaaS Builder, plus four more working files.

Starter Kit5 files · free
See All Access: $99/mo →30-day money-back guarantee
Keep reading

Related guides.

The AI Automations libraryAll articles