n8n Reviews

One standout project I built with n8n was for a distribution client using Odoo ERP. They had a fully manual order fulfillment process where orders from their Shopify and WooCommerce stores landed in Odoo, but the warehouse staff had to print pick lists, pack slips, and perform extensive manual work to create shipping labels in ShipStation and then re-enter all those details into Odoo. This process was very time-consuming and error-prone. I built an n8n workflow that acts as the central system, triggering every 10 minutes on new confirmed sales orders in Odoo using the Odoo node. The workflow validates inventory levels, applies custom business logic for bundling and formats, creates the shipment request, receives the tracking number and label URL, and sends a personalized SMS to the customer via Twilio.

I have also implemented a wide range of workflows across different business functions using n8n. For example, in retail, I automated the synchronization of online orders from Shopify to Odoo ERP, which automatically creates sales orders, checks inventory levels, sends confirmation emails to customers, and triggers notifications. I built complex multi-step workflows integrating CRM, marketing, and customer support systems. For instance, when a lead is marked as high priority in Salesforce, n8n triggers a workflow that notifies the account manager on Slack, adds the lead to a marketing nurture campaign, and schedules a follow-up call in Google Calendar.

My client absolutely wanted to get hands-on participation in the project, but had no technical background. Instead of coding the task itself, I walked him through some of n8n's features and gave him workshops and tutorials. Now he is able to configure some of the flows himself without relying on an external consultant.

n8n has positively impacted my organization, particularly in terms of saved time, reduced errors, and increased productivity. My recommendation is to start with n8n if you have any need for automation or integration, especially if you value control, cost predictability, and technical transparency. For technical users, developers, and IT professionals, n8n is more transformative. Unlike some black-box automation platforms, n8n empowers you and does not hide complexity; it visualizes it. You own the workflows and your data, and the cost structure is a major advantage. For a self-hosted scenario, n8n is free forever, which is phenomenal for small businesses or for prototyping. Even the very reasonable price in n8n Cloud plans is transparent, and in my team, it has made an impact on junior people because it gives them more hands-on experience with implementations, allowing them to transition to custom coding later.

n8n's strongest feature is its transparent execution model. Every step of the workflow execution is very transparent, and you can see the exact input and output data of every single node. There is also a debugger function, which is very valuable when building complex integrations or troubleshooting APIs. Additionally, the expressive power of the JavaScript and SQL nodes is another superpower. It allows me to drop into code for complex transformation while using pre-built nodes for the heavy lifting of API connections.

I use the JavaScript and SQL nodes in my workflows, particularly when importing data into a database. Data that comes from very old legacy systems or from a massive master sheet in Excel requires mastering SQL because mapping the fields sometimes cannot be done manually. Using the SQL function allows me to automatically map the columns and save considerable time for the customer.

I also appreciate that n8n is open source. This means I can inspect the code, customize it if necessary, and even contribute back to the community. This level of transparency is critical when working with clients who have strict IT policies. Additionally, the community around n8n is very active. I can usually find pre-built nodes, example workflows, or guidance on complex integrations. This accelerates the development time and reduces the need for custom coding while still giving me the flexibility to build very sophisticated workflows.

Regarding improvements for n8n, I would highlight two areas. First, while there is a growing community, the ecosystem of pre-built nodes for niche or proprietary systems still lags behind some commercial competitors. I often have to build custom HTTP request nodes or create my own node packages, which is doable but adds to project timelines. Second, features for team collaboration and lifecycle management are still evolving. Moving workflows from development to staging to production can be a manual export-import process, and native Git integration and more robust user roles for larger client teams would be a game-changer.

Regarding needed improvements, I believe much of the existing documentation is not peer-reviewed. There is definitely a big community, but if the documentation or tutorials were approved or at least had a badge from n8n, customers would feel that this meets the standards of n8n editors themselves, which would give more confidence in the flows.

I have been using n8n since it became popular in 2023.

n8n is stable in my experience if you are an experienced implementer who knows how to fine-tune configurations for production and scalability. However, if you are a junior developer or preparing for a prototype, you might face challenges that could lead to failures in production.

My experience with n8n's scalability indicates that while you can scale up workflows or deployments, many of the prototypes and pre-built flows are not resilient enough for production when there is extensive manual error or manual processes. There is considerable fine-tuning that needs to be considered, and it often requires changing some features and flows. Therefore, it is crucial to have a technical team to support you with real experience in n8n and large-scale implementations.

Through n8n Cloud support, I have had a good experience. I received dedicated support via email with generally good and faster response times than the free tier. I describe the support team as knowledgeable, helpful, and responsive. They often address questions relevant to my scope, and at times they also recommend searching for technical documentation or specific forums. Ultimately, they always point me to the relevant solutions for any problem.

Previously, I used Zapier and Make.com. The reason I switched is that those tools are still not complex enough to manage multi-flow processes and are better suited for simple use cases with basic automations and triggers, particularly for small companies that want to automate one or two processes.

The pricing experience was a bit of a learning curve. Working in an on-premise environment with no cost is great. For cloud environments, I noticed that depending on the number of nodes used and the number of executions, the basic plan might not be enough, and this is something I learned through experience. These days, when I recommend n8n, I always go with the tier one pricing system, opting for the premium option.

I have not seen a return on investment from my side because the impact is primarily on the customer side, where non-technical people can go through a learning curve and take over some of these tools, allowing them to save costs because they can reduce the hiring process for external developers for this type of automation that they can do themselves.

I have not seen a return on investment from my side because the impact is primarily on the customer side, where non-technical people can go through a learning curve and take over some of these tools, allowing them to save costs because they can reduce the hiring process for external developers for this type of automation that they can do themselves.

The pricing experience was a bit of a learning curve. Working in an on-premise environment with no cost is great. For cloud environments, I noticed that depending on the number of nodes used and the number of executions, the basic plan might not be enough, and this is something I learned through experience. These days, when I recommend n8n, I always go with the tier one pricing system, opting for the premium option.

Before choosing n8n, I evaluated Zapier, Make.com, and Workato. Among the three, I felt that n8n provides the most visual experience, the most powerful tool for execution and for production, and a very reasonable pricing system.

For those looking into using n8n, I advise that collaboration is key. I typically use Git or version control repositories to maintain workflow definitions for larger projects. I also document each workflow extensively within n8n using node descriptions and comments, so anyone on the team can understand the logic. For cross-functional teams, I use screen share and workflow walkthroughs along with peer reviews, which I recommend to other users and junior implementers starting with n8n.

I advise testing first in staging. I suggest starting simple and then scaling. Begin with a simple workflow connecting Slack with Google Sheets before adding complexity. It is important to master the fundamentals, such as data structure and JSON data between the nodes, and then gradually work on optimization, rate limits, monitoring execution, and deploying additional nodes along the way.

I rate n8n an eight on a scale of one to ten because it is a very powerful tool. However, I feel that for very complex production environments, it still requires considerable fine-tuning and knowledge, and sometimes it might not be fully ready to support large-scale implementations in production. For prototyping and small use cases, as well as medium and small enterprises, n8n can be a great option. For larger implementations, it might still lag behind.

I use n8n to automate business processes. For example, if a customer calls and wants to buy goods, I can automate that process by integrating n8n to the voice service so that n8n takes the information from the voice service and then inputs it to the client's CRM. The client gets all the information needed based on what the customer asked.

I have used n8n with Vapi, a voice solution. I have used it with Airtable and Google Sheets. I have used it with many platforms including Vultr and 11 Labs. I have integrated n8n with virtually anything as long as they have good documentation in their platform. The key is knowing your endpoints and how to connect using an HTTP request.

The primary benefit is automation, which saves costs and time for repetitive tasks. For example, I do not need to hire a data entry specialist to input data in my system. I can automate that process with n8n and save costs and time. I can use the time I would have spent on that to do other things. Customer service can also be automated through voice. I can set a time in n8n, do my configuration, and input the numbers I want to reach out to. Once it is that time, the workflow will automatically trigger and those clients will be called simultaneously. I do not need to call one person, wait for the call to finish, and then call another person. I can call all of them at once, saving me time.

n8n has really helped me improve my data management because I do not need to do much work. I have automated my businesses so that I just need to set my voice AI agents. When anybody calls my number, n8n will automatically register that call into my Google Sheets or Airtable. When I review the transcript, I know exactly what went on. If something requires me to call the customer back, I can also do that automatically using n8n. I can do it manually too, but sometimes I prefer to do it automatically just to save time and cost.

What I like about n8n is the ability to customize your workflow. I can do virtually anything with n8n with the HTTP request node. I can customize anything and do any automation with it. Unlike some other automation platforms, I am not limited in my own customization.

n8n's user interface is very good. Recently, they upgraded their service to include AI. I can just talk to the interface. For example, I can type what I want to achieve, and the AI will build the framework for me so that I just need to input my credentials and then start the automation. They have a very friendly user interface.

Data privacy is handled well in the sense that my information is saved with me. I am not worried about data privacy because everything is stored in my own virtual environment. My clients know that the information is not leaking or being sold to anybody.

What I would like for them to improve is to include more nodes and different service provider integrations, just the way Zapier does. They have so many integrations. I really want them to add many more integrations to their platform. I know they are trying, but they still need to add more to it. Even though I can connect to different platforms with the HTTP node, it would be easier for people who are not technically advanced to connect with the internal integrations. I would like them to have more connections.

I have been using n8n for close to two years.

I have not had any downtime with n8n. It has always been up and running unless I fail to pay my VPS provider and then they might shut me down. As long as I am subscribing, it is always up and running.

n8n is scalable. I find it to be scalable.

I have not actually asked any questions regarding customer service.

I think it is $20 to $25 per month. I cannot really get the exact figure, but it is not more than $25 per month. The minimum price is $25.

First of all, the cost is a major factor. The open source version is free. I only need to pay for my VPS. Secondly, regarding the number of runs, the open source version has unlimited runs, while the paid version has a limited number of runs unless I upgrade my plan to have different amounts of runs. That is the difference between open source and the paid n8n.

The difference between n8n and Zapier and Make is basically the integration. n8n has less integration than what Make and Zapier have. Many people, since there are not so many technical persons, tend to go for Zapier, more especially for their workflow because it is drag-and-drop functionality. Unlike n8n, where I might need to do something with a particular platform and that platform is not on n8n, I then have to do API calls and HTTP requests and set parameters, which is a little bit advanced for some persons. That is the main difference. The cost is also a factor. Zapier is expensive, but n8n is cheaper. Make.com is expensive too, but n8n is affordable. If I am a less technical person and have the money, I might go for Zapier. If I am a budget-conscious person, I can go for n8n. However, I have to be a little bit technical because n8n does not have more comprehensive integrations the way Zapier and Make have. That is the difference.

n8n is a really good automation platform where I can use it to automate my businesses and processes and also save money and time. The most important thing is to learn how to use the software. If I can use the software and know how to integrate different platforms to communicate with each other, then I will save a whole lot of money because n8n is cheaper and it does not get tired. It does not make mistakes. Mistakes can also cost money. Using this automation tool will help me reduce that situation. I really encourage people to use n8n if they can use it and if they are technical persons. If they are not technical persons, there are also different tools they can use to learn. YouTube is available for learning how to automate these things or how to use the software. My overall rating for n8n is 9 out of 10.

My main use case for n8n is in the area of HubSpot marketing CRM AI agent project. I built and implemented CRM marketing automation patterns such as contact creation, audience and list management, workflow enrollment, pause or resume controls, and campaign ROI reporting through HubSpot APIs. My perspective is practical and build-oriented, focusing on how automation tools such as n8n support AI agents workflows, CRM operations, integrations, and process automation.

I have also designed a Mollie agent that helps with onboarding and processing payments for e-commerce, mainly for the EU region. That represents another use case where I made use of n8n.

The orchestration and automation are the most valuable aspects. n8n supports AI agents workflow, CRM operation, integration, and process automation in a way that helped me understand the logic of how I orchestrated the workflow, including all the different layers that are integrated.

The different workflow operations include control workflow, enrolling contacts in workflow, getting workflow details, pausing workflow, and resuming workflow. These are different API points that I integrated to help in AI automation for AI agents, making them autonomous agents that can work as a companion with marketers in the marketing domain.

The orchestration layer that connects all APIs without ambiguity drew my attention to the way n8n actually connects all these different APIs. I used that same orchestration logic to understand how that logic can be applied to connecting how AI agents autonomous workflows would also work.

n8n is very useful because it has saved a lot of people a lot of code. It has brought us to a point of little or no-code development that has helped create a way that we are not fully dependent on those writing the code and trying to glue integrations together. As the founder and designer of an early-stage company, n8n has helped me by giving me the orchestration logic through which I was able to orchestrate how workflows move before considering how to govern this automation.

One of the best features is trigger-based workflow automation and integrations, which has reduced my development time significantly.

n8n could improve the onboarding and debugging experience for users who are not deeply technical. The platform is powerful, but when workflows fail, error messages and node-level troubleshooting can sometimes require technical understanding. Clearer guided debugging, better beginner templates, and simpler explanations of failed executions would make it easier for more users to adopt the platform.

At every point where there is a failure in the workflow, it should not just shut down or give an error. Instead, it should be able to tell someone what the error is and suggest ways to address it. The improvements needed are easier debugging, clearer error explanations, and smoother onboarding for non-technical users. I understand what I went through to understand how the whole platform works before actually integrating it. For people coming in who want to build with n8n, it should provide clear guidance and manuals rather than just saying something is available.

I have been using n8n for over a year now, working on various projects over the past twelve months. I have been using it fluently throughout this period.

My startup is at a growth stage and yet to reach scaling. At that point, I may have observations to share about scalability, but for now, I cannot speak from projection or personal experience with scaling challenges.

I have not had issues that required me to contact support for n8n to understand how their customer service works. However, if n8n customer service uses artificial intelligence, then its customer service would need to be recalibrated with what is currently emerging. It is very clear from what I have been doing and what is unfolding that calibration after outcomes helps the institution learn, while calibration before commit helps the institution stay protected. If n8n makes use of models in integrating and trying to help in their customer service, they might be using some data to that particular vendor. I do not know how their customer service works, but I suspect they have scripted artificial intelligence in their customer service. From the standpoint of platforms such as n8n, they should be part of the solution regarding ethical integration of AI into the autonomous era that is upon us.

I am not really focused on reliability and output because I am much more focused on the commit boundary. What is aligned at the commit boundary is what actually passes down to the downstream as checking outputs. When the upstream is being recalibrated and what I created was being recalibrated, I was not so focused on checking output scores or how the output is right. I am more into what is aligned with action and consequence for the greater good of who the consequence falls back to, which is the human being.

Every AI capability out there is missing something. It is missing commit. Every AI action is in the policy documents, but governance only treats actions after they have already occurred. There is no governance at the commit that actually enforces action at the runtime. In essence, governance that is not at commit is advisory.

n8n has definitely saved me time. If we are considering finances, I should not speak about finances because I have not yet had what I built go into the ecosystem to generate funds. However, the agent that I created, which is an extension of what n8n already has in terms of solving problems and creating value in the ecosystem, is definitely going to help me create revenue. The automation agent I created extends n8n in terms of guardrails and governance in the autonomous field at the commit boundary, and this is definitely saving time for me and adding value.

I have been in the field and n8n stands out, so I made use of n8n. I did not really have a reason to check something that is not in its class.

n8n is very useful because it has saved a lot of people a lot of code. It has brought us to a point of little or no-code development that has helped create a way that we are not fully dependent on those writing the code and trying to glue integrations together. As the founder and designer of an early-stage company, n8n has helped me by giving me the orchestration logic through which I was able to orchestrate how workflows move before considering how to govern this automation.

n8n did not give me a reason to go and start reinventing what was already there. It gave me the ground that I could use with the same logic that already exists, creating a particular way in which it moves in sequence and in good order. That brought about the aspect I was trying to build, which made me have to not use n8n straight because n8n did not allow me to put in or enforce governance at the point of execution with these AI agents as we are already integrating them to do work that has consequences on humans. Because of that constraint, I used the way n8n itself flows and works to create an autonomous system that I designed for the marketing domain, making sure that the guardrails are executing at the commit boundary. At the point of execution, we ensure it is not something that we need to check after the consequence has happened because n8n did not allow for that, but it did support a bigger part of the process. I had to repurpose what was already there and add the layer that was not actually there.

As an early founder yet to receive seed funding, I understood how n8n works. I am more technical, and I am not focused on deploying n8n as an enterprise stack. Rather, I was looking at a way that what n8n has can be extended in terms of AI agent workflows. The agent that I created, which is an extension of what n8n already has, addresses the gap by adding guardrails and governance in the autonomous field at the commit boundary. This is definitely going to help me create revenue and is definitely saving time for me. My overall rating for this product is 7 out of 10.

My main use cases for n8n involve workflows I built. The first is a genfin mapping workflow, which takes trial balance data and uses GPT-4 with structured output parsing to automatically classify accounts into the correct financial statement line items. A second workflow is the basis of preparation workflow, which ingests PDFs, extracts financial context, and then generates a complete basis of preparation document using an LLM. That one involves webhook triggers and custom JavaScript nodes for output fixing.

The best features n8n offers that stand out to me are three things. First, the visual workflow builder allows me to see the entire data flow and orchestration logic graphically, making it much easier to debug and iterate, especially when working with complex multi-step processes. Second, the JavaScript code node provides full flexibility for custom data transformations, which most low-code platforms simply do not offer. I can write logic to fix JSON parsing issues, merge outputs, and handle edge cases without breaking out to a separate service. Third, the LLM integration nodes allow me to drop in GPT-4 API calls directly into the workflow and chain them with other operations, which is genuinely powerful.

One thing worth mentioning about my main use cases and the workflows I built with n8n is the real impact it had on our client side. We are automating tasks that chartered accountants did manually, such as trial balance mapping and financial statement preparation. We see roughly a 70% reduction in manual processing time on the document pipeline side, which means our clients can focus on higher-value audit and compliance work rather than data entry. That is where n8n really shines for us. It is not just about automating something technical; it is about delivering tangible business value to financial services.

n8n can be improved, and beyond LLM output validation, there are a few other pain points I notice. First, the debug experience could be stronger. When a workflow fails partway through a complex multi-step process, it is sometimes hard to pinpoint exactly where and why, requiring manual stepping through each node.

A couple of things come to mind regarding needed improvements. Documentation around advanced use cases, especially combining JavaScript nodes with LLM integrations, could be more comprehensive. There are patterns we figured out through trial and error that are not well-documented, which slows down new team members. On integrations, the PDF handling could be smoother. We use third-party nodes for PDF integration and had to write custom JavaScript to accurately extract structured data from PDFs. A native, more robust PDF processing node would have saved significant development time for anyone building document automation workflows.

I have been using n8n for approximately one and a half years at Radian Services, where I work as a full-stack developer in an AI-focused role.

n8n is quite stable in my experience. It has been reliable in production.

n8n's scalability has been decent as we scale up workflows over time with increasing client volume. We can handle hundreds of documents per day through the trial balance and disclosure note workflows without major issues. The limitations we start to see are with very large batch processing. When we try to process thousands of documents in parallel or handle deeply nested loops with complex LLM calls, the system gets sluggish.

Customer support has been more reliant on documentation, community, and direct support. n8n has a fairly active Discord community where I can ask questions and get responses quite quickly from both the team and other users who have built similar workflows.

Before n8n, we were building custom Python and FastAPI microservices to handle document processing workflows. It worked, but it required full backend development cycles. We would write code, containerize it, deploy it, and maintain it; every workflow change meant touching the codebase. With n8n, we can iterate much faster. Business logic changes that would have taken days of deployment and testing can now be done in hours through the visual workflow builder. We do not completely abandon custom code; we still use Python for heavy lifting such as OCR and LLM fine-tuning, but n8n becomes our orchestration and integration layer instead of building everything from scratch.

Since we self-hosted, we avoided n8n's SaaS pricing entirely. Our costs are primarily on the Hostinger VPS subscription, which is quite reasonable at around fifteen to twenty dollars per month, plus the time investment in setting up Docker, configuring persistent storage, and managing the infrastructure ourselves. The licensing side is straightforward because the self-hosted version is open source. We do not have per-user seat costs or tiered pricing to negotiate. That makes it very cost-effective.

I have seen a return on investment, and the clearest metric was the 70% reduction in manual processing time I mentioned, which translates directly to our clients handling roughly three times the document volume with the same team size. For a chartered accountant firm, processing financial documents at that scale is substantial.

Since we self-hosted, we avoided n8n's SaaS pricing entirely. Our costs are primarily on the Hostinger VPS subscription, which is quite reasonable at around fifteen to twenty dollars per month, plus the time investment in setting up Docker, configuring persistent storage, and managing the infrastructure ourselves. The licensing side is straightforward because the self-hosted version is open source. We do not have per-user seat costs or tiered pricing to negotiate. That makes it very cost-effective.

Before choosing n8n, we evaluated a few alternatives. We looked at Make, formerly Zapier, because it is popular and has good LLM integrations, but it felt more suited to simple automation rather than complex workflows with custom logic. We briefly looked at Airflow for orchestration, but that is really designed for data pipeline scheduling rather than real-time workflow automation with webhook triggers and immediate responses. There were other low-code platforms as well, but most of them did not provide the JavaScript flexibility to write custom fixes for LLM output issues.

If you are looking into using n8n, I would recommend this: if you have developers in your team who are comfortable with JavaScript and APIs, n8n is genuinely worth evaluating. It is particularly strong for AI automation workflows where you need to orchestrate LLMs with custom logic. Start with a proof of concept on a specific use case rather than trying to replace your entire automation infrastructure at once, and budget time to learn the JavaScript code node properly, as that is where most of the power comes from. Finally, be realistic about self-hosting, as it gives you cost savings and control. I would rate this product an 8 out of 10.

I generally use n8n for my email responses, for lead generation, for image generation, responses to all my WhatsApp messages, creating bookings, and handling all my tasks for meetings.

For lead generation, I gave all the contacts to n8n and made it write the email and automated the email sending workflow for lead generation, and the conversion rate was around 70%. If I message 100 users, I get 70 users converted and experienced a growth in business by around 50%.

Regarding the memory feature: whenever I get a booking through my WhatsApp, the memory feature stores everything inside it and later helps other clients to check my schedule and book a call with me for a specific time when I am actually free.

n8n helped us remove quite a bit of human interference, and the workflow which n8n has, along with the ability to create those workflows it provides, has given a significant boost in the business and a reduction of production time.

There is a reduction in time and improvement in the human resource. The teams are more pro-inclined towards work now that they have this n8n tool; they are self-learning n8n for their daily use cases and are applying the same concept in their work as well. Every employee is trying to create an n8n workflow which can replace themselves so they can sit and relax and just have a handsome amount in their pocket every month.

Time saved and fewer employees needed represent the main benefits; money saved is not relevant for now.

n8n is just an empty canvas where you can drag and drop anything and do unimaginable things with n8n; there are so many possibilities. There are more than 500 different applications for integration, the AI agent, the memory feature which n8n provides, the complete look and feel of n8n, and the user experience, which is very easy to use with just a drag-and-drop method. It feels a new Canva for AI agents.

n8n can make the platform even less complex for people who are not from a technical background. I am from a technical plus business background, and people who are actually not from a technical background should have something which they can easily access and create. I would suggest that n8n can provide a prompting agent or prompting bot, by which businessmen or managers can create their own workflows or agents, and if that could happen, it would be one best thing. Another best thing n8n can do is address the webhook URL aspect; basically, once you create a workflow or an AI agent, there is a webhook URL you should use to send the data. I think something else can also be used apart from the webhook, and it would be great if n8n comes with something very useful for all the non-technical crowd.

I have been using n8n for six to seven months.

I don't think it is highly scalable, but it is scalable at a moderate level for companies which have 200 to 500 clients daily; the daily throughput is of 200 to 500 clients.

I have never really tried customer support.

Negative

I did not use anything previously.

Pricing is a bit high, and the setup experience had no cost; it was entirely free and there was no licensing required for this. I used AWS to set up n8n and run it locally on the AWS instance.

When I was exploring n8n and discovered I could self-host it on my own server, I bought an instance on AWS and self-hosted n8n, which was a very interesting part. Currently, I am using n8n on my self-hosted server.

I would say there is a positive ROI.

Pricing is a bit high, and the setup experience had no cost; it was entirely free and there was no licensing required for this.

I still don't know any other option apart from n8n, and I did not evaluate other options either.

There are a couple of things which I haven't explored, such as the Jira plugin, which I am yet to explore. There is a Notion plugin, so basically, all the product designing and product development tools in the market are plugins I have never used with n8n, and I am very keen to use them. I will soon use these and share another review. I would rate n8n a 7 out of 10. There is no specific reason for giving it a lower score, but certainly, there is also no reason to give it a higher score. It perfectly fits for a 7. I would surely recommend using n8n for daily work.

I perform pre-sales automations and post-sales automations, which involves CRM management. This includes finding leads on the internet, reaching out to the leads, building interest, and scheduling meetings with the sales team. Another use case for me is scraping information off the internet periodically, which could include competitor information or business intelligence information that is then scraped and put into a Google Sheet. A third use case I'm currently working on is blog generation for SEO. Companies that want to get their name better represented on the internet hire me to write automations for them that write blogs and use keywords. With these keywords, they are posted to the company's page directly or to their LinkedIn page, which helps build interest and helps them rank higher on Google.

The features of n8n that I have found the most valuable so far include the ability to deploy it myself and to build a workflow around what I need, and that it connects with a bunch of other services. It connects with Google Sheets, and it has APIs for CRMs such as Salesforce or DatoCMS, which is pretty helpful because it connects to everything. It's also really helpful that I can store context for AI, so once I can store context for the AI, it makes the generation much more accurate.

One positive impact that n8n has had on my customers' organizations is significantly less hassle over SEO or reaching out to clients and scheduling meetings. It helps them save a lot of time, and most of the time, it assures interest in the organization. If a pre-sales automation is done and someone has scheduled a meeting through n8n or the automation that I've built, the customer can be certain that the person who scheduled the meeting is interested in the product. This means a warm lead coming in instead of a cold outreach. I would say the main benefits are saving time, increasing efficiency, and reducing hassle.

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.

I have been working with n8n for the past two years.

I would rate the stability and reliability of n8n as very stable. I've never had a crash, and I've never had it use too many resources. n8n deployments are some of the cheapest that I've come across; the monthly cost for n8n deployment self-hosted rarely exceeds five dollars. For five dollars, I can run an entire business's back end basically.

The scalability of n8n solution is pretty good, and that's where my expertise comes in. It's about how scalable you can make it. Suppose the customer has ten thousand data points that they need to run through n8n. One approach might take a day to go through all of it and another approach might take fifteen minutes to go through all of it. It just depends on how you format the thing and how you go through it, or how you organize the workflow and how the workflow carries over.

I don't often communicate with the technical support of n8n; the community support is really good. I can reach out to members of the community, ask questions, and usually within a week, they're answered.

Negative

When my customers start working with me, most of them are Indian right now, and they do not know these automations exist. If they were previously aware, they would be using Zapier, the American company. Once I make them aware of n8n and how it works, they're very eager to try it, and once they see the results in action, they just stick with n8n.

In my experience with the deployment and installation of n8n, initially, when I was learning the software, I had some challenges on how to store information and how to make sure that the information is persistent and doesn't reset all the time. Once you read the documentation posted online, it's pretty straightforward, and hosting it myself on the cloud is also pretty straightforward.

I'm a consultant for n8n; I copy the source code and I deploy it personally.

Comparing Zapier with n8n, I see that Zapier is kind of expensive; it charges per run. When I say per run, it means every run over the workflow, it charges you, plus the API costs on top of that. The other microservices that Zapier has are kind of expensive. I would say Zapier is more user-friendly; it's very no-code, and anyone who's never deployed something themselves or built an automation can easily use Zapier to make something, but it will end up being a lot more expensive. For example, per run on Zapier, I think is ten cents, and if you have one hundred runs of a workflow, that is easily one dollar. Workflows usually run for more than fifteen thousand to sixteen thousand runs.

My customers are usually not aware of n8n; they have to be made aware. They're more aware of Zapier, n8n's competition, and for Zapier, they purchase it directly from the website. n8n has to be deployed on a cloud usually.

I think my customers usually buy n8n from third-party marketplaces. I have not heard of a customer buying n8n directly from n8n's website. The third-party website would be me, basically. I would make them aware of the product and then they would start using it through me. Once they're aware of how n8n works, they usually leave the handling to someone else because it's a complex tool to use and it's kind of hard to master. Once I deploy it for them and I make a solution for them, it runs automatically. They don't need me to change the process anymore. If they do require me to change the process, that's when they reach out to me again or perhaps another consultant.

The materials, guides, and documentation on n8n available on the internet are pretty extensive. They basically walk you through everything, and the different APIs that n8n connects to have their own set of documentation. The documentation on the internet is very extensive; there is no way that if you read through the documentation, you won't find the solution to what you're looking for. I would rate this review a ten out of ten.

I have been working in my current field for 1.5 years, and I have gained hands-on experience in automation, APIs, integration, and workflow optimization, especially using tools like n8n to streamline the process. During this time, I have developed practical experience with the tools and integrated various applications with n8n.

I have 2.5 years of experience with n8n, which includes 1.5 years of personal experience and an additional year of usage before that. During this time, I work on building automated workflows, integrating APIs, and optimizing processes to reduce manual efforts.

My main use case for n8n is designing automation and system integration. I primarily use it to connect different services via APIs, automate repetitive tasks, and build event-driven workflows. For example, I have used it to process incoming data through webhooks, transform it, and push it to other systems such as databases or messaging platforms. I have automated repetitive tasks, and API orchestration and integration are also tasks I use n8n for to connect multiple services, handle data transformation, and automate communication between the systems, especially where there is no direct integration available.

One workflow I built on n8n was for automating lead processing from a website form. When a user submits a form, a webhook in n8n gets triggered. The workflow then validates and transforms the data based on certain conditions such as lead quality and routes the data accordingly. For example, high-priority leads are automatically sent to Slack for immediate attention. All leads are stored in a database or Google Sheet, and I also added an email notification step so the system gets alerted instantly. This automation significantly reduces the manual work and ensures a faster response time to potential customers. Another automation I have built is invoice generation and invoice analysis. By using WhatsApp, chat, or a Telegram bot, we can provide the input or the required data through that, and the automation will process the data and generate the invoice, provide the PDF as output, and also store all the data in the database and send the mail to the admin for approval or cross-verification.

n8n has a very powerful impact on our organization, mainly by reducing manual work and improving process efficiency. For example, we have automated tasks including data syncing, notification, and API integration, which earlier required manual intervention. This not only saves time but also reduces human errors. In one case, automating our lead processing workflow helped us respond to customers much faster, improving our overall response time and conversion rates. Overall, it allows the team to focus more on high-value tasks instead of repetitive operations.

We saw a significant improvement in response time when implementing n8n. For example, earlier, our lead processing and notification flow took around one to two hours, depending on manual handling. After automation, it became almost instant, within a few seconds. That is roughly about a 90 to 95% improvement in response time, helping us engage with customers much faster. We reduced manual effort by around 60 to 70%, and error rates also dropped significantly. Some recurring tasks that took two to three hours daily are now fully automated.

One interesting edge case I handled with n8n was building a workflow with robust error handling and retry logic for unstable external APIs. In this setup, I used conditional checks and retry mechanisms with delays, so if an API failed or returned incomplete data, the workflow did not just fail. If it still failed after retries, the system could log the error and send a notification to Slack for manual intervention. I also designed the workflows to be idempotent, so even if it is tried multiple times, it would not create multiple records. This made the system much more reliable in production.

The best feature of n8n, in my opinion, is its flexibility, self-hosting capability, and the ability to build complex workflows with full control. It allows us to build complex workflows using conditional logic and loop data transformation. The open source and self-hosting is a significant advantage, and the visual workflow builder is very useful, easy, and powerful. We can drag and drop the node and visually design and debug the workflows. n8n provides strong API and developer support, allowing us to write custom JavaScript, call any REST API, create custom nodes, and also event-based process and scheduled automations through webhooks, cron jobs, and API-based triggers. Cost efficiency is another advantage, as there is no per-task pricing if self-hosted, making it ideal for high-volume automation. Additionally, the feature of version control and workflow history allows us to track changes in workflows. Therefore, the best features of n8n, in my opinion, are its flexibility and control.

One additional aspect I would highlight about n8n is how well it handles data transformation and debugging within workflows. The ability to inspect data at each step and modify it using built-in nodes or custom JavaScript makes it powerful for real-world scenarios. I particularly appreciate how workflows can be designed in a modular way, making them reusable and easier to maintain as the system grows.

Overall, n8n is a powerful tool, but there are a few areas where it could be improved. One key area is the user experience for beginners. While it is very flexible, the learning curve can be a bit steep for non-technical users. Improving onboarding and documentation for complex workflows is crucial. Another area is scalability and performance monitoring; while it works well, having more built-in tools for monitoring workflow performance, execution metrics, and debugging at scale would be very helpful. Lastly, expanding the number of native integrations and making some nodes more feature-rich could reduce the need for custom implementation.

One additional improvement I suggest is around workflow management at scale; as the number of workflows grows, it becomes harder to organize versions and maintain them efficiently. Having a better folder structure, tagging, or search capabilities would really help in a larger environment. I also think the debugging experience could be enhanced further, especially for complex workflows, with clearer error traces or suggestions for fixing common issues.

My advice would be to start with a clear use case rather than trying to automate everything at once. Begin with a small, well-defined workflow, such as a notification or data syncing, and then gradually expand as you get comfortable with the tools. Another important point is to design workflows with error handling and scalability in mind from the beginning, especially if you plan to use it in production. Overall, it is a very powerful tool, but you can get the most value when you approach it with structured and thoughtful implementation. I would rate this product an 8 out of 10.

I run an automation agency at orbiscr.com, and we use n8n for our projects. We create systems for others to use in their business automation rather than for our own use, and we use n8n to build these systems.

We primarily use n8n to create scrapers, website crawling tools, data collection systems from websites, and email automation, all integrated with different applications. I do not use it solo; I use it in combination with other technologies. We sometimes use it with a Python backend and partially with n8n. We call the backend through our architecture, for example, when we have a Python backend and a front-end with React, and then we have another backend with n8n, combining it with different usage patterns.

The best features of n8n are reading documents like Google Sheets and Google Drive, and especially the AI agent functionality, the Agent Mode and AI agent nodes, which I find very amazing, along with webhooks and HTTP nodes.

I am integrating n8n with Google products. For example, I created an application where the client has huge data, and we integrated n8n there with Google Sheets. The Google Sheets already contained Google Drive links and Google Drive folder links, which we then list and send to AI. We summarize it through AI and then send it back to Google Sheets.

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 have been working with n8n for almost one year.

I would rate the scalability of n8n an eight, which is acceptable.

I have never needed to communicate with n8n's technical support.

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.

Once n8n has passed all the tests, it works fine, which is why people use it on a VPS instead of a local server. Using the paid version is somewhat expensive.

The difference between the free version and paid version of n8n is that the paid version, if hosted locally, is almost the same. However, with the latest update from using the website, you get the AI assistant that can set up the flow for you automatically with prompts, which is a good feature. Cloudy also does the same, so people use Cloudy and they use a localhost of n8n. For example, I normally create a JSON file for the complete flow through my AI coder and then import it to the n8n canvas.

My customers mostly prefer deployment on the cloud. We are using AWS, Hostinger, and there are a few more cloud providers. I would rate this review a 9.5.

I worked on n8n, and Morgan messaged me on LinkedIn to review and provide feedback about the n8n product.

I have used n8n for almost six months and built a personal project with it. My main goal was to move to this new technology, but due to the lack of jobs in my circle, I stopped working on this product.

I appreciated how n8n can be integrated with other services such as WhatsApp, LinkedIn, and Twitter, and the automation tasks it performs. I built a system in which n8n was fetching commits from GitHub and passing those commits to an AI agent. The AI agent was building LinkedIn posts and Twitter posts along with visual graphics effects, and it was performing very well. I showed that product to many companies, but they said they were not interested, so I left working on it.

I appreciated how n8n can be integrated with other services such as WhatsApp, LinkedIn, and Twitter, and the automation tasks it performs. I built a system in which n8n was fetching commits from GitHub and passing those commits to an AI agent. The AI agent was building LinkedIn posts and Twitter posts along with visual graphics effects, and it was performing very well. I showed that product to many companies, but they said they were not interested, so I left working on it. I really value this product, n8n.

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.

It has been almost three to four months since I last used n8n.

I had no issues with the stability of n8n. I never worked on a complex project, so I cannot comment on that aspect.

Regarding scalability, n8n has versions, creating versions for every step, so scalability is not difficult. I first deployed it for LinkedIn, then moved to Twitter, and then to Facebook, and it was smooth.

I never contacted n8n's technical or customer support. I made a suggestion to them, but I do not recall what it was, and I did not receive a response from them.

As I am a full-stack developer, the initial deployment of n8n took me almost half a day, so it was not a difficult task for me. I had no issues with that and never faced problems.

I did not use any alternative to n8n. I never tried any similar solutions.

I do not know about the pricing of n8n because I simply downloaded it, deployed n8n on my WSL in Ubuntu on my machine, and then on the VPS. I never had an issue with the pricing, which was a positive aspect of n8n.

n8n does not require any maintenance on my end. I deployed it on the VPS, and it worked for me almost three to four months continuously. I never needed to check it on the server and simply visited the LinkedIn posts or the Twitter posts. I never needed to visit the server.

My overall review rating for n8n is eight out of ten.

My main use case for n8n is to create a workflow for affiliate marketing, where I need to send Telegram affiliate links manually. When I was looking for automations, I appreciated that n8n offered the features I needed. I am also using LinkedIn automation, and when we need to post on LinkedIn, we go to ChatGPT or any GPT, ask a few questions, and filter that content into a LinkedIn post for posting. We created another automation where I give the Telegram bot to the client, enabling them to automatically write anything they want. It automatically triggers the APIs, using good prompt engineering to post on LinkedIn, which saves a lot of time as we do not have to go to LinkedIn manually; it is direct from the bot.

I am creating workflows primarily to save time for my clients and myself. These workflows are very helpful for us.

The best features n8n offers include the webhook node, which I really appreciate, along with many other nodes. The agent feature is also good; I have used it for many things. n8n connects directly to our Google Sheets, which I find valuable, as well as the Telegram bot, which I appreciate a lot.

I find myself using the webhook node the most because I use it differently, such as in LinkedIn. I created a community node that daily pulls data for Telegram posting. I also created a bot in Telegram that retrieves specific videos. For example, I am using the Kaggle University webhook role that scrapes data every morning and sends it to Telegram. This workflow is essential for me. In digital marketing, I provide form submissions, and when someone submits through the site, it hooks that and automatically sends a message to WhatsApp, making it easy to convert customers. My clients are very happy with this, so I consistently use the webhook.

n8n has positively impacted my organization because we previously needed to write product descriptions manually for over 50,000 products on our website. It is not feasible to write all of them manually, so we created an automation. This automation helps us by automatically writing all meta descriptions and titles, which significantly supports our growth. It is very helpful and time-saving for us.

At present, I do not have any new features to add, but I believe a few improvements should be made, such as providing all nodes in one space, and sometimes workflows do not automatically save, so adding that automatic saving feature would be beneficial.

n8n has improved significantly, but it still has competitors such as Make. I feel that n8n is more coding-oriented, as it presents everything in a JSON format. Those with coding knowledge find it easy to understand, while those without it still have good support.

n8n needs to update some features and ensure that everything is user-friendly.

I chose a rating of eight because it is a recent product, and there are many features that still need improvement. They also need to collaborate with various other tools.

I have been using n8n for around five months, as I started this around six months ago.

I can estimate that I only work one time when I create the workflow, which typically takes two to three days. However, the overall impact lasts many days, effectively saving a considerable amount of time.

I came up with my approach by taking a piece of paper and writing down all my ideas. First, I took the YouTube course and completed the tutorials. Then, I self-hosted n8n in AWS, using Amazon Web Services and connected to the VPS. When we started working, I needed to write the workflow on paper, determining the necessary nodes and creating a rough diagram. I do this daily; if I get any errors, I take a screenshot and ask questions in Claude or ChatGPT, and I solve any problems with their help. I also use Claude MCPs, which makes it easy to create the workflow.

I purchased n8n through the AWS Marketplace and directly hosted it in AWS.

My advice for others looking into using n8n is to take advantage of the 14-day free trial. Open the free trial and simultaneously utilize their courses. If you can read, do so while executing to enhance your knowledge. They provide numerous YouTube tutorials as well, and n8n has beginner and advanced courses available. By watching and implementing the material, you can improve your automation and workflow skills effectively.

I find n8n to be a good tool for those who do not know coding but want to build significant automations. I believe it has a promising future as many users will benefit from it.

I rated this product an eight overall.