Running processes completely independently, achieving scalability and efficiency and all that without (much) programming thanks to low-code and no-code – that sounds like a lot of promises and flowery prospects.
Cloud automation can and does deliver on these promises: with intuitive interfaces, numerous resources and plenty of reach. So it's no surprise that the market for automation platforms, also called iPaaS, is growing. The competition is increasing and so we cannot avoid comparing the most important applications with each other.
For beginners in particular, many of the applications can seem very similar. However, we would like to highlight the differences and send Workato and Make into the arena. The comparison covers technical and content-related functionalities, pricing and user-friendliness. For an initial overview of both platforms, we also offer a blog post about Workato and a post about Make.
The first difference becomes clear when you create a test account. On the Workato landing page, you will initially only find the buttons "Login" or "Talk to sales". However, you can log in with your Microsoft 365, Google, Salesforce, Slack or Wrike account. This allows you to take a look at the automation platform at your leisure.
With Make, on the other hand, you will find the "Get started free" button directly on the website and can register immediately. Here, you can sign up with Google, Facebook, GitHub, or your email.
Workato has one more level of hierarchy than Make: You can create individual projects, which in turn create folders that contain your recipes. Make does not offer a project level but allows you to sort your processes into folders. Thus, Workato offers a little more clarity.
If you start a new scenario or recipe (we call both processes here for simplicity’s sake), you will of course first need to link it to your desired and used applications.
For a better comparison of the interface and technical possibilities, we have tried to build the exact same process in Workato and Make.
First, we select Airtable as the trigger, an intuitive database that is perfect for automations. Make offers the following trigger actions for Airtable:
Workato, on the other hand, offers these trigger actions for Airtable:
The Airtable account must then be linked via the API key and the correct table and the entry that serves as the trigger must be selected.
Already the complexity can increase with both platforms, as formulas can be used for better filtering. These are really powerful and can complete your automated processes down to the smallest detail:
How the process continues after the trigger can also be customized. Both platforms offer branches, "if, then" functions, error handlers or filters to better model the process.
However, there are small differences: Features such as aggregation are not provided in Workato, at least not by default. In our opinion, Make is closer to the real world with its logic and can therefore map significantly more complex integrations or process automation compared to Workato.
In our setup, we decide on a very simple process and link HubSpot as a CRM. Here, a new contact is created as soon as a new entry is created in Airtable. We are then notified of this in Microsoft Teams. The simple processes we created look quite different in the interface of both iPaaS platforms.
When it comes to pricing, the two platforms offer different structures. Workato offers two pricing options: "Workato for your business" and "Workato for your product".
“Required” forms the basis of Workato for your business. It includes workspaces with unlimited apps, connections, recipes, builders, and administrators. If needed, tasks can also be added on top.
The second option, "Workato for your product" is only relevant for users who want to connect their software with other applications via integrations. Workato does not reveal a price for either option. You can only request a quote. For this, it is necessary to arrange a demo.
Make, on the other hand, communicates its pricing strategy very transparently:
A free version is available with 1,000 operations per month. Operations in Make are defined as the individual steps within a process.
These are decisive for the required subscription. Ranging from $9 to $29 per month and even up to enterprise solutions, Make offers a package for every need. The platform also allows you to add on operations once you have exhausted your monthly limit.
A direct comparison is therefore only possible to a limited extent in this area. Prices are communicated more transparently at Make, which could be more attractive for individuals.
For enterprises, the aspect of compliance is of particular importance. Roles, rights and security must be guaranteed. Make’s Enterprise package offers numerous functions to increase security, for example:
Of course, Workato also offers measures designed to meet strict data protection, security and compliance requirements: Optional two-factor authentication using an authentication app such as Google Authenticator or Microsoft Authenticator, integration with SAML-compatible third-party Single Sign-On (SSO) systems, hosting in selected non-US regions, regular vulnerability and penetration tests or, of course, the assignment of rights and roles.
Admittedly, it is a little more difficult for us to evaluate the user-friendliness, at least with Make, since we use the platform on a daily basis and are therefore very familiar with it. Nevertheless, we would like to put ourselves in the shoes of newcomers.
In Workato the free trial is somewhat hidden. But that is also intentional, after all, purchasing decisions in large companies are rarely made in one day by one person. That is why we exclude this aspect in this comparison, but for those who are curious, it is much easier to create a free account in Make to try it out.
After logging in, you land on the dashboard for both iPaaS platforms. This is where Workato clearly scores, as its straightforward design provides an immediate overview of the relevant data.
In addition to the number of recipes, you can also see the number of successful runs (jobs) as well as failed jobs and the number of tasks used – all broken down per day. You can also filter by time, project and recipe. Another view, the Dependency Graph, shows how your different processes are connected. This feature is great if you don't want to lose track of hundreds of recipes.
With Make, on the other hand, the dashboard is very slim. In addition to your settings, you will find a graph that shows you how many operations you have used per day in the last 30 days and how much data was transmitted. That's it. The findings are rather meagre, in comparison.
We have already shown comparisons for this step above. Both iPaaS platforms, Workato and Make, guide you through the creation of new processes step by step. Basic automations can be created in no time at all.
It gets more complicated if you want to use the numerous functions, filters and conditions that both tools offer. The possibilities are really numerous. In our opinion, beginners need some time to get to grips with both Make and Workato. However, both providers support you with videos and training material.
A platform that wants to link different applications with each other naturally lives from the fact that these applications are also sufficiently supported. This is why the simple number of supported apps is important, as are extensible possibilities via the API interfaces.
In Workato, compatibility is currently geared more towards enterprise applications: Over 1,200 connectors are available. So-called on-premise connectors are also supplied as standard. Make, on the other hand, offers over 1,900 apps, but also only limited on-premise support by default. Integrating with on-premise systems may require third-party tools or custom API integrations.
However, both iPaaS platforms also offer a particularly important function: almost every application can be connected via HTTP calls or API calls. This means that not only can already defined endpoints (for example, "Send to email") be used, but other endpoints can also be connected (for example, "Get an email"). This enables further, numerous connectors.
In terms of integration possibilities, Workato and Make are thus pretty much on a par. Workato offers a slightly better linkage in the direction of on-premise and enterprise.
In the duel Workato vs. Make, the two iPaaS platforms are neck and neck. Admittedly, they cannot be compared 1:1, as they currently focus on different target groups. Workato scores in the enterprise sector, but Make covers a broader range of users.
Overall, we find Workato easier and more self-explanatory to use, especially for beginners. The dashboard also offers more clarity than Make currently does.
Your process automations gain complexity with the formulas. We find that both applications require practice and experience in order to exploit their full potential. Nevertheless, Make scores with slightly more features that can map even more comprehensive processes and are thus closer to reality.
However, Make currently still lacks enterprise connectors and apps. Here again, Workato scores with its on-premise connectors and enterprise applications.
Arrange a free consultation with us!
We provide you with independent advice and are happy to offer you our support.
Get Free consulting
