How n8n got its users

Stand up a Discourse forum before you launch and run its Feature Requests category as the public roadmap. Jan opened community.n8n.io/t/shopify-integration/22 himself, a month before launch. Then he pushed every "it lacks X" comment there: post it as a request, others upvote, he builds in vote order. Shipped ones get a status tag right in the title, [GOT CREATED], and move to Feature Requests (done). The complaint becomes a queue you own instead of an argument you lose.

done whenA month in, are strangers opening feature requests you never asked for, and can you name your top three by vote count without looking?

Launch on Hacker News and answer under your own handle, all night, including the people calling you dishonest. Jan replied as janober down nearly every branch of the 2019 n8n thread, fixed reported typos mid-thread ("Got fixed in the meantime"), added a license FAQ section to the docs while the thread was live, and posted license@n8n.io for anyone unsure. Mods retitled the post from "open source Zapier alternative" to "Workflow automation alternative to Zapier" and left it standing.

done whenCount replies against comments on your own launch thread. If the harshest comment is the one you skipped, you did not run this play.

Make the unit of help pasteable. In n8n you select nodes on the canvas, Cmd+C, drop the raw JSON into a forum reply, and the asker hits Cmd+V on their own canvas and it runs. That is why answers in "Help me Build my Workflow" travel: each one is a working object, not instructions. Find your equivalent, a config block, a snippet, a share URL, and make it copy in and out in one keystroke before you spend an hour in anybody's forum.

done whenCan a stranger go from your forum answer to a working result in one paste, with zero setup steps in between?

Turn every good forum answer into a permanent page at n8n.io/workflows, filed under AI, Sales, IT Ops, Marketing, Document Ops or Support, and browsable by the stack it touches: Google Sheets, OpenAI, Telegram, Slack, Notion. Each page is the landing spot for "tool A to tool B" searches. Submissions go through creators.n8n.io, which emails back what to change before approval. With no audience you write the first batch yourself, titled after the tool pairs people already search.

done whenAre your template pages pulling search traffic on queries that name a tool you connect to, rather than your own product name?

Publish the rules that let strangers extend you in public. n8n's docs fix the shape: package name starts with n8n-nodes-, keyword n8n-community-node-package, nodes declared in the n8n attribute of package.json, scaffolded by npm create @n8n/node. Verified ones show up in the in-app nodes panel, so a stranger's package reaches users inside your product. Top template authors get a Verified Creator Badge, a Creators Directory listing and a private Discord channel.

done whenHas anyone shipped an extension you did not commission, and did they follow your naming convention without you telling them to?