Can't find several nodes by searching or browsing manually

Hey n8n community!

I’m fairly new here, so forgive me if this is a very obvious answer - but I can’t seem to find some seemingly core nodes anywhere… They don’t appear if I search the nodes panel, or if I browse manually to where I’d expect to see them. The only way I can get them into a workflow is by copying the code from someone else on the forums workflow.

Is there a setting to change which nodes are visible in the panel, or am I using the search wrong?

I’ve forgotten some of the nodes this has happened to, but recently it’s been:

  • Read Binary File
  • Item Lists

Any help much appreciated!

Information on your n8n setup

  • n8n version: 1.85.4
  • Database (default: SQLite): SQLite
  • n8n EXECUTIONS_PROCESS setting (default: own, main): default?
  • Running n8n via (Docker, npm, n8n cloud, desktop app): Docker
  • Operating system: Synology DSM7
1 Like

If it’s the first node you are adding, the list is limited to triggers. See if you find what you are looking for after you add a manual trigger node.

Unfortunately not, I had quite a lot of the nodes fleshed out with a manual trigger on this one, and I’m encountering the same issues on a few other workflows which are similarly populated too.

Apologies for not noticing initially which nodes you were referencing. The forums and templates, especially older items, often reference nodes that have been “removed” (but not completely) from n8n and replaced with other nodes.

  • Read Binary File - Replaced with Read/Write Files from Disk
  • Item Lists - Replaced with Aggregate, Limit, Remove Duplicates, Sort, Split Out, and Summarize

Instead of removing the old nodes completely (and breaking older workflows), those nodes are marked as “hidden” so they’re not easily added to any new workflows.

So, when you are looking for something referenced in an older template or an older forum post, and can’t find it in the current/recent n8n version’s node list, try searching the documentation to see if there is a replacement, or take a look at the source code to see if it’s there, but marked hidden.

1 Like

Ah, that makes sense. Thanks for the clarification!

Too much reliance on tutorials at my end it seems…

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.