Workato

Workato is definitely the easiest tool to work with. We found other tools more challenging when there are no pre-built connectors, and it requires coding knowledge to extract objects from JSON payload for example.
In Workato, the payload is auto parse and each object can be dragged and dropped in the workflow.

Workato is useful for the rapid development of simple workflow-oriented integrations. It was not designed for large, enterprise integrations like Boomi. Their target audiences and target use cases overlap in some areas, but there are very important differences. We selected Boomi for the large-scale, complex integrations where we have to process large datasets. Workato is used by the less technical users who need to develop simple integrations for themselves. Anything beyond the prebuilt recipes often requires more advanced technical support from developers as this product is not truly a no-code solution.

Our developers are certified in Workato, Mulesoft and Boomi.We tested Workato and compared it to Mulesoft and Boomi for an IPaaS solution. Workato claims that anyone off the street with no IT training whatsoever can build integrations with their tool. This is absurd. No, your secretary or janitor will not be able to create your enterprise integrations with Workato. Furthermore, there is a continuum between simplicity and lack of power and functionality on one extreme and complexity and flexibility and power on the other end of the continuum. Workato sees itself on the simple side of the continuum. We can see from the experience of other Workato adopters that they discovered belatedly that Workato often fails to have the built-in, native functionality required for more complex use cases, then they are left with trying to cobble together custom coded solutions. Note that last December 2021 that Workato significantly upgraded its SDK, and added new connectors for Process Mining tools, a Python connector to allow custom Python code.Workato runtime is in the cloud, but an on-prem agent can be installed for connectivity behind a firewall. Mulesoft is on the other end of the spectrum. It is a powerful tool, but requires the AnyPoint Studio client side software to be installed, along with Java JDK and preferably Maven. It has four deployment options: CloudHub, Runtime Fabric, On-Premise, and Hybrid (CloudHub and On-premise). The Mulesoft runtime, like Boomi's, can be installed on-prem or the cloud runtime can be used.Given this situation, you would want developers with solid Java experience to work with Mulesoft. That said, Mulesoft is very powerful and flexible compared to a limited solution like Workato. Boomi is between the previous two options in terms of the complexity vs simplicity continuum. It has a very user-friendly interface and has a relatively gentle learning curve. It is also very powerful in that it allows for custom coding to be built into the process flow in the inevitable event that you cannot find the built in functionality needed for a given task or use case. There is no need with Boomi development to install ANYTHING WHATSOEVER on the client system. All development occurs in the Boomi cloud platform. And from years of experience, I can tell you for sure that NOT ONE of the so-called 'No Code' or 'Low Code' solutions will EVER completely anticipate all of your requirements for built in functionality. I don't care what their marketing team says. In all but the absolute simplest of use cases, there will be some inherent complexity that is outside the realm of the easy drag and drop scenarios that the marketing team is touting in their sales pitch. For us, Boomi was the sweet spot in terms of ease of use and built in functionality. It has been a great tool, and we have the option of on premise Atoms or using Boomi Atom Clouds. You can even have a private Atom Cloud, as well. Clustered Atoms are called 'Molecules'. Clients we have had that moved from Boomi to Workato ended up moving back after realizing how limited the Workato platform really was.

Offers many, if not all, of the same capabilities that competitors have. Zapier is more user friendly, and cost effective for many organizations. Not needing to have technology experience is also attractive. Mule soft is usually overkill for some of the more straight forward integrations that Workato can handle. Workato is flexible and if the cost is justifiable, then it is a great solution

Both products were much more complicated to configure and get started with. With Workato, we had simple integrations set up and running without a couple of hours. With Jitterbit and SnapLogic it required some training just to evaluate it, and also required a lot of configuration steps. You just can't beat Workato for ease of use and rapid deployment.

We have experience using MS Flow, Zapier, Pervasive, Talend, .net, and others. After extensive research and testing, Workato has shown itself as a clear leader in the iPaas space.

Workato offers what we need at a much more affordable price...simply put

Workato proved to be the most user-friendly integration platform, showing the most promise in the area of no-code or low-code analyst-capable interface configuration.

Workato has a faster deployment cycle and no formal training needed to start using it. You may start creating recipes from day one.

Workato beats the competition pound for pound, not even close. It's a much more enterprise-grade tool, designed from the ground up to be stable, solid, and secure. The other tools I've tried were either buggy, lacking in capability, felt like toys, or were really hard to scale.

We ended up choosing Workato because of how easy it was to get started and because it did everything we needed it to do. It was one of the first products we trialed specifically for this use case even though we had used other products in the past. The trial was enough time to get us up and running and gave us something we could use in production. The learning curve was a short one and the UI was intuitive.

I use Workato for the full view of my process. Both the console on errors and debugging as well as the unified view of each task I'm automating. In addition, I know that Workato has all the power necessary for enterprise integration.

Zapier's integration tools are impressive, especially considering the cost. Their connectors are lacking functionality vs Workato, which ultimately leads to more development time and cost. Workato's built-in functionality, like lookup tables, are extremely impressive. They continue to add functionality in what feels like days. As a development shop, we really utilize the ability to use an HTTP connector and build out our own functions.

A market leader when it comes to an out of the box/do it yourself integration tool. It is very user-friendly with an excellent track record for new connectors and reliability.

We ended up using Workato for the functional user abilities as well as the flexibility in the platform. Our business is agile and an integration build today may not have a lifecycle longer than 6 months without modification. We wanted the ability to maintain these ourselves without technical expertise. It has been a game-changer for us.

Zapier was great for simple integrations, however, error handling and recipe writing isn't as strong. We also found the pricing to be deceiving once working on more complex integrations.

Helps to understand a more cloud-based tool integration.

CA Automic offers everything under the sun and it's a little harder to use for someone that doesn't know coding. With Workato there is a smaller learning curve and their support team has be instrumental in our success.

I've used and explored others. Workato was the quickest to learn and deploy at a reasonable cost. The others had large learning curves and were more expensive.

We found Workato to be easier to use, more powerful and more robust than other solutions we tested at the time. It simply does the trick and allowed us to implement all that we needed in all the precise details we needed. It gave us all the power, flexibility and autonomy we needed without bogging us down with unjustified complexity. Workato came through for us and that's why we keep using it after three intense years.

We use multiple integration platforms for various use cases. Workato did not replace anything. We believe in having the best tool for the job/persona and thus employ multiple tools with some overlapping functionality aside from the unique strengths/trade-offs of each.

From what I could see, Zapier was very limited against what Workato was offering. The model of Zapier, at first sight, was very easy to understand: you pick 2 connectors and create a process in the middle, but that's where Workato made the difference, on how easy the recipe building can be and how complex can it get as well (for example, by creating a step that executes Ruby code).

Workato is much simpler to learn and configure than Dell Boomi. While powerful, I struggled with Boomi's interface. I know Boomi is powerful and trusted by many enterprises, but it seems a little inaccessible to me - the learning curve is a little too steep and I don't have the time to invest.

Zapier, while very user friendly, doesn't offer the breadth of connectors and overall robustness that Workato does. Workato is enterprise-ready and a solution I feel comfortable recommending to more mature organizations.

In our initial meetings with Boomi, they told us we'd be able to automate all of our processes ourselves. After a few meetings, though, they told us we'd need to contract a team of engineers for 5-6 weeks to build the solution, and we'd need to use engineers whenever we want to modify it.

With Workato, we started automating our processes ourselves in the first meeting. Full implementation was really quick, and the Workato team guided us through it so we could do it ourselves going forward. Workato did everything Boomi said they could do but couldn't, and its costed us half as much. We did like the Boomi people, but to be honest I'm not sure why anybody would use it when they can use Workato.