Browse

n8n workflow examples

n8n workflow examples are finished graphs you can import and then change. n8n workflow ideas are the jobs those graphs are for. A useful example names the trigger, the model step if there is one, where the result lands, and what happens when a step fails. A vague idea such as “marketing automation” does not.

Live listings

Live n8n workflows next to the examples on this page. Patterns above are not sample listings.

All n8n workflows

What you should copy from an example

Copy the shape, not someone else’s credentials. An example is a JSON file plus the notes that say which fields you must edit. Import it into a scratch project. Connect one credential. Run a tiny input you understand. If the author gave you a sample input and the output they expect, use that first. If they did not, the example is a sketch, and you should treat the first red node as the real documentation.

Write down the n8n version, Cloud or self-hosted, and any community node. A workflow that ran on the author’s machine can fail on yours because a node moved, not because the idea was wrong. Also write which accounts the buyer, or you, must already have. The example does not include those subscriptions.

n8n workflow ideas that are specific enough to build

Start from a job a person already does every week. If you cannot say what arrives and what leaves, you do not have an idea yet. These are the kinds of jobs that survive contact with real accounts. Each one can be a free pattern you rebuild, or a paid template if the error handling and the notes are already done.

  • New lead in a form or CRM: look up the company, ask a model for a five-line summary, write it back on the record
  • New email in a shared inbox: label it, draft a reply, and leave a person to send it
  • File dropped in a folder: extract the fields you named, append a row, and branch when a field is missing
  • One approved article: draft a short post for two channels you actually use, and stop there
  • A weekly schedule: pull a few numbers you already store and write a short summary a person can edit
  • A webhook from a tool you trust: file a row, notify one channel, and ignore everything else

Three n8n workflow examples, as patterns

These are patterns, not a ranking and not a claim about what sells. AIMarket24 does not publish install counts or a bestseller chart. Use them to see what “done” looks like before you import a file or pay for one.

Lead summary. The trigger is a new row or a form submission. One node reads the fields you listed, such as company name and site. A model step writes a short summary from those fields only, with an instruction not to invent facts that are not in the input. The last node writes the summary back to the CRM or the sheet. The failure path is the interesting part: if the lookup is empty or the model times out, the row is flagged and nothing is emailed to the lead. Credentials are the CRM and the model key. The buyer changes the field names and the destination, not the idea.

Inbox triage. The trigger is a new message in one mailbox, not every mailbox the author owns. A step classifies the message into a few labels you chose. A later step drafts a reply and saves it as a draft. It does not send. Sending is a separate decision, and a template that auto-sends customer mail should say so in the first lines. The failure path keeps the original message untouched. Credentials are the mailbox and, if you use a model, that key. This is a support workflow, not a chatbot. If you need a widget on a site, that is a different product.

Document extraction. The trigger is a new file in a folder or an upload. A step reads the file and asks a model for a fixed set of fields, such as date, total, and vendor. The result is one row. If a required field is missing, the row goes to an exceptions sheet instead of the main sheet. Credentials are the file store, the model, and the sheet. The example input should be a file you are allowed to show, not a customer’s invoice. Say which file types you tested.

n8n workflow ideas that are still too broad

“AI for the whole company,” “social media on autopilot,” and “replace the sales team” are not examples. They hide the trigger and the place the result goes. Split them until one sentence works: who starts it, what the model is allowed to decide, and who still has to approve. A workflow is a fixed path. If the next step depends on what the model just found, and that path is not written down, you may want an agent instead of another node.

Also skip ideas that only work with data you cannot legally or practically share. A demo that needs a production token, a private customer list, or a community node you cannot name is not an example a stranger can run. Redact first, then show the graph.

Free library, paid file, or build it once

n8n publishes its own templates library. Creators can submit workflows there, and verified creators can publish paid templates. That help page does not print a commission. Use the library when you want to learn a pattern. Read the nodes before you import. A free template can still need paid apps and a model key.

Pay for a template when the author already did the part that usually breaks: the error branch, the sample input, the credential list, and a short note on which fields change. Do not pay for a screenshot you could redraw from the docs in an hour. On AIMarket24 a workflow listing has a price, a written scope, and escrow. Listing is free. The platform keeps 15% of a sale, or 5% for six months for the first 50 sellers who publish a live listing. This page does not invent a typical price.

Turn an idea into something you can hand someone

If you already run the workflow, the example is your export with secrets removed. Add the version, the credentials, one input, the output, and the failure behavior. That package is what a buyer compares. If you are still at the idea stage, build the smallest path that completes one job, then decide whether it is worth listing.

The marketplace is live. The catalog shows live workflow listings, not sample cards from the homepage. Open one and read the scope before you import anything into production.

Frequently asked questions

Where can I find n8n workflow examples?

n8n’s own templates library is the free starting point. This page describes patterns you can rebuild, and the live shelf lists workflows sellers have packaged with a scope. An example should include the JSON, the credentials, and a sample run.

What are good n8n workflow ideas for a small team?

One repeated job: summarize a new lead, draft an inbox reply without sending it, or extract fields from a file into a sheet. Skip ideas that do not name the trigger and the destination.

Do n8n workflow examples work on Cloud and self-hosted?

Often, but not always. The notes should name the n8n version and any community node. Check that before you depend on the import.

Can I sell a workflow based on an example?

Only if the license allows it and the result is your work, not a rename. AIMarket24 rejects uploads that are 95% or more similar to an existing listing.

Related guides

Read next