Some of the very simple use cases that people use Make for is AI-powered content creation. That is where we help them out with different kinds of content creation and social media posting, different business process automations such as HR recruitment processes. Several of these cases have been implemented using Make.

Make's front-end interface, the modular interface that it has, drag-and-drop interface, is very easy to understand, use, and integrate. It has definitely helped us and in terms of efficiency, it reduces the time that is required to complete any sort of automations.

Make's key features are very flexible when compared to Zapier. Because of that flexibility and the features it provides when using a particular module within Make, as well as using an HTTP module directly accessing any API, it is very flexible compared to Zapier.

Make's front-end or the low-code interface provides you with a very efficient way of creating these integrations and automations, which saves your time to market or creation time of these automations.

We utilize Make's drag-and-drop interface all the time. We use that low-code interface for creating automations.

We have utilized them and used them with different sorts of AI decision making. As advanced users of Make, we have handled many complex scenarios within Make.

Make needs to put some focus on or clarify the security aspect in its documentation or website. When creating automation through these modules between two different applications, there should be clarity about whether the data is secure while passing through these automations or integrations created within Make.

The pricing of Make at this point is through operations consumption, and it becomes really expensive in certain scenarios when iterations are involved. The operation consumption is too high and sometimes becomes a burden on the client. Make needs to review its pricing strategy since they have tough competition from n8n.

Make sometimes has issues with user logins and data saving when simultaneously working on two different PCs or when two developers are working on something or some blueprint. It can lose saved data from one interface to the other, and when logging on with the same user on another workstation, it occasionally misbehaves.

We were unaware that Make had its own local implementation module. They need to advertise this feature more effectively as we are developing many projects in Make and working with various clients.

We have been working on Make for the last two to two and a half years. Before Make, it was called Integromat. We have been working with it since before it was acquired and rebranded.

In terms of scalability, Make has no limitation or issues.

We have escalated a few issues that we faced during some integrations, and we received reasonable responses from Make support.

The initial setup for Make and getting a project ready and starting off with the project is very easy. Usability is not an issue.

n8n provides the same kind of flexibility and is much cheaper than Make. Once we install and get the local implementation ready for n8n, it becomes free for users.

Zapier is less flexible, and with the evolution coming through n8n and Make's new features, it is becoming a primitive tool. The main comparison in terms of features between Make and n8n shows that n8n, apart from pricing, is evolving into user interface based automations as other tools UIPath or Automation Anywhere.

In the last three months, many new customers are requesting n8n because of this pricing strategy.

Make is very flexible, easy to use, and has a whole universe of modules readily available within its offering and portfolio. People should feel comfortable using it even if they are citizen developers or not hardcore developers. They should be able to use Make by watching one or two tutorials and by dragging and dropping things and connecting the different modules and adding conditions. I highly recommend Make with a rating of 8 out of 10.

We use Make to manipulate data, cut the numbers, take this line of code, and translate it to another line of code. SaaS products use XML, and other products use JSON. You need to translate to communicate between them. You have to make a transit code between them to communicate and take the backup between them.

Make has a single IP. We cannot use a single IP because of the security. There are a lot of crashes when you work manually. Also, they need to provide more models.

When you have an error, Make should inform them with guidance before you make the mistake. There is a lot of data you can confuse.

I have been using Make for four years.

I rate the solution’s stability an eight out of ten.

The solution's scalability is great.

The solution is for enterprises but is more suitable for medium- and small-size businesses.

There is no issue with the technical support. I did use the support and community for help.

Zapier is the only competition. Zapier is easy, but it becomes a more robust product when you understand Make. It becomes easier to use with visual and lightness in the building. This helps a lot to know where you are and where you will build inside instead of Zapier.

The initial setup is simple and better than Zapier.

Make is cheaper than Zapier.

Overall, I rate the solution an eight out of ten.