Home › Guides

Where to Sell n8n Workflows (and How to Package Them So People Buy)

You built an n8n workflow that saves hours every week, and now you wonder whether someone else would pay for it. Many builders hit the same wall: where do you actually sell an automation, and what exactly is the product? This guide walks through the main options, how to package a workflow so a stranger can run it, and the mistakes that get templates refunded or ignored.

1. First, decide what you are really selling

An n8n workflow can be sold in three very different forms, and the right marketplace depends on which one you pick.

A template is the exported JSON plus documentation: cheap to deliver, easy to copy, and the buyer does the setup. A done-for-you setup means you install and configure the workflow in the buyer's own n8n instance with their credentials: it is a service, priced on time and outcome. A hosted automation means you run it on your side and sell the result (for example, a weekly lead list or enriched data): the buyer never sees the workflow at all.

• Template: low price, high volume, little support
• Done-for-you setup: higher price, fewer sales, clear scope needed
• Hosted result: recurring value, but you carry the running costs and the uptime

2. The main places to sell n8n workflows

There is no single best channel; most sellers combine one discovery channel with one checkout channel. In a public n8n community thread from late 2025, a builder asking where to sell workflows outside the official hub was pointed to the options below.

• The official n8n Creator Hub: tied to the n8n community and template library, which gives free exposure. Community members reported that you must first publish free templates (three, at the time) and that simple submissions can be rejected, so expect a review process.
• General digital-product checkouts such as Gumroad, Lemon Squeezy or Ko-fi: you handle the marketing, they handle payment and file delivery.
• Independent automation-template marketplaces: check that they are active before investing time; some listed sites appeared abandoned or had broken submission forms.
• Your own site plus content (YouTube walkthroughs, posts in automation communities): slower to start, but you own the audience.
• Marketplaces for AI agents and automations, where buyers come looking for a ready-made solution or a setup service rather than a file.

3. Package the workflow so a stranger can run it

Most bad reviews on automation templates come from setup friction, not from the logic itself. Before you export, open the workflow as if you had never seen it.

• Remove every hard-coded API key, token or password from node fields. Exported n8n JSON does not contain your stored credential secrets, but it does contain credential names and anything you typed directly into a node.
• Replace personal data, test emails, sheet IDs and webhook URLs with clear placeholders.
• Add sticky notes inside the canvas explaining each block and what the buyer must change.
• Give nodes descriptive names (Fetch new leads, not HTTP Request 3).
• List the n8n version you tested on, the required community nodes and every external account needed (and whether those services are paid).
• Include a short README: what it does, what it does not do, setup steps, a sample input and the expected output.
• Test the export in a fresh n8n instance before publishing.

4. Price it without guessing

Price relative to the time the workflow saves and the effort it takes to set up, not relative to how long it took you to build. A template that needs two hours of configuration and three paid accounts is worth less to most buyers than a simpler one that runs in ten minutes.

A practical approach: look at what comparable templates sell for on the channel you chose, launch at a price you can defend, and offer the done-for-you setup as a separate, clearly scoped option at a much higher price. Many buyers who see the template realise they would rather pay someone to install it.

• Write down the exact scope of any setup service (which accounts, how many revisions, what is out of scope)
• Say clearly whether updates are included when an API or node changes
• Avoid promising business results such as revenue or time saved that you cannot verify for the buyer

5. Check the rules before you sell

n8n is distributed under its own license terms, and marketplaces each have their own policies. Selling workflows you built, or your setup time, is a different thing from reselling n8n itself or offering n8n as a hosted service to others. Read the current license and the terms of the platform you sell on, and if your model is unusual, get proper advice. Also respect the terms of every third-party API your workflow calls: some forbid scraping or redistribution of their data.

6. Where Kiosq fits

Kiosq is a marketplace for AI agents, bots, prompts, automations, SaaS and small startups. You can list an n8n workflow as a digital product, or sell the setup as an on-demand service. Services are covered by the Kiosq Guarantee: the buyer validates the delivery, gets one free revision if something is off, and can then be refunded, which pushes both sides to agree on a precise scope. Buyers pay in USDC on Polygon, with on-demand services held in escrow until validation; card payment is not available yet. Kiosq also exposes an API and an MCP server, so AI agents themselves can find and order automations.