Make could be improved by having more platforms and connections that we would like to use, as well as more flexibility in paying for operations, with tasks on a sliding scale instead of by tier.Furthermore, providing more thorough support documentation on connecting various platforms and troubleshooting errors would be very beneficial, especially for junior team members.
One thing is that the platform is really slow when loading. It takes about three minutes to get to the page of an automation and start changing things. That is really slow and frustrating. Another improvement would be if Make gave us the ability to use more developer-friendliness features for power users who want that. For example, putting variables inside of expressions would be really awesome. One reason is the slowness I mentioned, and the other thing is that there are platforms such as n8n which provide a better deal because Make is quite expensive. The pricing can be a little more reasonable. Recently they started charging for credits in a way that something will cost more. The pricing structure is transparent, but it is not very good for a growing organization. You should either charge a fixed monthly price or a price for executions, not for each operation. That is not very good to use. One of my main complaints is that they can be more reasonable with their pricing model.
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.
I don't think there's anything else Make needs, but one improvement could be the addition of no-code steps that can be used within Make, similar to what Zapier offers with its own actions.
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.
Make could improve the ease of use, it can be more complicated than other solutions. There are a lot of elements that are more technical than in other solutions.
Make is a robust automation platform that streamlines workflows, connecting apps to enhance productivity. Tailored for tech-savvy users, it offers dynamic automation solutions that optimize processes and facilitate seamless integration of disparate systems. At its core, Make empowers businesses to automate tasks through an intuitive builder with drag-and-drop capabilities. Ideal for professionals who need to integrate systems efficiently, it supports a wide range of applications, aiding in...
Make could be improved by having more platforms and connections that we would like to use, as well as more flexibility in paying for operations, with tasks on a sliding scale instead of by tier.Furthermore, providing more thorough support documentation on connecting various platforms and troubleshooting errors would be very beneficial, especially for junior team members.
One thing is that the platform is really slow when loading. It takes about three minutes to get to the page of an automation and start changing things. That is really slow and frustrating. Another improvement would be if Make gave us the ability to use more developer-friendliness features for power users who want that. For example, putting variables inside of expressions would be really awesome. One reason is the slowness I mentioned, and the other thing is that there are platforms such as n8n which provide a better deal because Make is quite expensive. The pricing can be a little more reasonable. Recently they started charging for credits in a way that something will cost more. The pricing structure is transparent, but it is not very good for a growing organization. You should either charge a fixed monthly price or a price for executions, not for each operation. That is not very good to use. One of my main complaints is that they can be more reasonable with their pricing model.
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.
I don't think there's anything else Make needs, but one improvement could be the addition of no-code steps that can be used within Make, similar to what Zapier offers with its own actions.
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.
Make could improve the ease of use, it can be more complicated than other solutions. There are a lot of elements that are more technical than in other solutions.