# Community nodes directory - NCNodes

**URL:** <https://community.n8n.io/t/community-nodes-directory-ncnodes/115706>\
**Category:** Built with n8n\
**Tags:** product-feedback, community-node, ai\
**Created:** [May 15, 2025, 8:00am UTC](https://community.n8n.io/t/community-nodes-directory-ncnodes/115706 "2025-05-15T08:00:49Z")\
**Posts on this page:** 14\
**Page:** 1

<div class="post-metadata">

**Author:** ![imajus](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/imajus/32/45292_2.png) [@imajus](https://community.n8n.io/u/imajus)\
**Post date:** [May 15, 2025, 8:00am UTC](https://community.n8n.io/t/community-nodes-directory-ncnodes/115706/1 "2025-05-15T08:00:49Z")

</div>

I’m excited to present my project, which adds value to existing n8n community nodes. There are over 1,500 public community nodes that hold more than 4,000 nodes for n8n, but currently there are barriers to widespread adoption:

- The searching is extremely limited.
- Often, the nodes developers don’t include any useful documentation.

🧩 NCNodes is an AI-powered directory of community nodes for n8n that tackles these problems:

- It uses LLM to analyse source code and generate documentation.
- It provides a full-text search function that delivers more relevant results.

Also, it has a dark theme! 😍

 ![ncnodes-example](https://europe1.discourse-cdn.com/n8n/original/3X/3/8/38815781f60395f4b04f6a0189e3fabac199fc60.png)

Try it for yourself and let me know what you think: [https://ncnodes.com](https://ncnodes.com)

I’m eager to get feedback from the community. Let’s work together to shape the future of this product!

---

<div class="post-metadata">

**Author:** ![Miquel\_Colomer](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/miquel_colomer/32/18606_2.png) [@Miquel\_Colomer](https://community.n8n.io/u/Miquel_Colomer)\
**Post date:** [May 15, 2025, 8:22am UTC](https://community.n8n.io/t/community-nodes-directory-ncnodes/115706/2 "2025-05-15T08:22:43Z")

</div>

Hi @imajus

Congratulations!

That’s a very interesting project and provides transparency to the community. That’s really important for all of us 🙂

Related to this, I am also preparing a few tools related with community nodes at [n8nhackers.com](http://n8nhackers.com).

Let me know if you are interested to give you priority access for testing purposes 😉

---

<div class="post-metadata">

**Author:** ![King\_Samuel\_David](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/king_samuel_david/32/83690_2.png) [@King\_Samuel\_David](https://community.n8n.io/u/King_Samuel_David)\
**Post date:** [May 15, 2025, 2:46pm UTC](https://community.n8n.io/t/community-nodes-directory-ncnodes/115706/3 "2025-05-15T14:46:35Z")

</div>

I normally search using [https://www.npmjs.com/search?q=keywords:n8n-community-node-package](https://www.npmjs.com/search?q=keywords:n8n-community-node-package) some cool nodes though thanks for sharing.

---

<div class="post-metadata">

**Author:** ![imajus](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/imajus/32/45292_2.png) [@imajus](https://community.n8n.io/u/imajus)\
**Post date:** [May 16, 2025, 8:30am UTC](https://community.n8n.io/t/community-nodes-directory-ncnodes/115706/4 "2025-05-16T08:30:45Z")

</div>

Yes, the NPM search is the only official way to search for community nodes. However, the problem with it is that, since NPM is a general-purpose registry, it doesn’t provide any n8n-specific features, which degrades the UX.

Unlike NPM, NCNodes includes packages README files in the search context. Furthermore, NCNodes automatically generates node documentation from the source code, providing additional context for the search.

To give a quick example, let’s say we want to search for some Binance-related nodes.  
[Searching in NPM](https://www.npmjs.com/search?q=keywords%3An8n-community-node-package%20binance) returns only 5 relevant results based on a match of the package names: `n8n-nodes-binance`, `n8n-nodes-binance-trade`, `n8n-nodes-binance-spot`, `n8n-nodes-binancespottrade`, `n8n-nodes-binance-extended`. All the results below these are irrelevant and just add to the confusion, to be honest.

On the other hand, [searching in NCNodes](https://ncnodes.com/packages?p=1&s=binance) returns 9 results, all of which are relevant. In addition to the same 5 packages listed in the NPM results, NCNodes was able to find the following: `n8n-nodes-mexc`, `n8n-nodes-indicators`, `n8n-nodes-nano`, `n8n-nodes-finnhub`.

You might be surprised at how many useful community nodes have been around all along, but have been unfairly overlooked by the community. NCNodes removes the blindfolding fog surrounding the n8n community nodes, making them much easier for everyone to discover.

---

<div class="post-metadata">

**Author:** ![Miquel\_Colomer](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/miquel_colomer/32/18606_2.png) [@Miquel\_Colomer](https://community.n8n.io/u/Miquel_Colomer)\
**Post date:** [May 16, 2025, 11:54am UTC](https://community.n8n.io/t/community-nodes-directory-ncnodes/115706/5 "2025-05-16T11:54:57Z")

</div>

Yeah. You are completely right. Easy discovering is basic.

And people usually don’t know what integrations are currently available (many topics claim visibility).

Well done @imajus !

---

<div class="post-metadata">

**Author:** ![King\_Samuel\_David](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/king_samuel_david/32/83690_2.png) [@King\_Samuel\_David](https://community.n8n.io/u/King_Samuel_David)\
**Post date:** [May 16, 2025, 6:21pm UTC](https://community.n8n.io/t/community-nodes-directory-ncnodes/115706/6 "2025-05-16T18:21:04Z")

</div>

Nice, thanks for the info I didn’t know this, will check it out.

---

<div class="post-metadata">

**Author:** ![Entrepositive](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/entrepositive/32/16077_2.png) [@Entrepositive](https://community.n8n.io/u/Entrepositive)\
**Post date:** [May 23, 2025, 8:42pm UTC](https://community.n8n.io/t/community-nodes-directory-ncnodes/115706/7 "2025-05-23T20:42:38Z")

</div>

@imajus - outstanding! And extremely helpful.

@King_Samuel_David - how do you search the NPM site? As far as I can gather it’s basically a luck-of-the-draw if I happen to stumble upon anything I’m looking for (or even just nodes that are interesting). So it’s good for discovery but I haven’t yet figured out how to search and find specific nodes.

E

---

<div class="post-metadata">

**Author:** ![King\_Samuel\_David](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/king_samuel_david/32/83690_2.png) [@King\_Samuel\_David](https://community.n8n.io/u/King_Samuel_David)\
**Post date:** [May 24, 2025, 5:04pm UTC](https://community.n8n.io/t/community-nodes-directory-ncnodes/115706/8 "2025-05-24T17:04:56Z")

</div>

I just use keywords:n8n-community-node-package normally, and the name of node I need, but some are old / may not work, so I try not to use I mainly have the MCP and Ellevenlabs one, I tend to use HTTP request node if there API is available etc.

---

<div class="post-metadata">

**Author:** ![imajus](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/imajus/32/45292_2.png) [@imajus](https://community.n8n.io/u/imajus)\
**Post date:** [May 26, 2025, 6:12am UTC](https://community.n8n.io/t/community-nodes-directory-ncnodes/115706/9 "2025-05-26T06:12:16Z")

</div>

Thanks for your interest!

You may have noticed that some nodes still display the '“Node Analysis Pending” message instead of the documentation. It takes time to process a large number of community nodes source code using AI and generate summaries. Searching will work even better once all existing nodes have been processed.

If you would like certain packages to be analysed first, please use [this](https://api.ncnodes.com/form/cae8b29a-d54b-4602-b192-902c1c4a7146) form.

---

<div class="post-metadata">

**Author:** ![imajus](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/imajus/32/45292_2.png) [@imajus](https://community.n8n.io/u/imajus)\
**Post date:** [June 2, 2025, 7:42am UTC](https://community.n8n.io/t/community-nodes-directory-ncnodes/115706/10 "2025-06-02T07:42:03Z")

</div>

To reflect the recent [update](https://blog.n8n.io/community-nodes-available-on-n8n-cloud/) that allowed installing community packages to the n8n cloud platform 🧩 NCNodes has been updated to showcase these packages.

Community packages available for cloud installation will now feature a special “verified” icon displayed next to their names. Check this package for example:

> **[n8n-nodes-ticktick | n8n community package | NCNodes](https://ncnodes.com/package/n8n-nodes-ticktick)**
>
> TickTick module for custom n8n node.

This update will assist cloud users in filtering for packages they can readily utilize and is designed to encourage community node creators to submit their nodes to n8n for verification.

---

<div class="post-metadata">

**Author:** ![imajus](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/imajus/32/45292_2.png) [@imajus](https://community.n8n.io/u/imajus)\
**Post date:** [November 13, 2025, 12:47pm UTC](https://community.n8n.io/t/community-nodes-directory-ncnodes/115706/11 "2025-11-13T12:47:10Z")

</div>

NCNodes has 5k+ community nodes now! However, there were **~400 extra packages** in NPM that were not present on NCNodes!

The problem was that the indexer relied on keyword `n8n-community-node-package` in package.json, which some of the package developers had not included.

NCNodes now indexes all of them! More visibility for package authors, more tools for self-hosters.

P.S.: It will take a while until all of them are properly indexed and analysed by the backend service.

---

<div class="post-metadata">

**Author:** ![easybits](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/easybits/32/153703_2.png) [@easybits](https://community.n8n.io/u/easybits)\
**Post date:** [February 11, 2026, 4:18pm UTC](https://community.n8n.io/t/community-nodes-directory-ncnodes/115706/12 "2026-02-11T16:18:00Z")

</div>

First of all, this is a great tool with a solid overview of community nodes! Thank you so much for sharing it!

One thought that keeps coming back to me is that I’d love to see an integrated node assistant. I’d imagine being able to explain what I’m trying to solve, and having the assistant suggest the right nodes based on that.

The main issue I see with these types of pages is the paradox of choice. There are so many options that users might pick one, but if it turns out to be the wrong fit, the ‘start-over’ process is super frustrating. I’d love to know if others would find a feature like this valuable as well.

---

<div class="post-metadata">

**Author:** ![imajus](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/imajus/32/45292_2.png) [@imajus](https://community.n8n.io/u/imajus)\
**Post date:** [August 21, 2026, 9:48pm UTC](https://community.n8n.io/t/community-nodes-directory-ncnodes/115706/13 "2026-08-21T21:48:24Z")

</div>

@easybits thank you for feedback. This is a great idea and we already have it in our [roadmap](https://ncnodes.com/roadmap).

---

<div class="post-metadata">

**Author:** ![imajus](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/imajus/32/45292_2.png) [@imajus](https://community.n8n.io/u/imajus)\
**Post date:** [August 21, 2026, 9:55pm UTC](https://community.n8n.io/t/community-nodes-directory-ncnodes/115706/14 "2026-08-21T21:55:09Z")

</div>

In the meantime, we’ve been working to improve n8n nodes search quality.

It was not only tuning the matching algorithm, but also excluding duplicate packages with no added. [NCNodes](https://ncnodes.com/packages) now spots when packages ship the same nodes and shows you the one the community actually uses. That’s over 1,6k near-identical copies out of your way.

There’s an option to toggle this off and get a full listing, if you choose to.

This is how it looks in the UI. Searching by ‘chatwoot’ now returns 43 results, but before it was 82.

 ![Screenshot From 2026-08-22 02-42-11](https://europe1.discourse-cdn.com/n8n/original/3X/b/e/be29e72bdbe95fa06f3e110a073fb1e4fafbe1d2.png)
