Workato Reviews

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.

As part of the integration team, we use Workato for integrating systems such as NetSuite and Oracle ARCS. Specifically, we design recipes in Workato using both connections to collect data from NetSuite based on saved searches. This includes accounts and GL balances, which we refer to as amounts. We gather these from saved searches in NetSuite, perform some transformations in the Workato recipe, and then transfer that data to Oracle ARCS. In Oracle ARCS, we create profiles for the specific data and transfer the amounts from NetSuite to the corresponding profiles, allowing clients to perform their monthly or quarterly reports based on this data.

I have worked with Workato's real-time data synchronization feature, such as collecting data from NetSuite and updating Oracle ARCS. This process is a real-time sync; every day at 6:00 a.m. PST, the recipe runs, executing saved searches in NetSuite to pull data and transfer it to Oracle ARCS. Additionally, I have worked on other projects involving real-time synchronization, such as from Salesforce to NetSuite, where we update account, brand, and country information in Salesforce. The recipe triggers in Workato based on specific conditions, and we pick up record details from Salesforce to update the same records in NetSuite.

Currently, we primarily utilize the NetSuite SOAP connector for many projects in my company. By using this connector, the NetSuite team internally creates some saved searches and provides REST API calls. We then utilize the HTTP pre-built connector in Workato to make API calls, process the information, and send it to the destination system. Using the pre-built NetSuite SOAP connector enables us to execute saved searches or SQL queries, allowing us to search for data cost-effectively for clients without requiring new connector purchases.

The best feature of Workato that I especially appreciate is its low-code, no-code platform. Many candidates find coding hard to grasp, so with this Workato platform, we primarily use low-code, no-code methods. In cases where a client's requirement is atypical and cannot be met using Workato connectors, we create a custom connector using SDK. Aside from that, we do not utilize any technical coding in Workato while developing recipes; we mostly leverage the platform. This is the main aspect of Workato that appeals to me.

The main benefits I have seen from using Workato include its ease of use and low complexity. For example, tasks such as data field mappings or data verification can be managed by clients themselves without needing to reach out to a Workato developer.

Regarding assessing the impact of recipe-driven automation on task management efficiency, we use a real-time approach. Instead of applying condition logics, we implement batch processing, where each batch contains around 50,000 or 30,000 records. We process those records in batches and utilize conditional statements, which reduces task utilization in this complex integration system.

From my point of view, a few improvements regarding Workato could include the notification system, which should inform clients or businesses quickly and be accessible through a mobile app. For example, Salesforce has a mobile app that provides notifications about errors or changes in business strategies. If Workato could develop a similar mobile app, it would be a great advantage for businesses and clients.

Apart from the mobile app, I believe incorporating AI would be a significant improvement for Workato. Furthermore, the recently used AI agents in Workato's chat support would be a great feature as well.

I have been working with Workato for five years.

I have observed some minor stability issues with Workato, particularly related to connectors failing occasionally and delays in report sending.

Regarding scalability, I haven't experienced any issues in my past projects; I find it easy to scale up or down.

On a scale of one to ten, I would rate the technical support from Workato an eight, based on my experience with a few support projects for my company.

I have basic knowledge of MuleSoft. Initially, at the start of my career, I built some projects on MuleSoft, connecting Salesforce and NetSuite using MuleSoft Studio. Additionally, I have industrial experience with Salesforce Admin tasks for Sales Cloud and Service Cloud and some knowledge in CPQ from Salesforce. Currently, I work as a member of the integration and data teams, managing tasks related to both areas, including Power BI reporting.

In terms of comparing Workato to MuleSoft or other iPaaS products, I find that Workato has a user-friendly interface compared to MuleSoft. MuleSoft includes many versions, while building recipes or programs in MuleSoft feels more complex compared to Workato. While MuleSoft is stronger in terms of available connectors and systems, I believe Workato has potential to be widely adopted as confidence in its use grows, similar to MuleSoft's current standing.

In terms of ROI, or return on investment, they mentioned that they charge for recipes based on time consumption. If we build callable recipes, those do not incur charges. For main recipes, there are charges, so by focusing on creating as many callable recipes as possible based on requirements, we can improve cost efficiency for the business.

Regarding pricing, my core team members, including my senior member and manager, handle the licensing and setup costs. As I lead a few team members, they take care of the yearly costs associated with licensing and other financial aspects.

As an integration team member, we mostly utilize the Workato platform over MuleSoft and Dell Boomi. However, in the future, there may be considerations to adopt one of those platforms in conjunction with Workato.

From my experience, I highly recommend using Workato because it offers cost efficiency compared to other iPaaS technologies. The training process for newcomers is easier compared to using Dell Boomi or MuleSoft. Workato is simple enough to train individuals on, and its tool efficiency is enhanced when an experienced person manages it. Overall, I suggest businesses adopt Workato over alternatives such as MuleSoft and Dell Boomi.

Currently, we primarily utilize the NetSuite SOAP connector for many projects in my company. By using this connector, the NetSuite team internally creates some saved searches and provides REST API calls. We then utilize the HTTP pre-built connector in Workato to make API calls, process the information, and send it to the destination system. Using the pre-built NetSuite SOAP connector enables us to execute saved searches or SQL queries, allowing us to search for data cost-effectively for clients without requiring new connector purchases. I rate Workato a nine out of ten.

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.

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.

It is used for customer onboarding and HR self-service. We are using it in finance as well.

We are using its latest version. It is a cloud-native product. It is on a public cloud. We use their service. They're an iPaaS provider.

Before this, we would've to build a lot of manual requests into our Workday HR application. It was a bit complicated, but now, we build the automations through Workato. The previous process for requesting holidays with Workday was very clunky. The current process with Workato is easier. The approval process for approving holiday requests from employees is also much easier. It is faster, it is more efficient, and it takes less developer time to build the automations as well. Given that we don't have that many developers anymore, it is much better and much easier to use.

It is very easy to use. It takes complex workloads away, and it provides very smooth integration. It has got a lot of out-of-the-box connectors. It has got a lot of out-of-the-box APIs, which makes it really easy to integrate with applications for different use cases, whether it is in finance, HR, or customer operations. It is by far our favorite integration product.

Like every product, it constantly needs to be updated because the industry and applications keep changing, but we are very impressed. I can't really see many areas of improvement because Workato is bringing out new enhancements to the product every couple of months. We don't have any complaints. The only minor drawback would be if there was a UI at the front of it, for apps and for a portal as well, it would make it really easy. It would be really useful if there were more apps capabilities.

I have been using this solution for about 18 months.

It is very stable. The product has been around for a few years. It is going to do very well. It seems to be stable. It is built on AWS, and that's a platform we use as well.

It is very scalable because of being a cloud service.

Their customer support is very good. They also have a customer success team that has helped us out quite a bit. 

We used to use on-premise products from TIBCO and Oracle, and they were very cumbersome and very difficult to use, but Workato is much easier.

We bought the core platform. It was very straightforward to set it up because their customer success person helped our team get it off the ground. It only took about a week to get the product up and running.

We did some of the training ourselves because we had free training course providers. So, we trained up some of our own people.

I'd highly recommend it to any enterprise customer. The product is very good. I'd rate it a nine out of ten.