Workato Reviews

When I was at HighRadius, I was leading the integration team, and we were using Workato to integrate customer data from their systems to our systems. We needed to integrate data from various data points and bring it into HighRadius systems for client projects. This was the main use case for Workato.

Workato reduces total development time as it generates code seamlessly and integrates with SQL databases or APIs through configuration. This automation facilitates efficient integration of customer data from their systems into our systems. It effectively handles real-time data integration with moderate volumes, and development time is significantly reduced by its automation capabilities, which are beneficial for both SQL databases and APIs.

The data flow and debugging processes need improvement, especially for tracing issues. Additionally, Workato struggles with scalability when handling high volumes of data, such as terabytes, requiring chunking for initial data loads. While it works well with moderate volumes, it requires enhancements to handle larger data volumes more efficiently.

I have been working with Workato for about one and a half years recently. However, I had used it previously when I was at Saeronlabs.

For daily runs, Workato is stable and there is no latency issue. However, during the initial data loads with large volumes, Workato was unable to handle the data effectively, which indicates stability issues under high loads.

There are scalability limitations with Workato. The solution could not handle high data volumes during initial loads for one of our clients, which required us to break the data into smaller chunks for processing.

The customer service and technical support from Workato were good. Whenever we faced issues with data volume, the support team helped us by suggesting solutions like breaking the data into chunks.

Positive

Overall, I would rate Workato an eight out of ten. 

While it has a lot of potential, there are areas like scalability and debugging that require improvement.

The main use cases include API-related scenarios, sales cycle processes, and invoicing operations. This primarily involves the purchase journey of the company, where Workato serves as an integration tool for transferring customer data, invoicing information, and orders between systems.

Their UI interface is very strong compared to other tools, allowing even non-coders to perform basic data transfers between systems effectively. When it comes to complex scenarios and customization, our team faces challenges in Workato. When we encounter issues and reach out to the Workato support team, they have limited ability to assist, leading us to implement temporary solutions and workarounds.

Maintenance requires minimal effort on our end as Workato handles most maintenance tasks themselves. We only need to retest major flows if there is a significant release. Regarding stability, it performs adequately without major issues. There are occasional refresh and cache issues, but it functions properly 90-95% of the time.

The customization capabilities could be enhanced significantly. Having used other integration tools such as Boomi and MuleSoft in the past, the features in Workato appear to be at a primitive stage. The support team has limited ability to assist when issues arise. Workato should improve their customization capabilities for complex scenarios that cannot be handled through drag and drop options. While they offer options for writing Ruby scripts, the functionality is not advanced enough. They should implement functions or internal mechanisms that allow users to write custom code for complex scenarios that cannot be accommodated by drag and drop features.

The deployment process in Workato is complex because new versions require copying rather than overriding, forcing users to perform numerous manual steps to maintain the latest code.

I have been using Workato for one year.

The stability is adequate with no major issues. There are occasional refresh and cache issues, but the system functions properly 90-95% of the time.

Scalability depends on the requirements we receive. It can be challenging due to the GUI development structure. Adding code between existing segments is difficult for developers. With effective design, it can be scalable, though not completely. The scalability rating would be approximately 60% to 70%.

We contacted Workato's technical support several times last year. With an advanced support model, the speed and response time were good. However, exact resolutions took time due to their need to understand issues and hand them over to other team members, along with time zone challenges. The support was good but not excellent.

The support rating is eight out of ten.

Positive

I have used other solutions such as Boomi for many years. Being an IPaaS tool, it accommodates all scenarios. I have also used MuleSoft.

Boomi is a better fit compared to Workato. Boomi offers drag and drop features similar to Workato but provides more extensive customization options. It enables advanced API management and has more adapters than Workato, which is newer in comparison. Boomi provides better management of multiple development teams working on the same code and has a superior deployment cycle.

We currently use both Workato and Boomi in different areas as needed.

Boomi is more expensive than Workato. Workato is recommended for small to medium-sized companies, while Boomi is more suitable for larger companies with extensive data needs. The choice depends on company budget and size. For simple integrations and limited budgets, Workato is recommended. For large-scale companies with substantial data and budget, Boomi or MuleSoft would be more appropriate.

We collaborated directly with the Workato team for purchase, not through any reseller or store. Deployment requires the entire team as every developer needs to know the latest code and coordinate with the person handling deployment. For large teams, the development team lead is essential.

I need to verify partnerships with Workato as we work with different clients in a service-based company, resulting in various setups where some have partnerships and others use subscriptions.

Overall rating for Workato: 7 out of 10.

I have used Workato for almost six months in my company to integrate different platforms using this Workato tool.

The main use case of using Workato is that Workato is an integration platform, whereby if I want to integrate one platform with another, such as integrating SAP with Freshworks, I have to use Workato as a tool to integrate these two platforms with each other.

The process of integrating SAP with Freshworks using Workato is pretty straightforward, and I really appreciate Workato in terms of integration because it is very simple and user-friendly when it comes to coding, and most of the part is a non-coding part. When there is complexity in functionality for one system, we have to do the coding on Ruby, which is also a fun part. I have used many integration tools other than Workato, and I find Workato quite easy to understand and fast compared to Integration Hub of ServiceNow, which is quite detailed and a little complex. Therefore, I found Workato easy and the speed is quite good.

The best feature of Workato is the ability to create a flow, and the majority of the things are already available in the module, which I find valuable. Additionally, if we have a demand for a specific tool, we can connect with the support team, and they can provide us what we need. Another valuable aspect is that there are many things publicly present in their library to use, and if I need to create an integration for a particular system to another, there might already be something available created by other users in public repositories.

The public repository helps me significantly because when I know the PRD document of the customer and understand their use case, I can look first in the public repository for something similar instead of creating everything myself, thereby saving my time. If I find something similar, I can take it as an example, utilize it in my personal flow, reduce my work on that particular task, and incorporate that chunk of flow into my own flow. Hence, the presence of numerous flows in public repositories is quite helpful.

Workato has positively impacted my organization, depending upon the customer's preference for which tool to use. While some customers prefer Workato due to its good customer support, it's ultimately based on the customer's needs, and we can perform integration using various tools available in the market. Personally, I enjoy using Workato, and my company feels that it results in significant time savings since it is easy to understand and allows new team members to onboard quickly. My superiors appreciate it as it enhances speed and accuracy, allowing QEs to understand and test completed tasks easily.

The positive impact on my team's speed and accuracy is evident whenever we start a new project, as new team members face challenges understanding how we use Workato. However, the best thing about Workato is the amazing and detailed documentation available on their website, which makes understanding and using the tool easy and fast. Even individuals without a coding background can contribute to projects quickly, as we have had freshers join with limited exposure to coding who can still catch up and integrate with projects swiftly.

Regarding improvements for Workato, there was an incident when we wanted a specific feature implemented, and the process was quite lengthy as we had to raise a ticket, track the ticket, and wait for the team to address it. Given the millions of users of Workato, when a customer has a specific requirement, it reflects a possible shortcoming in team resources. However, it's understandable given the high volume of tickets, and I believe Workato may be working on this aspect by leveraging AI tools in the future, which points to this being more of a manpower issue than a critical flaw.

I believe the process is already efficient, and I don't think I'm in a place to suggest improvements since I find Workato very amazing and well-kept.

I have been working in my current field for over one year and nine months, approximately.

We have never faced reliability or downtime issues with Workato; it is very stable.

Workato is very scalable, and we can scale any project using it, so scalability is not an issue.

I would say customer support is good, but I cannot classify it as very good as my personal experience varies.

Neutral

I have used multiple tools for the same integration before Workato, but it was not a personal choice; it was driven by my organization's requirements based on customer needs. I prefer using Workato because it's user-friendly while other tools tend to have much complexity due to being very detailed integration tools suited for large systems Oracle and SAP. Each tool has its own strengths and weaknesses, depending on the customer's requirements and our development needs.

I have definitely seen a return on investment from using Workato, notably in time saved and the reduced need for employees since it requires less time to understand and a handful of people can manage much larger integrations with this tool compared to others.

My advice for others looking into using Workato is to thoroughly review the Workato documentation, as it is very detailed, good, and easy to understand.

I think we have covered almost everything regarding Workato.

On a scale of 1-10, I rate Workato a 9.

There are workflows available to integrate with other systems and automate the process. One of the typical use cases is on order processing. It's an eCommerce-based system connecting with the VTEX as the eCommerce platform and the backend as SAP. The solution is integrated with Slack, and some approvals are required through Slack. Once you receive an order from the portal or the mobile app, it goes for approval directly on the Slack channel. It then goes to the next level for an SAP check for quality or approvals, and then it moves to the actual processing and submission for delivery to the customer. This workflow is nice, and we worked with it recently.

The automation in Workato is very good. Their automation and workflows are very strong, and you can build the workflows very easily and quickly. You can still have your complete workflow defined, and they call it a recipe. You can build a recipe very quickly and easily.

However, their API management is not very good, and their EDI pieces are not strong. The API Management needs to be matured. They have the major connectors available, but they still need to improve them.

A limitation is that their cloud presence is only in North America and Europe. They don't have anything in the Middle East or India. So they need to expand their base for companies that don't want to leave their country or region.

We have been using this solution for one year, and we are using the latest version. It is a pure iPad solution, and it is deployed on cloud.

We haven't faced any issues with stability.

It has good elasticity and is scalable. I am unsure how the solution performs during the festive seasons when our orders are multi-fold. We only need about two people for maintenance once it is in production. It will also depend on the business hours and what the business needs.

We get good support from Workato, and they help with the initial setup. As soon as you purchase the Workato licenses, you get a credit based on your requirements and the package you purchase. You can get 80 or even 120 hours of professional service support from Workato, which is helpful. I rate the technical support a nine out of ten.

Positive

The initial setup is quite straightforward. When connecting Workato with your on-premises system, you have to install the Workato agent on your network. It was not complex but a long process to configure and settle. Workato has not gone live for us yet, so only the developers are currently using it. But in terms of users, we will have close to 250 and maybe 30 additional direct users.

We are seeing a lot of different use cases where we can add new recipes because we started small, and there are many different areas where we can implement Workato for automation.

We have seen a return on investment.

It's recipe-based pricing. You have base pricing, and then you have recipe-based pricing. They sometimes have different kinds of pricing for commercial enterprises.

If you are going with a commercial price, it is cheap at around 50K per year. However, if you go with enterprise pricing, the price will be more at about 120k-130K. And for every recipe you add, it makes a price difference.

We evaluated MuleSoft because of the use cases at the time that MuleSoft did not have. The first feature we wanted was workflows, and we found that developing workflows in a Workato recipe was easier than in MuleSoft. Secondly, the price of MuleSoft was high, and Workato was cheaper. Thirdly, because we had a limited number of use cases, there was time sensitivity in choosing a solution. But now, if I had to choose between MuleSoft and Workato, I would choose MuleSoft.

I rate this solution an eight out of ten. Regarding advice, before proceeding with Workato, evaluate the product and understand your use cases. If you want to do batch processing or workflows that aren't heavy, Workato is good. However, Workato is not the best choice if you have heavy EDI.

In the next release, we would like to see more connectors. They are still evolving on many connectors, and EDI support is needed. In addition, many customers may not want to use Workato because they are on AWS Cloud, and those who use Azure Shop or GCP Shop may feel the transaction has a cost. They have to go with a cloud-agnostic platform. Workato plans to provide its services on different clouds, not only on GCP or AWS.

We use Workato as an iPad solution and a platform as a service. We take a subscription and build services on top of it. The services communicate with various enterprise applications. Some examples are Salesforce, NetSuite, and Workday, for billing, HRMS, and financing applications. So when we try to create a centralized integration environment, we use Workato as a platform service.

It's a no-code platform, so all the activities we create are drag-and-drop and very intuitive. It's easy to understand, makes flows and is efficient. It's less hassle regarding the code when we move the service we created from one environment to another. In addition, it has a user-friendly interface.

Since it's been promoted as a low-code and no-code platform, it is tedious to make a tailor-fit function. Trying to extend the customization limit becomes a challenge as the platform is not code-friendly. It is a challenge to make tweaks and create custom features.

We have been using this solution since 2018. It is deployed on AWS cloud and is updated automatically.

Stability is one of the main focus points, and we have seen fewer failures in terms of platform stability. They basically have zero downtime and even if there is, they ensure they pick up all the events that failed and reprocess them. I rate the stability a nine out of ten.

It's fairly scalable and they have multiple versions of their licensing. Depending on the organization's size and requirement, they can charge based on the number of transactions happening on a given interval or the number of services built and running on their platform. So depending on the usage and the organization's requirement, we can tweak it.

The technical support team is pretty responsive, and I rate them an eight out of ten.

Our choice of Workato was based on the cost and the users. We figured out an excellent balance between these two things, which was a good fit. So with the number of transactions happening currently, we are fairly comfortable with the license cost.

The initialization was relatively easy because they provided us with all the training materials on the kickstarter front. It's mostly a drag-and-drop to create the services and the business flows. I rate the setup a seven out of ten.

Most of the features in Workato are already active once you get the license. However, when you try to create a connection between your internal applications, it takes time. In addition, creating the business flow is also time-consuming. Aside from that, other actions are fairly easy and take minimal effort and time. For example, deployment, making services live and disabling certain services can be done with just one click. We did not need professional services for the deployment.

The cost is dependent on what kind of agreement an organization goes with. There are multiple licensing versions, and a company can choose depending on what kind of license a company is comfortable with. I am unaware of the exact costs. It is an excellent tool for small to medium-scale organizations.

I rate the solution a seven out of ten. Regarding advice, if a person is already into the enterprise integration and domain and if they have knowledge of how the business processes and the business flow, it would be fairly easy to understand Workato.

Regarding additional features, we would like to see a feature where we can expose certain data in terms of dashboards to an external viewer. It would be good if they didn't require access to log into Workato and send all the data. At least the dashboard features should be available in an external environment so all stakeholders know what happens with transactions.

We use Workato for iPaaS, which is like a middleware enterprise service bus. We use it for transformation, quick data migrations from one platform to another, and building connectivity. It's got over 300 pre-built connectors. We use it mostly for migration projects for quick benefits over traditional solutions.

Workato is low code, intuitive, and easy to use. The biggest feature of Workato is its pre-built connectors. Suppose you have to move something between Salesforce and ServiceNow. Based on the volume of data you're looking at and the complexity, this would take anywhere between three to six months in SSIS. With Workato, you can do it in two to four weeks once you have all the data and requirements mapped out.

Workato's Extract, transform, and load (ETL) and extract, load, and transform (ELT) are not very strong and could be improved for very complex transformations. Workato's licensing model is a bit confusing, and it's not very transparent. They charge for SAP, but then there's a cap on the number of transactions as well. I found it very difficult to understand how each transaction is considered.

I have been using Workato for more than two years.

I had no issues with Workato’s stability.

I rate Workato a nine out of ten for stability.

Workato is a pretty scalable solution. About three to four of our customers are using Workato.

Workato’s initial setup is very easy.

We have seen a return on investment with Workato.

Workato is an expensive solution.

Workato is deployed on-cloud in our organization. They've also got an on-premises connector, but primarily it's on-cloud. It's a SaaS application.

If budget is not a constraint, I'd definitely recommend Workato because of its ease of use and the time it takes to get started and see an outcome. The solution has helped our customers see an outcome in less than two weeks. The solution's cost is on the higher side, but if budget is not a constraint, then you can choose Workato.

Workato is a pretty solid platform. The solution's ease of use and the ability to deliver results make it very intuitive to define complex transformations.

Overall, I rate Workato a nine out of ten.

We use the solution for enterprise integration, integration between applications, and enterprise data layers via IPR.

The valuable feature of the solution is its ease of use of its basic features.

The management dashboard in the solution is an area with shortcomings that needs improvement.

I have been using Workato for about eighteen months. My company has a partnership with Workato. Also, I am using the solution's latest version. My company has a partnership with Workato. We are also customers of the solution.

Stability-wise, I rate the solution a ten out of ten.

Scalability-wise, I rate the solution a ten out of ten. Speaking about the users is one thing, but considering applications, it's used for about 300 different applications. So, you can pull out around 300 applications to a user.

I had contacted the support, but it's more around connecting to different technologies and the actual technology itself.

The initial setup was extremely easy. We have deployed the solution on the public cloud as well as connectors on-prem connections.

Speaking about price, I would say that it's market-related. Also, there are costs in addition to the standard license fees since different add-ons depend on what you require.

I would ask those considering using the solution to sign in and understand the market and what it's meant for so that they know what it is not meant for while understanding its capabilities.

I rate the overall solution a ten out of ten.

Our primary use case is for all the integration we do for Coupa, the Salesforce.

The most valuable features are easy integration, quick tab to develop, quick tab to market, and the interactive integration platform.

I would like to see the dashboarding and reporting processes improved.

I have been working with Workato for the past two years.

They have been doing fixes to bring this growing solution to maturity. I would rate it a seven out of ten.

The scalability of the Workato on a scale of one to ten is an eight. There are currently more than one hundred users in the organization that use Workato on a regular basis.

I would rate technical support an eight out of ten.

I have used UiPath but the integration is not seamless. Workato is better for quick time market with integration.

The initial setup was pretty straightforward and takes around two weeks for implementation. You need to research and make sure it follows all of your company's security compliance policies. There needs to be an audit and agreement. The next thing will be getting an instance in their platform, then some details, and getting that set up. You will set up your environment, depending upon your organization, set up the different backgrounds, and get user access.

We are currently seeing more than forty percent of our return on investment.

On a scale of one to ten, the pricing is around a six. We have a consumption model and the pricing is higher. If you are using any kind of ML-based approach, machine learning, or some advanced analytics, you may have to pay more.

If you are looking out only for integrations, integration with different components, then they can link for Workato. But if they want to do more like an API, build an API, or get a platform only to create APIs and manage the APIs, right, there are some alternate other solutions and products which they can actually have a look at. We have MuleSoft specifically only for creating the APIs. But for integration, when it comes to enterprise-grade implementation, right, that is where Workato will be more helpful. But if it is only for a very smaller use case, only a limited set of users going to use it, then they may have to think of the cost and other factors, if Workato will be a good fit for that. I would rate Workato a seven on a scale of one to ten.