n8n community node not showing up, or gone after an update? Where community nodes really live, and how to install them on n8n Cloud, Docker, queue mode, and several servers so they stay installed.
Launch your n8n integration - NativeShip.io
In this video:
- n8n Cloud vs self-hosted: Cloud installs verified community nodes only
- Installing from Settings - Community nodes, with a version
- Why a search finds nothing: node name vs package name
- Why Docker loses community nodes on update, and the volume that fixes it
- N8N_REINSTALL_MISSING_PACKAGES and its cost
- Queue mode and private packages: manual install with npm
- N8N_COMMUNITY_PACKAGES_MANAGED_BY_ENV and N8N_COMMUNITY_PACKAGES (n8n 2.21+)
- N8N_COMMUNITY_PACKAGES_PREVENT_LOADING when a node stops n8n from starting
Chapters
0:00 It was there yesterday
0:34 n8n Cloud vs self-hosted
1:14 Installing from Settings
1:51 Why Docker loses community nodes
2:40 Queue mode and private packages
3:17 One list for every server
3:59 When a node stops n8n from starting
4:28 Recap
From the n8n docs
Installation and management: Installation and management | Nodes | n8n Docs
Troubleshooting: Troubleshooting | Nodes | n8n Docs
Environment variable installation: Environment variable installation | Nodes | n8n Docs
Build your own node instead? A 10-part series, from an empty folder to a verified n8n community node: https://www.youtube.com/playlist?list=PLYkThRYZ5f5g