n8n community nodes: install them without breaking your instance
Community nodes are npm packages that add nodes to n8n. They fill gaps, but they run with the same access as n8n itself, and n8n 3.0 changes the default for unverified ones. Here is what is out there, how each install path works, and a short checklist before you add one.
What to know first
- Community nodes have full access to the machine n8n runs on and to the data in your workflows, per n8n's risks page.
- n8n 3.0 turns unverified packages off by default.
N8N_UNVERIFIED_PACKAGES_ENABLEDchanges from true to false, and installed unverified nodes stop loading after the upgrade (3.0 breaking changes). - Public templates rarely depend on them. In our study of 13,574 public n8n templates, only 18 templates (0.1%) contain a node n8n.io marks as community or non-native, so most templates import without extra packages.
Want to know which ones people actually use? See the most-used n8n community nodes, ranked monthly by npm downloads and how much usage they keep.
How many community nodes are there?
An npm search for the keyword n8n-community-node-package, the tag n8n's install screen uses, returned 13,941 packages on Oct 26, 2026. n8n's own public catalog (api.n8n.io/api/community-nodes) listed 2,010 nodes from 1,518 packages, about 11% of the npm total. In that catalog:
- 1,716 of 2,010 nodes (85%) were created in 2026.
- 1,391 (69%) are marked usable as an AI agent tool.
- 690 (34%) carry a company name, such as Apify, DataForSEO, Crowdin, Zoho and IONOS Cloud.
We don't treat the catalog as the verified list; n8n doesn't say the two are the same. Download figures in the catalog don't match npm's own counts, so we don't rank by them.
Four ways to install
| Method | Where | Who | Notes |
|---|---|---|---|
| Nodes panel (verified nodes) | Cloud and self-hosted | Owner and Admin | Verified nodes only. On Cloud, the owner can hide them under Instance settings |
| Settings > Community nodes (from npm) | Self-hosted | Owner and Admin | Any npm package. You must tick “I understand the risks…”. To change version, uninstall and reinstall (GUI docs) |
| Manual npm install | Self-hosted | Server access | Needed for queue mode and private packages (manual docs) |
| Environment variables | Self-hosted, n8n 2.21.0+ | Server access | N8N_COMMUNITY_PACKAGES with N8N_COMMUNITY_PACKAGES_MANAGED_BY_ENV=true. Packages not in the list are uninstalled (env docs) |
Before you install one: a checklist
- Check for a built-in way first. The HTTP Request node or the Code node can call most APIs without new code on your server.
- Prefer verified nodes. n8n vets them against data and system security rules, and they keep working on n8n 3.0 defaults.
- Read the package. Look at the npm page, the repo, the last publish date and the maintainer. Pin the version you tested.
- Persist it. In Docker, keep
~/.n8n/nodeson a volume, or setN8N_REINSTALL_MISSING_PACKAGES=true, which can slow startup (troubleshooting). - Plan for 3.0. List the unverified packages you use. Either move to verified ones or set
N8N_UNVERIFIED_PACKAGES_ENABLED=trueon purpose. - Know the off switch.
N8N_COMMUNITY_PACKAGES_ENABLED=falsedisables community nodes on self-hosted n8n. On Cloud, the console can stop them loading if the instance won't start.
Where n8n 3.0 sends you to a community node
n8n 3.0 removes the SerpApi (Google Search) node with no direct replacement. The docs suggest calling SerpApi's API with the HTTP Request node as a tool, or using a verified community node. n8n's catalog lists one from SerpApi itself (“SerpApi Official”). The same release removes the deprecated defaults.color property, which only matters if you build nodes.
If you publish a node
To be verified, a node must be published from GitHub Actions with an npm provenance statement (required since May 1, 2026), use @n8n/node-cli 0.23.0 or later, and pass n8n's verification guidelines, including no run-time dependencies. n8n says it can reject nodes that compete with its paid features (submission docs). Report a bad node to security@n8n.io; n8n keeps a blocklist of nodes that can't be installed.
Check a workflow for community nodes
Paste any workflow JSON into the free n8n workflow checker. It flags community nodes and removed nodes before you import, and runs in your browser. The built-in nodes it checks against are in the n8n node library, for example AI Agent and Webhook.
Sources: n8n docs on community nodes, risks, troubleshooting, submission and the 3.0 breaking changes; n8n's community node catalog; the npm registry search. All read Oct 26, 2026.
Related
- Most-used community nodesMonthly ranking by downloads and retention
- Activepieces vs n8nCredits vs executions, plans and app coverage
- n8n use casesWhat 13,574 public templates are built to do
- n8n node libraryUsage data and known problems for the 22 most used nodes
- 25 free n8n templatesImport-ready JSON, plus a free workflow checker
- n8n pricingPlans, executions and a cost calculator
Questions
- Are n8n community nodes safe?
- Not by default. n8n's docs say they have full access to the machine n8n runs on and to your workflow data. Verified nodes are vetted by n8n; others are unverified code from npm.
- Can I use community nodes on n8n Cloud?
- Verified community nodes, yes, from the nodes panel. Installing any package from npm is documented for self-hosted n8n.
- What changes in n8n 3.0?
- N8N_UNVERIFIED_PACKAGES_ENABLED defaults to false. You can't install unverified nodes from npm, and installed ones stop loading, unless you set it back to true.
- How many n8n community nodes are there?
- On Oct 26, 2026, npm had 13,941 packages tagged n8n-community-node-package, and n8n's public catalog listed 2,010 nodes from 1,518 packages.
- Why did my community nodes disappear after a Docker update?
- The packages live in ~/.n8n/nodes. Keep that folder on a volume, or set N8N_REINSTALL_MISSING_PACKAGES=true so n8n reinstalls them at startup.