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 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.

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.

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 am using n8n for generating agentic AI agents. I will explain this via one example. We have a requirement to create a chatbot for a university website. For that purpose, we have used n8n. Students will directly come to our chatbot and ask about courses, departments, and fees. Our agentic agent will respond to their inquiries.

We are also using n8n for HR purposes. We have stored all documents in GitHub and converted all documents into vectors, storing that information in Pinecone. We have used n8n to retrieve the information based on the user's query.

n8n supports connectivity to any application. We can easily connect any application with n8n, which is a feature I really appreciate.

In the previous examples with Pinecone and the chatbot application, we have utilized Gemini and OpenAI as an LLM. With the help of n8n, we have easily connected them. We have also connected Google Spreadsheet to get data from Google Sheets and save the data back to Google Sheets. We have done this very easily without coding.

n8n has helped us build agents very quickly. Without coding, we can accomplish this. Our business is growing faster because we have created workflows that help us improve our business.

We have improved time, cost, and productivity. All three have been improved.

n8n could benefit from a better UI. Currently, n8n provides workflows and we can easily create workflows and connect most applications. However, if n8n provided AI integration where we could just type via text and it would generate a workflow, that would be very useful.

Currently, when I configure n8n or create a workflow, I have to do everything manually. We do not have any AI with an LLM where I can just provide information in human language and it will convert or create the workflows. That is why I have deducted two points.

I have been using n8n for one year.

I have set up n8n on our local server, which is on a Contabo-based server, and sometimes it was losing connection. I have to restart it again and again. That type of issue I was experiencing.

We can scale up as per our need. I do not face any issues with scaling up.

I am not aware of customer support because nowadays many AI things are available in the market. I do not have to reach out to n8n customer support. I just ask a question to ChatGPT or Gemini, and it will answer my questions. I have not contacted them.

I have not used another solution. Currently, n8n was good. That is why we have started reviewing it.

If we use n8n, we will save time and money with fewer employees.

n8n is a very good product. It will save time and add more productivity. It will also reduce the work of humans if you utilize it in a better way. If anybody wants to use it, that is a very good product.

I am a customer as well as a developer. I would rate this product an 8 out of 10.

A main use case for n8n is connecting different platforms and using workflows to optimize day-to-day operations. One of the main examples is our sign-up flow. Whenever someone signs up, we create a record in our CRM, send them an email welcoming them, and send a notification into our internal communication channel announcing the new sign-up. All of these actions are done via n8n. We receive a webhook whenever someone signs up, and all of these nodes are connected, so the automation is built that way.

n8n is used extensively for many things. We use it to feed documents to our agents. We use it to go through our database records and filter out chats with issues. We use n8n in our reporting for the part where we send actual emails to clients. With n8n, the limit is just the sky.

n8n has impacted our organization positively. Whenever a new account is created, the CRM account is created and the notification is passed into our internal communication channels. Earlier, people would get notified of new clients joining only when they checked the CRM. Currently, even if they join in the middle of the night, we get a notification through n8n. Those kinds of things overall have saved a lot of time in our organization.

n8n is saving somewhere around two to four hours every week. I would estimate it to be around four to six hours per week, though I am an automation engineer doing automations and saving time for other people, so I am not the one to give the exact figure.

The best features n8n offers are the developer-friendliness, which makes n8n exceptional. You can use expressions anywhere. Expressions are basic JavaScript functions or JavaScript code that you can put in any node to pass data dynamically. I have not seen that kind of flexibility in make.com, Zapier, or any other platforms in the same domain. The flexibility for development and developer options are the best aspects of n8n.

Regarding the features, all of those are really good. Recently there is a great rise of people using n8n. People are posting about it every day with mind-blowing automations, including fully automated content pipelines and fully automated email reply agents. n8n is simply the best platform for these automation scenarios. The UI is also good. I would not say it is the sleekest, but I might prefer Zapier's UI a little more, but n8n gets the job done and gets the job done the best.

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 have been using n8n for more than a year. I started using it for personal projects when I was working in a different company. When I joined this company, my skills in n8n were what got me selected. I have been using it from the day I started at this company. It has been almost one year.

One of the main pieces of advice I would give to others looking into using n8n is regarding the self-hosted version. You will have to update it regularly. Otherwise, you will miss out on a lot of new features and security patches. It does not get updated automatically. You have to go and update yourself manually. I know that is a hassle, but it is really worth the time. Another thing is to always keep an eye on the newly added nodes. People are creating new nodes and uploading them to the community all the time, and people are creating new workflows as well. There are really creative workflows out there. If you keep an eye on the community, you will find a lot of hidden gems. My overall rating for n8n is a 9 out of 10.

I started using n8n about five months ago.

My main use cases for n8n are creating automations for the company and automating whatever can be automated in the company, whether it's with the product or with the business side.

An example of an automation I've set up with n8n is automating a catch-all inbox that receives hundreds of emails every day. I created a workflow that triggers when I get the email, reads it, and sends it through a workflow to be processed by an AI agent, specifically Gemini. Gemini decides if the email is important or unimportant, labeling it accordingly. The goal for this automation is to reduce the time users spend to see only important emails in their inboxes.

The best features n8n offers in my experience include integrations with many existing apps, such as Gmail, where you can already get messages, send messages, and label them, all included in the workspace without needing to use API requests. This is very useful because it has many apps with predefined functions.

Another feature I really appreciate is the visual aspect, meaning your workflow is visual, allowing you to understand data flow direction and see the data in different views, whether it's in a table or JSON.

The features I rely on the most day-to-day are the integrations with AI agents, such as Gemini LLM, which allows me to send questions in a useful format to get answers. This process is essential for me and is something I utilize every day.

n8n helps automate jobs that no one enjoys doing, which are very repetitive. It saves time and money because it handles those boring tasks that can now be automated.

For the example I mentioned earlier, it saves time significantly; instead of taking an hour a day, it only takes about five minutes, which is around ten percent of the original time. Although it takes some time to create the automation, it becomes very valuable in the long run.

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.

I have been working in my current field for the last six months.

From my experience, n8n is stable, though the part that can be less stable is that you must stay connected to many APIs. If something disconnects for any reason, n8n doesn't notify you about it, which is something I would appreciate seeing improved.

n8n is scalable for my needs as I can have more workflows running simultaneously. The standard solution allows for about five workflows at the same time, and it is scalable since I can upgrade my plan for more executions and workflows if needed.

My experience with pricing and setup costs has been good. I feel that the price is right as I'm using the standard version, which allows for about one thousand five hundred executions per month, which is sufficient for me and my organization. It seems scalable, so if more executions are needed, I can pay a bit more.

I believe the return on investment from using n8n is good because employees who previously worked on the specific problems I've automated can now focus on other, more interesting tasks without spending so much time on repetitive ones.

My experience with pricing and setup costs has been good. I feel that the price is right as I'm using the standard version, which allows for about one thousand five hundred executions per month, which is sufficient for me and my organization. It seems scalable, so if more executions are needed, I can pay a bit more.

Before choosing n8n, I considered using Zapier or Make, but I didn't try them. I noted that they are more expensive, and if you are a developer with good technical skills, n8n is generally better, based on reviews and YouTube videos I watched, which is why I chose n8n.

The pricing is fair.

I use the on-cloud solution that n8n recommends, and I pay the monthly standard fee for their services to deploy it.

My advice for others looking into using n8n is to just try it; you will see how it can benefit your organization. There are many options and workflows you can create and automate, so I highly recommend giving it a shot. I would rate this product an eight out of ten.

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.