Why I Took Three n8n Templates Off Gumroad

Three n8n templates that used to sit on my projects page are gone now: Stop Sorting Support Emails Manually, Lead Capture Automation for n8n, and the free Launch Content Pack. I pulled all three off Gumroad in the same week I wrote about how I package n8n workflows for resale, which is an odd thing to admit right after a whole post about the packaging process. The packaging wasn’t the problem. Where they lived was.

What actually happened

Nothing dramatic. No refund wave, no bug that broke trust, no single event I can point to. Stop Sorting Support Emails Manually had gone up recently enough that I never had sales numbers worth reporting for it in the first place. Lead Capture Automation was narrow and functional, form in, sheet row and two emails out, the same single-purpose shape I described as “standing alone” in the packaging post. Launch Content Pack was free, built mostly as a lead-in to the paid templates rather than something I expected to carry weight on its own.

None of the three failed loudly. They sat on Gumroad without anything pushing traffic toward them, and at some point I stopped believing that was going to change by itself.

The same lesson, applied a second time

I already wrote about this pattern once, explaining why I opened a shop on Etsy instead of trying to make Gumroad carry every kind of product I build. The Obsidian plugins sell because Obsidian’s own plugin directory puts them in front of people already searching for that exact kind of tool. Etsy works the same way for the products that fit there, a search engine with a checkout attached. Gumroad by itself is just the checkout. It converts once someone already knows what they want, but it doesn’t put a niche automation template in front of a stranger who has never heard of it.

n8n templates should, in theory, get the same advantage the plugins do. n8n.io runs its own template library, and I’d assumed that would function like Obsidian’s directory. But listing something on Gumroad doesn’t automatically put it in front of n8n.io’s search traffic, and I never did the separate work of getting these three properly into that library. So they ended up in the worst spot: a niche product, on a platform with no discovery layer of its own, with no community or search intent doing any of the finding for me.

What I did instead of quietly deleting them

I didn’t unlist them and pretend they never existed. The packaging post and the $json bug post still reference them, now with a note that they’ve been taken down instead of a dead link to a product page that no longer exists. The workflows themselves aren’t gone either. The credential-stripping and guide-writing work is still there if I fold them into a themed bundle later, or list them properly in n8n.io’s own library instead of only on Gumroad.

Where this leaves things

I don’t have a number to attach to this one, no sales count that proves the platform mismatch over some other explanation, because I never let these run long enough with enough traffic to know for sure. What I do have is the same reasoning that’s shown up in most of my other builds: a product doesn’t sell because the build is good, it sells because it’s sitting where its buyer is already looking. Three templates without that turned out to not be worth maintaining as separate listings. The next automation product I ship goes wherever that buyer actually searches first, bundled, listed properly in n8n’s own library, or not built as a solo Gumroad listing at all.