n8n Community Forum

What is it?

The forum runs on Discourse and is staffed by both community members and n8n employees. It is organised into Questions (workflow help and errors), Feature Requests (vote on what ships next), Built with n8n (showcases with real workflow JSON), Announcements (releases and breaking changes), and Jobs / Hire. Everything is public and indexed by Google, which means a well-written question helps thousands of people after you — and a badly written one gets ignored.

Which category should you post in?

Posting in the wrong category is the fastest way to get no answer. Each category has a different audience and a different expectation of what a good post looks like.

• Questions — anything that is broken, confusing, or 'how do I…'. 90% of posts belong here.
• Feature Requests — only for capability that does not exist yet. Search first; duplicates dilute votes.
• Built with n8n — showcase a finished workflow. Include a screenshot of the canvas and the JSON.
• Announcements — read-only for most users; subscribe rather than post.
• Jobs — paid work only, with budget and scope stated up front.

How to write a question that gets answered fast

Answerers are volunteers scanning dozens of threads. The posts that get solved are the ones that let a reader reproduce the problem in under a minute. Treat your post like a bug report, not a plea for help.

A strong structure: one-line goal, environment details, what you tried, the exact error, and the minimal workflow JSON. Anything more is noise; anything less means a round trip of clarifying questions that costs you a day.

• Title: '<Node name> — <what fails>' beats 'Please help urgent!!'.
• State the n8n version and whether you are on Cloud, Docker, npm or Kubernetes.
• Paste the error text as text, not a screenshot, so it is searchable.
• Attach a minimal 2–4 node reproduction, not your 40-node production flow.
• Say what you already read in the docs — it prevents advice you have already tried.

Searching the archive like a professional

The forum's search supports Discourse operators, and using them turns a vague hunt into a precise lookup. Search the error string in quotes first, then loosen the query if you get nothing.

• "ERR_NON_2XX_RESPONSE" — quoted exact-phrase search on the error.
• category:questions google sheets append — restrict to a category.
• status:solved webhook 404 — only threads with an accepted solution.
• after:2025-01-01 ai agent memory — avoid advice for old versions.
• in:first order:latest — find recent original posts, not replies.

Redaction: what to remove before you paste

Everything on the forum is public and indexed. Workflow JSON exported from n8n does not contain credential values, but it does contain URLs, IDs, header names, query strings and sometimes sample data pulled from a previous run — which is where leaks actually happen.

• API keys, bearer tokens, basic-auth strings and signed URLs.
• Production webhook URLs — anyone can then trigger your workflow.
• Customer names, emails, phone numbers and order data in pinned sample output.
• Internal hostnames, private IPs and database connection strings.

Where to ask what

How to use it — step by step

1. 1Create a free account with email or GitHub and add a short bio — profiles with context get better answers.
2. 2Search your exact error message in quotes, filtered to status:solved, before writing anything.
3. 3If nothing matches, open a new topic in Questions with a specific title.
4. 4Include: goal, n8n version, hosting type (Cloud / Docker / npm / K8s), the exact error, screenshots of the node panel and Output tab, and a redacted minimal workflow JSON.
5. 5Reply to clarifying questions quickly — threads go cold after about 24 hours of silence.
6. 6Mark the reply that fixed it as the solution, and add a short note about what actually worked.
7. 7Subscribe to Announcements and watch the tags for the integrations you depend on.

Quick checklist

• Searched the exact error in quotes
• n8n version and hosting type stated
• Minimal reproduction workflow attached
• All credentials, tokens and URLs redacted
• Screenshots of node parameters and Output tab
• Docs pages already tried are linked
• Descriptive title, not 'urgent help'
• Solution marked once fixed

Pro tips

• Answer two questions for every one you ask — reputation converts directly into faster answers.
• Link the docs page you followed; it shows effort and avoids duplicate advice.
• Use code fences (```) around JSON so it stays readable and copyable.
• Follow the tag for each integration you rely on to catch breakage before it hits you.