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

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 working as an integration lead, and we had a project where we implemented an integration for one of our clients. The use case in our project was to bring data from a source system, Shopify, where we transfer all dimensions and fact data to Snowflake. This integration was achieved through Workato.

The most valuable features of Workato include event streams that enable loosely coupled APIs and maintain reusable flows in the platform. We can bind multiple subscribers to them and have the same data supplied across multiple channels and multiple subscribers.

Another valuable capability I am currently exploring is Intelligent Document Processing, which allows us to read PDFs and images and extract those details. This is especially useful for invoices and purchase order receipts.

The recipe-driven automation in Workato is very impressive. For the same client project, we extracted purchase orders from emails and pushed them into the file system. The automation worked as expected, and we didn't face any issues with the Workato email connector.

Regarding connectors, I have used approximately 20 to 30 connectors. The most useful was the Ruby connector, which allows us to run Ruby scripts and get the required output. This was particularly helpful during our integration when we extracted and implemented business logic for multiple complex transformation scenarios. Similarly, we can run Python scripts and JavaScript as well, making these useful tools for data transformation.

There are storage limitations in Workato. The event streams come with a limitation of only 512 KB. If the payload size is huge, those payloads cannot be published into the event stream. We have to use storage and split the data. It would be beneficial if Workato could improve these size limits on event streams.

The Ruby connectors also come with a memory size limitation of around 45 MB, which could be increased to around 100 MB.

Regarding stability improvements, the memory capabilities need enhancement. Additionally, there was an action missing for inserting data into Snowflake tables. It would be advantageous to have the ability to insert records in batches. This is a missing point and an area for enhancement.

I have been working with Workato for the last six to eight months on a project for one of my clients, Sempra.

We haven't moved our APIs to production yet, but it has been stable across all the connectors and versions we are using. I don't see any major issues at all, so whatever versions we are using are stable.

For the stability rating, I would rate it a 7.

Workato demonstrates good scalability. We can scale as much as possible according to our plan, whether it involves recipes or connections.

I would rate the scalability of Workato an 8.

I interacted with technical support regarding an issue where we needed help with a memory limitation. We reached out, and they informed us about the maximum memory limit for our connector. We were looking to increase the memory size, but that wasn't possible. I'm looking forward to how they can improve this size limitation for higher volume integration.

Based on my experience with the technical support, I would rate them a 9.

Positive

The initial setup of Workato was straightforward, and I didn't face any challenges. This was due to the training materials shared by the Workato team, which were really helpful.

I work with the client through conference calls, so our architect handled the purchase. I haven't utilized real-time data synchronization in my project.

For metrics and KPIs regarding AI-driven insights, I check dashboards where I monitor task usage and dependency graphs.

I haven't utilized any AI capabilities in my project yet.

I cannot comment on Workato's compliance with industry standards.

I haven't been working with anything else other than Workato in the last 12 months. I can confirm my availability over call or email.

Overall rating for Workato: 8 out of 10.

My main use case for Workato is to do the maintenance of some BPA automation processes, building a recipe for everything in the process to make everything go smarter and faster. It works better than themselves.

One of those weekly automation processes uses a lot of approvals in the process, and I use Workato to define these approvers, set them, and check if everything goes well.

In Workato, I can see everything that goes behind the process. You can see how everything works, how the tool works in the background. If something goes bad and an error appears, I can see why it happened.

The best features Workato offers, in my opinion, are the easy integration with many different types of tools.

The Workato interface is so easy to use.

Workato has impacted my organization positively by reducing errors, which is one of the most important improvements I can see, and one great thing is that in Workato I can do many things that the main BPA platform we use does not do. Error reduction has helped our team in Workato as we can see more details about the most common errors and what makes everything go bad. With this specific data, we can develop a new and better solution. Workato helped us to do this. We can see more details about the errors and solve them.

Workato has improved a lot of my work because there I can develop many flows easier and faster. At this moment, I do not have anything that frustrates me.

At this moment, I do not remember anything I would see as an improvement.

I chose this number, 8.5, because if I would give a higher score, Workato should improve in some areas.

I have been working in my current field for one and a half years.

I think it is easy to scale up in Workato because you can build flows with many actions and steps, allowing you to create big processes with many phases. I think that is very easy to scale up.

I have never had to contact customer support, so I do not have any experience with them.

Negative

Before Workato, I used the native solutions of the platform called Pipefy.

My experience with pricing, setup cost, and licensing was a bit challenging in the past because the client I was working for did not have an unlimited license to use unlimited tasks and could not create many different processes and flows in Workato. However, today, it is a good experience because the client has an unlimited license, allowing me to do everything I want in Workato, creating many different types of flows and complex processes.

I did not evaluate other options before choosing Workato. Workato is very stable, and I would like to keep using it.

My advice to others looking into using Workato is to read the documentation of the platform to know how to use the actions, how to use the tasks, what to input, and what comes in the output. I think that by reading this documentation, you can understand faster how the platform works and do many different things more quickly.

At this moment, we are a reseller of Workato, but we do not have close contact.

I was not offered a gift card or incentive for this review, and I have no additional thoughts about Workato before we wrap up.

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

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