Back to Tutorials

n8n Community Forum: Where to Get Help with n8n and Community Nodes

Posted by alex@creahive Oct 27, 2026

The n8n community forum at community.n8n.io is n8n’s free support channel for every n8n user. n8n’s documentation calls it the best source for answers of all kinds, because both the n8n support team and community members answer there. This guide covers where to ask which question, what to put in your first post, and where to go when the problem is a community node rather than n8n itself.

Where to ask

Your question Where to ask
How to build something, an error in a workflow, a technical question The n8n community forum (free, all plans)
Technical, account or billing question on an Enterprise plan Email support at help@n8n.io, with an SLA (n8n Cloud Enterprise and self-hosted Enterprise)
Admin or billing question on another n8n Cloud plan Email support at help@n8n.io; technical questions go to the forum
A bug or missing feature in a community node The node’s author, usually through the issues of its repository
A community node that looks malicious or harmful security@n8n.io

The email support details come from n8n’s documentation; check n8n’s pricing page for what your plan includes today.

What to include in your first post

n8n’s documentation says you get help faster when your first message has the details of your instance and your problem. To copy your instance details:

  1. Open the left-side panel and select Help.
  2. Select About n8n.
  3. Select Copy debug information and paste it into your post or email.

Then add what helps someone reproduce the problem:

  • Screenshots or a short screen recording of what happens.
  • Links to any guides or documentation you followed.
  • The steps you took before the problem appeared.
  • The workflow or configuration files involved.
  • For n8n Cloud support, your workspace URL (it looks like https://xxxxx.n8n.app.cloud).
  • If it helps, a HAR (HTTP Archive) file from your browser, with sensitive details removed first.

When the problem is a community node

Community nodes are npm packages written by their own authors, not by n8n. n8n’s documentation describes them as unverified code from a public source, apart from the verified community nodes that n8n inspects and lists in the nodes panel (see Verified vs Unverified n8n Community Nodes). So a bug in a community node usually needs its author: node pages on this site link to the package on npm and, where there is one, to its GitHub repository, where you can see whether someone has already reported your problem.

Some community node problems come from the installation rather than the node. From n8n’s documentation:

  • Error: Missing packages. n8n installs community nodes onto disk and needs the files at startup. With Docker you can lose them when you recreate the container or upgrade n8n. Persist the ~/.n8n/nodes directory (the best option), or set N8N_REINSTALL_MISSING_PACKAGES to true, which may increase startup time and cause health checks to fail.
  • An n8n Cloud instance that crashes and won’t start. In the n8n Cloud console, go to Instance settings, turn on Disable all community nodes and select Save and restart.
  • Turning community nodes off on a self-hosted instance. Set N8N_COMMUNITY_PACKAGES_ENABLED to false.
  • Breaking changes. A new version of a node can break workflows that use it, so be careful when you upgrade.

More on these settings in n8n Community Node Environment Variables. If you are building your own node, see Troubleshooting n8n Community Node Development.

FAQ

Where is the n8n community forum?

At community.n8n.io. It is free for all n8n users, whatever plan or edition you run.

Does n8n answer questions on the forum?

n8n’s documentation says both the n8n support team and community members help on the forum.

Can I email n8n support?

Through help@n8n.io on some plans: Enterprise plans get email support with an SLA for technical, account and billing questions, and other n8n Cloud plans can email about admin and billing. Technical questions on those plans go to the forum.

Who fixes bugs in a community node?

The node’s author. Check the node’s repository for open issues, and report a node you think is malicious to security@n8n.io.