Where to Get n8n Help: Forum, Discord, GitHub and Support Channels
The Rule Before You Ask Anything
n8n has a genuinely active support ecosystem. The community forum has thousands of solved threads, the Discord moves fast, and the docs cover most standard use cases. Before posting anywhere, run a quick search. The odds that someone has hit your exact issue before are high, and a solved thread gets you an answer in seconds rather than waiting for a reply.
When you do need to ask, the channel you pick matters. Posting a billing question on the community forum will get you a slower, less useful response than emailing support directly. Posting a workflow logic question to support email will get you redirected to the forum. Knowing which channel handles what saves everyone time.
Quick tip: when posting a workflow question anywhere, always include your workflow JSON. Select your nodes on the canvas, hit Cmd/Ctrl + C, and paste the raw JSON into your post inside a code block. Without it, helpers are guessing.
1. The Community Forum
The official n8n Community Forum is the primary support channel for workflow questions. It is heavily moderated by n8n staff and developers, and the search index is deep. Most common problems have already been solved here.
2. The n8n Discord Server
The n8n Discord is where the community moves in real time. It is faster and more conversational than the forum, which makes it good for quick questions, sharing workflows, and getting a second opinion on something you are building. The forum is better for complex, searchable problems that benefit from a structured thread. Discord is better for "does anyone know if X is possible" or "quick sanity check on this approach."
A few things to keep in mind on Discord: responses are not guaranteed and threads do not persist as well as forum posts. If your question is complex or you want it to be searchable for others later, post it on the forum instead. Discord is a complement to the forum, not a replacement.
3. Official Email Support
For account-level issues and anything involving n8n's managed infrastructure, email is the right channel. The community cannot help with these, and posting them publicly is a bad idea anyway.
4. GitHub for Core Engine Bugs
If you have confirmed that a core node or the n8n engine itself is broken across all setups (not just your configuration), open a bug report on the n8n GitHub repository. The repo is actively triaged by the internal product team and releases happen frequently.
Before opening an issue, search existing ones first. Duplicate reports slow down triage. If your issue already exists, add a comment with your environment details rather than opening a new ticket.
GitHub issues are for confirmed bugs in the core engine, not for workflow help or configuration questions. Posting a "how do I do X" question as a GitHub issue will get it closed and redirected to the forum.
5. How to Write a Request That Gets Answered
The quality of the response you get directly mirrors the quality of the information you provide. Whether you are posting on the forum, Discord, or emailing support, include these every time:
6. Official Documentation
The n8n documentation covers every node, credential type, and core concept. It is the first place to check before posting anywhere. The docs are actively maintained and most standard use cases are covered in detail, including the AI agent node, sub-workflows, error handling, and self-hosting configuration.
The docs also include a built-in search that is reasonably good. If you are looking for how a specific node works or what a particular setting does, start there.