Sell your n8n workflows: package a tested template as a product people pay for
n8n's gallery holds 1,311 paid templates from 282 creators, at a median price of $20. A tested workflow with instructions a stranger can follow in 15 minutes earns its place among them. Nobody publishes sales counts, so plan around the work: a clean file, a setup guide, a demo, a price, and the setup jobs each sale brings in.
- The kit: setup guide, product page copy, changelog, support policy, pricing calculator, scoreboard and an example product file
- A few n8n workflows built and run already. New to it? Do Your own Zapier first
- Automate a small business's boring admin read through: its six workflows are good product starting points, and this mission reuses its licence step and its setup service
- Python 3.8 or newer for the scrub script (check with
python --version). No other installs - Useful alongside: Sell templates, the sister course on selling digital templates, and Make it legal for tax and invoices
Know what a workflow product is, and what it takes
The JSON file is the easy bit. The product is everything that gets a stranger from download to working in 15 minutes.
Here's the gap. n8n's gallery is full of clever workflows with one line of instructions and a sticky note that says "add your API key". People download them, get stuck on step two and give up. A workflow that's been run for a real business, cleaned up, and explained properly is a different thing. That's what people pay for.
A workflow product has five parts:
- The workflow (.json): imports with no errors, every node named for what it does, one settings node, one yellow Read me first sticky note, placeholders in CAPITALS, and no credentials, keys or test data inside.
- A setup guide: every step with a screenshot, the exact data table columns, which credentials to create, a test that proves it works, and a troubleshooting table.
- A short demo video (2 to 3 minutes): it running end to end. It sells the product and answers half the support questions before anyone asks.
- A support and refund policy: what you help with, how fast, what you don't do, and what happens if it doesn't work.
- A version number and changelog: which n8n version it was built for, and what changed in each update.
Who actually buysThe person paying for an n8n template already uses n8n, or is about to. That's freelancers and small agencies who build for clients, operations people in small companies, and technical business owners. The plumber isn't browsing n8n's gallery. Your buyer wants to skip hours of building and testing, which is why the setup guide matters as much as the workflow.
What the market looks liken8n's template gallery ↗ lists over 13,000 templates. Counting the paid ones through the gallery's public listing gives 1,311 paid templates from 282 creators. So nine in ten are free, and a paid one has to be clearly better documented, more specific, or both.
CarefulWhat it takes. The gallery shows prices, not sales (nobody publishes sales counts), so plan around the work rather than a sales forecast. A good first product takes 2 to 3 weeks of evenings to build, test and document. Listing a paid template in n8n's own gallery needs 3 approved free ones first (step 3). Sales build as you learn what buyers want, so build the setup offer in from day one: a good product proves you can build, and that brings in setup work (step 8). Who this suits: you've built and run a few n8n workflows, and you enjoy writing clear instructions and answering support emails. Keep your day job while you build it. Everything here works on free tools and free plans, so there's nothing to spend upfront.Your first 30 daysThe rest of the course fills in each part:
- Week 1: pick and prove. Choose one job (step 2). Build it and run it for a real business: your own, a friend's, or a client from the admin automation course. Start the scoreboard.
- Week 2: harden and document. Settings node, named nodes, sticky note (step 4). Scrub the export, test on a fresh n8n, write the setup guide (step 5). Submit a separate, smaller free template to n8n's gallery to start your path to verified creator.
- Week 3: list it. Record the demo. Write the product page. Set up Payhip or Gumroad (step 6), buy it yourself once to test delivery, and start the weekly routine (step 8).
- Week 4: support and adjust. Answer every question within 2 working days and turn each one into a line in the guide. Release 1.0.1 if you fixed anything. Offer a setup call to anyone who got stuck. Read the scoreboard, change one thing.
Everything is in the kit: download it as a zip (31KB) or read kit.md in your browser. It has the scrub script and its tests, an example product file, templates for the setup guide, product page, changelog and support policy, the pricing calculator and the scoreboard.