Workato Reviews

I am using Workato for integrating and automating solutions for finance, HR, and IT. Specific use cases include onboarding and offboarding for HR, handling invoices for finance, and creating tickets for customers.

When compared to other tools, Workato is a low-code solution with a user-friendly drag-and-drop UI. It comes with pre-built connectors, eliminating the need to write APIs. Workato ensures data encryption in transit and at rest, and offers built-in error monitoring with alerting capabilities through Slack, email, or external monitoring tools. It also facilitates role-based access.

One area for improvement is the CI/CD pipeline, which lacks a version control system similar to GitHub for easier deployment. Though it has a recipe life cycle management, it does not automatically integrate with a GitHub-like facility. Additionally, the cost for high volume integrations could be reduced, as Workato uses task-based pricing, which can become expensive with higher usage.

I have been using Workato for more than four years.

Deployment is straightforward, requiring the creation of a manifest that contains all the necessary logic and files. This manifest is then migrated to higher environments.

Workato is generally stable, although there are some limitations, such as a hard limit of 50,000 records for CSV file processing. To handle more than 50,000 records, I use scripting actions like Python or JavaScript to process large data in chunks.

Workato's support is robust, featuring first and second-level support. Minor issues can be addressed through the chat feature in the UI. For complex issues, the response may take a day, and tickets can be opened for follow-up. Customer Success Managers help expedite issue resolution.

Neutral

While the upfront cost is high due to task-based pricing, the cost is relatively low in terms of development because Workato provides necessary connectors for integration use cases.

I would recommend Workato because everyone is moving away from writing extensive code. In the current trend of AI, tools that integrate systems easily are valuable. Overall, I would rate the solution a 9.5 out of 10.

Other

I use Workato as middleware for cloud integration within my organization. It is employed to integrate systems such as ERP and customer planning systems. The automation capabilities are particularly useful for onboarding a new employee, allowing for their access to be automatically set up across approximately twenty systems such as payroll, training portals, Salesforce, and SAP ERP.

The main benefits of Workato for me are that everything is cloud-based, eliminating the need for installation or maintenance. It allows app-to-app and real-time integrations, which significantly enhance process efficiency. When an employee joins, accounts are automatically created. Moreover, AI automation simplifies integration development by understanding requirements from prompts and creating the necessary automation.

The Electronic Data Interchange (EDI) capabilities could be improved.

I have been working with Workato for about five years.

I find Workato stable.

In my experience, it is scalable.

I reach out to the professional services team or customer success team for technical support, and they provide immediate responses.

Positive

I am working with a Boomi solution alongside Workato.

The initial setup process is straightforward for me as there is no need for extensive setup, allowing direct development.

In my experience, we have seen a return on investment, with results visible within a week.

Workato is a SaaS product, and its pricing depends on usage.

I also work with a Boomi solution.

I recommend Workato for even small customers who may not have a large IT firm, as it can be used as an integration product to automate business processes. Overall, I rate it nine out of ten.

Public Cloud

Other

I am an integration consultant, and I use Workato for integration. Recently, one of my clients wanted to migrate from using Workato to another platform, so I started exploring Workato to understand why it's attracting big clients. The focus has been on cost efficiency since the cost of other platforms is quite high. I noticed Workato is less expensive and offers similar integration capabilities.

I appreciate Workato's job reporting feature, which consolidates recipes and jobs for easy management. I also like the control over performance, cores, etc., and the simplicity of creating recipes. Workato has around 100 connectors, allowing anyone, even without an IT background, to work with them. Additionally, the platform resembles Salesforce in presenting both solutions and their benefits.

Currently, Workato is a low-code platform without native programming capabilities. I would appreciate having a dedicated programming language for tasks like transformations and functional programming. Although the drag-and-drop framework is easy, incorporating a coding language could enhance functionality.

I have been using Workato for at least three months.

Deploying Workato was easy and clear. Although the components are good, I would like an IDE or similar tool to test recipes locally. Considering AI integration with agents in future releases would also be beneficial.

I have not observed any stability issues, but it should be tested with large files or data sets to determine its latency performance.

Workato lacks manual control over scalability. Their cluster management automatically calculates the necessary resources like VCores.

I have used other solutions previously but explored Workato when my client wanted to switch due to the high cost of those solutions.

The initial setup was straightforward and fast. Connecting components took some time depending on the authentication method, such as OAuth 2.0 or JWT, but overall, it was easy.

Compared to integrators like Boomi or MuleSoft, Workato is priced reasonably. While Workato was a target for acquisition by Salesforce, its CEO declined the sale, but Salesforce is one of its investors.

Solutions evaluated include Boomi, MuleSoft, and Workato.

For new users, having an IT background simplifies using Workato, especially regarding aspects like schedulers and connections. Those without an IT background should acquire basic IT knowledge. My overall ratings are eight for user experience and courses, ten for simplicity, and eight in terms of cost. I suggest creating academic projects or exercises for better learning. Although Workato is new in Europe, it shows potential for being cost-effective and time-saving. I rate the overall solution as eight.

Public Cloud

Other

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.

Public Cloud

Amazon Web Services (AWS)

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 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.

Public Cloud

Amazon Web Services (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.