I published two open source n8n community nodes six weeks ago and did absolutely nothing to promote them. No blog posts, no tweets, no Reddit threads, no Product Hunt.
In the first week they hit 900 combined downloads purely through organic npm and n8n community node discovery. They're sustaining ~300 downloads/week.
Here's what I built:
n8n-nodes-ffmpeg-wasm — FFmpeg compiled to WebAssembly, running inside n8n with zero server dependencies
The problem I kept hitting: n8n workflows that need video processing require FFmpeg installed on the host. Custom Docker images, system packages, binary management. I wanted something you could npm install and have work immediately.
So I compiled FFmpeg to WebAssembly. It runs entirely inside Node.js — no system binary, no Docker modifications. Install the node, restart n8n, and you have 21 video/audio operations: convert formats, resize, trim, merge, thumbnails, GIFs, social media presets (Instagram Reels, TikTok, YouTube, Twitter), subtitle burn-in, audio normalization, and custom FFmpeg commands.
n8n-nodes-youtube-dl — Download from YouTube and 1000+ sites inside n8n workflows
Powered by yt-dlp. Download video, audio, transcripts (with timestamps — great for AI summarization workflows), subtitles, and metadata. Auto-downloads the yt-dlp binary on install. Zero config. Zero runtime dependencies.
Together they give you a full video pipeline inside n8n: download content → process it → output it anywhere.
The numbers:
What I learned: Solving a real pain point with zero friction (npm install → works immediately) gets organic traction even before you say a word about it. The “zero dependencies” angle resonated — it’s the specific thing people hate about dealing with FFmpeg in automation.
Links:
Happy to answer questions about the technical approach (WASM + Node.js) or the n8n node ecosystem.
No responses yet.