A Guide To the forum

Questions
1

I’ve noticed a lot of similar questions, and a larger influx of new people, so as one of this forums top supporters, I wanted to give this as a guide to any newcomers who have questions, which is also why it is in this tab!

  1. A common misconception is that the supporters here are n8n staff, and while we’re happy to assist you, any questions regarding billing, n8n instance support, such as it being down for several hours or days, should go to help@n8n.io, (you must be on a cloud plan to email this). For any technical stuff, such as workflow issues, errors, or anything else, we’re happy to assist you!

  2. For any Licensing questions, we’re happy to explain it to you, and I’ve seen this question many times, so here is the licensing doc! here - here - here

  3. You may see many n8n tabs such as the questions tab, the academy tab, the announcements tab, and more! Each tab has their own explanation usually about the category! (Be sure to check out Announcements! Forum rules and n8n announcements pop up there time to time!) The built with n8n tab has a lot of cool stuff, and the tutorials tab is great for learning n8n!

  4. For any academy issues, this tab sometimes is hidden from the sidebar, here is the link!

  5. A lot of questions are usually already answered on the forum! If you go to the search, you can often find some of these issues already solved!

  6. Never be afraid to open a post! We are very happy to assist you, and we enjoy doing it!

  7. On the forum, we have a earning program, where for helping people, you can get rewarded, if you have any questions about that, please check - here

  8. None of what this says are official forum rules! This is just a community guide to help new people!

  9. @Anshul_Namdev Is our community moderator! He is very friendly, and is always willing to help!

I am also pinging @Anshul_Namdev and @kjooleng on this, incase I missed anything, but I hope this guide helps new forum members find their way around!

2

One addition that would cut the back and forth on half the technical posts: ask for the workflow JSON, not a screenshot. Select the failing nodes on the canvas, Ctrl+C, paste inside a code block. Credentials are stripped, only the credential name stays.

Two more for that list.

Version and setup, from Help > About in the editor. Self-hosted or cloud, queue mode or main, and the exact version change the answer more often than the workflow does.

The real error text. The red box on the canvas is a summary. Open the failing node, switch the output panel from Table to JSON, and read the Details section of the error. The status code and the provider’s own message live there, and that is usually the whole answer.

Posts with those three get solved on the first reply. Posts with a cropped screenshot take four.