All activity
Lucas Bennettleft a comment
Hey everyone 👋 I built n8n Node Explorer after getting frustrated while building workflows. I knew the community had nodes for what I needed — but finding them was painful. I kept jumping between npm, GitHub, docs, and random repositories just to figure out which node supported the right operation. The real problem wasn’t availability. It was discovery. I wanted to search by intent — like “pdf...
n8n Node ExplorerDiscover the right n8n community node faster
Discover and search through thousands of n8n community nodes in one clean interface.
Search by:
• Node name
• Package name
• Resource name
• Operation name
Currently indexed:
• 2,326 unique nodes
• 2,922 unique resources
• 9,061 unique operations
Instead of jumping between npm, GitHub, and docs, just type what you want to do — like:
“pdf to html”
“whatsapp message”
“image extraction”
“generate audio”
…and quickly find relevant nodes with contextual matches.
n8n Node ExplorerDiscover the right n8n community node faster
Lucas Bennettstarted a discussion
Finding the right n8n community node is harder than it should be.
n8n Node Explorer (https://n8nfind.com/) makes discovery intent-based. Instead of searching for a package name, you can search by: The task you want to accomplish The resource you need The operation you’re looking for This reduces context switching, speeds up workflow building, and helps you uncover nodes you might never have found otherwise. If you build workflows regularly, even saving 5–10...