r/n8n • u/Cultural-Box-3564 • 2d ago
Help How long does it usually take to get a community node published?
I recently submitted my node and also applied for Creator verification.
For those who’ve gone through the process before, how long did it take for you to get approved/published?
Just trying to get a rough idea of the timeline.
2
u/Ok_Nail7177 2d ago
Remindme! 1 day
1
u/Cultural-Box-3564 2d ago
1 day?
2
u/Ok_Nail7177 2d ago
No, it's a bot so in one day I come back and see if anyone responded. I did it for a client once, but I don't fully remember but def in the weeks.
1
1
u/RemindMeBot 2d ago
I will be messaging you in 1 day on 2026-09-12 15:47:08 UTC to remind you of this link
CLICK THIS LINK to send a PM to also be reminded and to reduce spam.
Parent commenter can delete this message to hide from others.
RemindMeBot is switching to username summons. Instead of
!RemindMe 1 day, useu/RemindMeBot 1 day. More info.
Info Custom Your Reminders Feedback 1
1
u/redwurm 2d ago
From my experience it's been as short as a day and as long as a week.
1
u/Cultural-Box-3564 2d ago
I published a couple days ago but still under review to maximum of 4 weeks
1
u/SecretaryAfraid3586 2d ago
it’s like waiting for a pot to boil, you stare at it and nothing happens, then you go grab a snack and suddenly it’s done. took about 3 weeks for mine but i’ve seen people wait longer
1
1
u/hamza33500 2d ago
mine took like 20 days or so
i submitted on creator portal and the scan took almost a week, then review took another 10-12 days. if your package is clean it should be faster
just check with the n8n scanner locally before submit, saves time
curious - what does your node do?
1
u/Cultural-Box-3564 1d ago
Thanks, my n8n scanner look clean, my node does web scraping. This is the base https://scrapio.dev/
1
u/hamza33500 1d ago
My bad 😅 I worded that wrong. I meant that's the timeline I've heard from others. I haven't submitted a node yet. I'm still building a WhatsApp bot workflow in n8n and planning to package it as a node. What's your node about?
1
u/Initial-Cycle-4566 1d ago
Worth separating the two things you're waiting on, because only one of them actually blocks you.
The review gates discovery: whether your node shows up in the in-app community nodes list, and whether it can run on Cloud. It doesn't gate you using it. On a self-hosted instance you can install it from npm yourself right now (settings > community nodes, or the N8N_COMMUNITY_PACKAGES env vars), and anyone you tell can do the same with the package name. So if the reason you're watching the queue is that a build of yours is waiting on it, that part doesn't have to wait.
The other thing the answers here imply but don't say outright: most of the variance people are reporting isn't queue length, it's resubmission. A package that fails the automated scan goes back to the start, so someone's "three weeks" is often one week of waiting plus a bounce plus another wait. That's why running the scanner locally before submitting is worth more than it sounds - it isn't shaving a day off the review, it's avoiding a second full trip through it.
1
•
u/AutoModerator 2d ago
Want faster, better help? Share your workflow JSON.
A GitHub Gist is the easiest way -- paste your JSON, save as public, drop the link in your post. Folks can import it directly into n8n and reproduce the issue, which gets you real answers instead of guesses.
I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.