Systems Architect & Ai Product Strategist | Founder At Orb Deep Technologies at ORBDEEP
Real User
Top 5
Feb 26, 2026
n8n currently has Python in the beta version, and if it can be fully released, it would be more amazing because JS is working very well, but if Python is added as a standard feature, the results will be exceptional. Python is very reliable and a very diverse programming language that helps tremendously with complex tasks like machine learning. It has different libraries like Selenium, so web scraping and data collection from websites are very effective with Python compared to JavaScript. The setup of n8n is sometimes very complicated, especially with the HTTP node, which is complex to set up. The local credential and environmental credential configurations are somewhat complex and could be simplified.
Works at a manufacturing company with 51-200 employees
Real User
Top 20
Jan 9, 2026
I wrote a message to n8n regarding a problem I faced, but I cannot recall what it was. Currently, most products nowadays include walkthrough or guide videos, short videos of 20 to 30 seconds that inform about any particular button or action, which n8n product does not have. I believe it would be a positive addition to this product. Tutorials are lacking in n8n, particularly short tutorials for specific buttons, explaining what each button does or what each node does.
n8n is a really developer-focused program right now. It's very good for people who are comfortable with programming, hosting things on their own, and with automations. However, it could definitely be made a lot more user-friendly because when I started out with automations, I was also using Zapier. n8n has a bit of a learning curve to it; you have to learn a lot. Once you learn the software properly, it's very good. If they can make it more user-friendly, that would be great.
n8n can be improved in the way that the UI could be better. There is a version two of n8n that I saw demonstrations of. It is a little better, but I think the UI could use a more futuristic approach. I am biased because I am also a designer. When connecting nodes and referring to earlier nodes, the structure that has to be followed is sometimes confusing. To write an expression to refer to data from an earlier node, sometimes you have to use item.json, and sometimes you have to use json.first. Those kinds of things are sometimes confusing, but when you get into it, you will figure it out. I do not think there are any other things to be added for improvements. The performance is good. Documentation is really good. I do not think there is anything else to add.
I would appreciate having more AI integrated into n8n, specifically an AI agent to help me better understand how to build workflows and assist when I encounter errors. Additionally, it would be helpful to have the option to open the same workflow in multiple tabs, allowing me to see the data from one execution while simultaneously viewing another workflow. Clearer and more documentation would be beneficial. I've seen helpful videos on YouTube to understand how to use n8n with examples, but it would be great if n8n could provide its own guided instructions for different topics and use cases.
There are areas that could be improved or enhanced in n8n. From a features and functionality perspective, there are specific features that are missing in n8n at the moment that I would like to see included in the future.
They haven't fully helped tailor solutions for our needs. We need to make adjustments, enhancements, and create custom workflows. I'm not saying it is completely ready at this time, but it solved most of our purposes. You cannot ask for everything as these products are getting to a matured stage, so we have to give some time for them to reach maturity. Regarding integrations, if they can make it more seamless and beef up their workflow constructs, that would be great. Another improvement would be in making n8n more popular through a similar approach to Kafka's documentation. Kafka has created ten-minute capsules of every use case, covering basics, foundational concepts, and each construct in detail. If a newbie spends at least a week studying the documentation, they'll be equally proficient. Any experienced person, senior developer, or architect who goes through Kafka's documentation and videos will have a good jumpstart. If n8n applies a similar methodology, that would benefit the entire community and help them grow faster.
n8n is good in terms of usability, functionality, and many different aspects. I am not too sure what needs to be improved in n8n, but regarding the interface, it has a black background, and they could bring in some improvements for user experience. The localized implementation is a bit complex and we definitely need some developers involved within this process. If they make it seamless so anyone who is not technology-savvy can just drag and drop things and do this implementation, that would be very beneficial.
What could possibly be improved in n8n to make this solution better for the next release is still a navigating process for us. I don't think I'm in a position to provide the improvement areas yet because we are still learning and discovering them. Regarding the cost, scalability, and initial setup, I can think that for a bigger enterprise environment, the scalability, based on my observation, could be improved since we haven't fully explored that modular adaptive nature of n8n. There are limitations in scalability.
n8n offers a flexible, low-code automation platform connecting over 200 applications to streamline workflows and increase efficiency through visual configurations and real-time monitoring.n8n provides a robust environment for automating tasks with extensive integrations, benefitting users through its adaptability and developer-friendly design. It supports AI model integrations like ChatGPT to enhance automation. While users value its configurability and real-time logs, they suggest...
n8n currently has Python in the beta version, and if it can be fully released, it would be more amazing because JS is working very well, but if Python is added as a standard feature, the results will be exceptional. Python is very reliable and a very diverse programming language that helps tremendously with complex tasks like machine learning. It has different libraries like Selenium, so web scraping and data collection from websites are very effective with Python compared to JavaScript. The setup of n8n is sometimes very complicated, especially with the HTTP node, which is complex to set up. The local credential and environmental credential configurations are somewhat complex and could be simplified.
I wrote a message to n8n regarding a problem I faced, but I cannot recall what it was. Currently, most products nowadays include walkthrough or guide videos, short videos of 20 to 30 seconds that inform about any particular button or action, which n8n product does not have. I believe it would be a positive addition to this product. Tutorials are lacking in n8n, particularly short tutorials for specific buttons, explaining what each button does or what each node does.
n8n is a really developer-focused program right now. It's very good for people who are comfortable with programming, hosting things on their own, and with automations. However, it could definitely be made a lot more user-friendly because when I started out with automations, I was also using Zapier. n8n has a bit of a learning curve to it; you have to learn a lot. Once you learn the software properly, it's very good. If they can make it more user-friendly, that would be great.
n8n can be improved in the way that the UI could be better. There is a version two of n8n that I saw demonstrations of. It is a little better, but I think the UI could use a more futuristic approach. I am biased because I am also a designer. When connecting nodes and referring to earlier nodes, the structure that has to be followed is sometimes confusing. To write an expression to refer to data from an earlier node, sometimes you have to use item.json, and sometimes you have to use json.first. Those kinds of things are sometimes confusing, but when you get into it, you will figure it out. I do not think there are any other things to be added for improvements. The performance is good. Documentation is really good. I do not think there is anything else to add.
I would appreciate having more AI integrated into n8n, specifically an AI agent to help me better understand how to build workflows and assist when I encounter errors. Additionally, it would be helpful to have the option to open the same workflow in multiple tabs, allowing me to see the data from one execution while simultaneously viewing another workflow. Clearer and more documentation would be beneficial. I've seen helpful videos on YouTube to understand how to use n8n with examples, but it would be great if n8n could provide its own guided instructions for different topics and use cases.
There are areas that could be improved or enhanced in n8n. From a features and functionality perspective, there are specific features that are missing in n8n at the moment that I would like to see included in the future.
They haven't fully helped tailor solutions for our needs. We need to make adjustments, enhancements, and create custom workflows. I'm not saying it is completely ready at this time, but it solved most of our purposes. You cannot ask for everything as these products are getting to a matured stage, so we have to give some time for them to reach maturity. Regarding integrations, if they can make it more seamless and beef up their workflow constructs, that would be great. Another improvement would be in making n8n more popular through a similar approach to Kafka's documentation. Kafka has created ten-minute capsules of every use case, covering basics, foundational concepts, and each construct in detail. If a newbie spends at least a week studying the documentation, they'll be equally proficient. Any experienced person, senior developer, or architect who goes through Kafka's documentation and videos will have a good jumpstart. If n8n applies a similar methodology, that would benefit the entire community and help them grow faster.
n8n is good in terms of usability, functionality, and many different aspects. I am not too sure what needs to be improved in n8n, but regarding the interface, it has a black background, and they could bring in some improvements for user experience. The localized implementation is a bit complex and we definitely need some developers involved within this process. If they make it seamless so anyone who is not technology-savvy can just drag and drop things and do this implementation, that would be very beneficial.
What could possibly be improved in n8n to make this solution better for the next release is still a navigating process for us. I don't think I'm in a position to provide the improvement areas yet because we are still learning and discovering them. Regarding the cost, scalability, and initial setup, I can think that for a bigger enterprise environment, the scalability, based on my observation, could be improved since we haven't fully explored that modular adaptive nature of n8n. There are limitations in scalability.