Run n8n Locally for Free with Docker (Part 8 of 10): Installing Community Nodes
By Abhishek Patoliya · 2026-08-12
This is Part 8 of the series on running n8n locally with Docker for free. n8n's built-in node library covers most common apps and APIs, but not every one of them — community nodes fill that gap, and this part covers installing one on your local Docker setup safely.
← Back to the full series index
What a Community Node Actually Is
A community node is an npm package, built by someone outside the n8n core team, that registers one or more new nodes in n8n's editor — usually an integration for a specific app that doesn't have an official node yet. Once installed, it behaves exactly like a built-in node: draggable onto the canvas, configurable, connectable to anything else.
Installing Through the UI (Easiest)
On a self-hosted instance, go to Settings → Community Nodes inside n8n, and search for the package by its npm name (community nodes are typically named n8n-nodes-*). Click install, and n8n handles downloading and registering it — no terminal required.
Installing From the Command Line
If you'd rather install it directly, exec into the running container and use n8n's own CLI:
docker exec -it n8n n8n community-node install n8n-nodes-example
Replace n8n-nodes-example with the actual package name. Restart the container afterward so n8n picks up the new node:
docker compose restart
Vetting a Node Before You Trust It
A community node runs with the same level of access as n8n itself — including any credentials that pass through it. Before installing one, especially for a workflow handling real credentials:
- Check the npm download count. A widely-used package has had more real-world scrutiny than one with a handful of downloads.
- Look at its GitHub repository. Recent commits, responded-to issues, and a reasonable number of contributors are good signs; an abandoned repo with old open issues is a caution flag.
- Read through what the node actually does before connecting it to a credential with real access — for anything sensitive, a quick look at the package's source is worth the few minutes it takes.
Where Installed Nodes Actually Live
Community nodes get installed into the same data directory mounted by the volume set up in Part 4 (/home/node/.n8n), which means they persist across container restarts and even a full docker compose down / up cycle — the same durability your workflows already have.
Removing a Node
From the same Settings screen, or via the CLI:
docker exec -it n8n n8n community-node uninstall n8n-nodes-example
Restart the container afterward for the change to take effect in the editor.
Next Up
With your local instance now customized, Part 9: Backing Up and Restoring Your Instance covers making sure none of it — workflows, credentials, or installed nodes — is one disk failure away from being gone.
Written by Abhishek Patoliya, Senior n8n Developer & Automation Architect, Surat, India. Verified n8n Creator.