Support Community

Where to Get Help in n8n

Published on Mar 21, 2026 · By Anshul Namdev

The Golden Rule of n8n Support

As you build increasingly complex workflows, you will inevitably hit a wall - an API endpoint throwing a 400 error, a node behaving unexpectedly, or a complex JSON mapping issue. When this happens, knowing exactly where to ask for help is the key to solving your issue rapidly. The right channel guarantees a fast resolution.

1. The Community Forum

The official n8n Community is extremely active and moderated heavily by official n8n staff and developers.

  • When to use it: Workflow design questions, custom JavaScript/Code node logic, debugging API errors, and asking if a specific third-party integration is possible.
  • When NOT to use it: Issues relating to n8n Cloud billing, workspace provisioning errors, or highly sensitive internal data leaks.

When posting in the community, always attach a copy of your workflow. You can easily do this by selecting your nodes on the canvas, hitting Cmd/Ctrl + C, and pasting the raw JSON directly into your forum post within code blocks!

2. Official Email Channels

For administrative or deeply technical edge-cases relating to the n8n managed services, bypassing the forum is critical.

  • support@n8n.io or help@n8n.io: Use these exclusively for n8n Cloud account issues, billing discrepancies, enterprise licensing inquiries, or catastrophic managed-infrastructure failures.
  • nodes@n8n.io: A highly specialized channel for when you are developing custom community nodes from scratch and need technical architectural assistance from the core integration engineers.

3. How to Write a Flawless Support Request

Whether you are posting on the forum or emailing support, the quality of their response directly mirrors the quality of your prompt. You must always include:

  1. Your Execution Environment: Are you on n8n Cloud, Docker Self-Hosted, or NPM local? Let them know.
  2. Exact Version Number: Bugs are often patched daily. Stating you are precisely on `v1.33.0` helps engineers isolate regressions.
  3. Instance Hash (Cloud only): If emailing Cloud Support, give them your workspace URL or internal workspace ID so they can check the internal logs immediately.
  4. Clear Error Logs: Do not just say "It failed." Paste the exact JSON output error trace of the failed execution node.

4. GitHub for Core Engine Bugs

If you have definitively proven that a core node is fundamentally broken or throwing unhandled exceptions across all setups, you should open a bug report directly on the n8n GitHub Repository. The repository is heavily monitored by the internal product triaging team and updates happen frequently.