Where to Get n8n Help
Every support channel, when to use each one, and how to write requests that actually get answered.
The Rule Before You Ask
Search first. The n8n community forum has tens of thousands of solved threads covering every node, every common error message, and most edge cases you will encounter. The official documentation is maintained daily and covers every credential type, expression syntax, and hosting configuration. Before you write a single word of a support request, spend two minutes searching. Most questions have already been answered.
When you do need to ask, the channel you pick matters. Posting a billing question on the community forum gets slower results than emailing support@n8n.io directly. Posting a workflow logic question to the support inbox gets you redirected back to the forum. Knowing which channel handles what saves everyone time, including yours.
The pattern that works: Search the forum and docs first. If the answer is not there, choose the right channel from the list below. Include your environment details, exact error output, and workflow JSON. That combination gets answers faster than anything else.
The Community Forum
The forum at community.n8n.io is the primary support channel for n8n. It is heavily moderated by n8n staff and core developers, with a deep search index built over years of solved threads. When you post a well-structured question here, you can expect a response from either the community or an n8n team member within hours, sometimes minutes.
The forum also hosts the n8n Academy subforum for course-specific questions: enrollment issues, grading problems, certificate questions, and badge support. If your question is about an Academy course, post it there rather than in the general help section.
Forum Topics
- Workflow design and logic questions
- Code node JavaScript or Python help
- Debugging API errors and node behavior
- Third-party integration questions
- Self-hosting setup and configuration
- Feature requests and general discussion
The majority of n8n questions belong here. Searchable, structured, and monitored by staff.
Visit the Forum →Use Other Channels
- n8n Cloud billing or payment issues
- Workspace provisioning errors
- Sensitive internal data or credentials
- Enterprise licensing questions
- Managed infrastructure failures
These require direct access to your account. Email support handles them faster and more securely.
See Email Support →The Discord Server
The n8n Discord server is where the community moves in real time. It is faster and more conversational than the forum, which makes it the right place for quick questions, workflow sharing, sanity checks on an approach, and casual discussion about what people are building. Active channels cover general help, workflow showcases, AI automation, and community projects.
Discord is a complement to the forum, not a replacement. Threads do not persist as well, search is weaker, and complex problems get buried under new messages. If your question requires a structured back-and-forth with code blocks and screenshots, the forum is the better choice. If you need a quick "is this possible" or "has anyone tried X," Discord is faster.
Keep in mind: Responses on Discord are not guaranteed. The community is helpful, but staff monitoring is lighter than on the forum. For anything mission-critical or time-sensitive, use the forum or email support.
Official Documentation
The documentation at docs.n8n.io covers every node, credential type, and core concept in n8n. It is actively maintained, versioned, and includes a built-in search that handles most lookups well. Before posting anywhere, check the docs. The answer is often already there, written by the people who built the feature.
Specific sections worth bookmarking: the hosting documentation for self-hosted deployment, the node reference for every integration's parameters and options, the expressions guide for data manipulation syntax, and the AI agent documentation for building agents with tools, memory, and chains. The Academy at learn.n8n.io provides structured courses if you prefer a guided learning path.
For a full breakdown of every Academy course, grading, and certificates, see our dedicated guide:
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. n8n maintains three dedicated email addresses, each routed to a different internal team.
Cloud account issues, billing, workspace provisioning, managed infrastructure. Use this for anything related to your n8n Cloud subscription: payment discrepancies, workspace creation failures, execution quota questions, and infrastructure outages on Cloud-hosted instances.
Enterprise licensing, subscription management, execution top-ups. If you are on an enterprise plan or need to discuss annual contracts, volume licensing, or purchasing additional execution credits, this is the inbox that reaches the right team.
Custom community node development, architectural guidance. Building a community node from scratch and need input from the core integration engineers? This inbox connects you with the team that maintains the node SDK and can advise on architecture, testing patterns, and publication.
When emailing any of these addresses, include your workspace URL (for Cloud issues), your n8n version number, and a clear description of the problem. The more context you provide upfront, the fewer back-and-forth emails it takes to reach a resolution.
GitHub for Core Bugs
The n8n GitHub repository is the place to report confirmed bugs in the core engine. If a built-in node behaves incorrectly across all environments, if the execution engine produces wrong output, or if the UI has a reproducible defect, open an issue. The repository is actively triaged by the product team, and n8n ships releases 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. When filing a new issue, include your n8n version, your execution environment (Cloud, Docker, or NPM), steps to reproduce the bug, and expected vs. actual behavior.
Important: 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. If you are unsure whether something is a bug or a configuration problem, post on the forum first.
How to Write a Request That Gets Answered
The quality of the response you receive directly mirrors the quality of the information you provide. Whether you are posting on the forum, chatting on Discord, or emailing support, including the right details upfront eliminates the back-and-forth that delays resolution. Every support request should contain these five pieces of information.
-
01
Execution environment. State whether you are running n8n Cloud, Docker self-hosted, NPM local install, or a managed platform like Railway. Each environment has different constraints, and the answer often depends on which one you are using.
-
02
Exact n8n version number. Bugs get patched frequently. Stating that you are on version 1.115.3 helps engineers determine whether the issue is a known regression, a fixed problem, or something new. Find your version in Settings > About.
-
03
Exact error output. Do not write "it failed." Paste the full JSON error trace from the failed execution node. Open the node output panel, switch to the JSON tab, and copy the complete error object. Screenshots of error messages are also useful, but the raw JSON is what engineers need.
-
04
Workflow JSON. Select your nodes on the canvas, press
Cmd/Ctrl + C, and paste the raw JSON into your post inside a code block. Without this, helpers are guessing at your node configuration, expression syntax, and connection logic. -
05
Workspace URL (Cloud support). When emailing Cloud support, include your workspace URL or internal workspace ID so they can pull execution logs immediately without requiring additional emails.
A well-structured post with all five details typically gets a useful response on the first reply. A vague post without context can take three to five exchanges before anyone can help. The difference is five minutes of your time upfront.
Support FAQ
The most common issues people run into, with actionable steps for each. Click any question to expand.
My workflow fails silently
- Check execution logs: Open the Executions panel from the left sidebar. Every workflow run is logged there with its status, even if no error notification appeared. Look for executions marked as "Error" and click into them to see which node failed.
- Enable error workflows: In your workflow settings, set an Error Workflow that triggers whenever an execution fails. This ensures you are notified of failures rather than discovering them later. The Error Trigger node gives you the full error context.
- Inspect individual node output: Click on each node in the failed execution to see its input and output data. Silent failures often happen because a node returns empty data rather than throwing an error. Check whether the output tab shows items or is empty.
Node shows "no data" after execution
- Expression errors: The most common cause is a broken expression reference. If you reference
{{ $json.fieldName }}but the incoming data uses a different key, the node processes zero items. Check the input data structure against your expressions. - Empty API response: The upstream API might be returning an empty result set. Test the API call independently (using the HTTP Request node with manual execution) to confirm it returns data. Check filters, date ranges, and pagination parameters.
- Item mismatch: If you use a Merge node or a loop, items can get filtered out unexpectedly. Use the "Always Output Data" toggle on relevant nodes to ensure the workflow continues even when a node produces zero items.
Webhook URL not triggering
- Check if the workflow is active: Webhook triggers only work when the workflow is toggled to Active (the switch in the top-right corner). While building, you can use the "Test URL" displayed in the Webhook node, but in production the workflow must be active to use the Production URL.
- Verify the URL matches: n8n provides two webhook URLs: a Test URL (only works during manual testing) and a Production URL (only works when the workflow is active). Confirm you are sending requests to the correct one.
- Test vs. Production URLs: The test URL path includes
/webhook-test/while the production URL uses/webhook/. Mixing these up is the single most common webhook issue. Double-check which one your external service is configured to call.
Credentials keep failing
- Re-authorize OAuth connections: OAuth tokens expire. Go to Settings > Credentials, find the credential, and click "Reconnect" to go through the OAuth flow again. This is especially common with Google and Microsoft services that rotate tokens frequently.
- Check API key expiration: Some services issue API keys with expiration dates. Log into the third-party service directly and verify your key is still valid. Generate a new one if needed, then update it in your n8n credential.
- Verify scopes and permissions: If a credential connects but specific operations fail, the API key or OAuth app may not have the required scopes. Check the n8n docs for the specific node to see which scopes are required, then update your API app configuration.
Where to report a security vulnerability
- Email
security@n8n.iodirectly. Do not post security vulnerabilities publicly on the forum, Discord, or GitHub. Responsible disclosure protects the entire community. - Include reproduction steps: Describe the vulnerability, the n8n version affected, and clear steps to reproduce. Include the potential impact. The security team will acknowledge receipt and work with you on a fix timeline.
The Short Version
Search the docs and forum before posting. Use the forum for workflow questions, Discord for quick real-time checks, email for billing and account issues, and GitHub only for confirmed core bugs. Every support request should include your environment, version, error output, and workflow JSON. Security vulnerabilities go to security@n8n.io, never to public channels.
For more n8n guides, see What is n8n?, How to Set Up n8n, Cloud vs. Self-Hosted, and the complete Academy guide.
