Workato Reviews

The usual use cases for Workato include real-time data processing from either SFTP or SAS, and we have implemented multiple use cases for our clients in the past 3.5 years. For example, the employee data processing, where they use Workday to hold employee details, is the source for us to integrate data from Workday to multiple target systems, such as communications through Slack or meetings via Zoom. We also utilize ITSM tools such as remedy force services and several other core systems, syncing employee master data on a daily basis for onboarding, offboarding, and data changes.

Another use case includes the security systems, where we implement badge access for new onboarding or visitors coming to the office. We have integrated various systems, from Workday to JumpCloud to Genentech and ITSM tools such as Freshservice. As a middleware, Workato helps us automate business workflows and reduce manual work, thus enhancing productivity and efficiency. Additionally, we have another client for whom we implemented financial transaction data integration from SAP to Kupa and different systems, showcasing Workato's role in data integration and business workflow automation.

Real-time data synchronization is being used for multiple clients, where many SAS applications have real-time triggers. In Workato, we have triggers to receive data from sources, whether from an ERP system or any other system, and we have successfully implemented that real-time data sync.

We use many of the pre-built connectors in Workato on a daily basis. There are numerous connectors that enhance our interaction with Workato. The number of connectors we typically use depends on the use case; for complex use cases, more connectors are required. It entirely depends on business requirements and specifications, so we cannot define a specific number of connectors.

The most valuable feature of Workato is that billing is based on task actions; whatever actions we take on the Workato platform will determine the task consumption and billing for each workflow. More optimized workflows lead to less billing for clients. Furthermore, they have introduced a Copilot feature for automation, helping build recipes and code with simple prompts. Additionally, they are developing AI solutions for clients. These are some top features, along with various others implemented per client specifications, such as CICD implementation and runtime connection changes.

The benefits of using Workato for our customers include automating business workflows and data integration. By addressing their manual efforts, which are time-consuming and prone to errors, Workato helps clients reduce costs while increasing productivity. We implement solutions that enable seamless data integration between different systems, minimizing time-consuming manual processes. A positive impact we see is cost reduction, as manual efforts are significantly lowered. For example, in production support teams, manual processes are streamlined through CICD implementation, allowing for a seamless integration of different environments with minimal errors and faster deployment.

In Workato, there are some limitations regarding very high transactional data in file formats. For instance, we have a 90-minute job timeout, and queues larger than 10,000 size will be purged. Additionally, processing large files requires chunking them into smaller sizes. The team is actively working on customizing the platform per client requirements and is rapidly releasing features to address these limitations.

I have been currently using Workato and implementing the solution for the clients for more than 3.5 years.

Workato is quite stable, and they are continuously improving the product's stability by implementing various connectors that are already available.

I am not sure about Workato's scalability, as that falls under the Workato team's expertise. We focus solely on implementation.

We have communicated with Workato's technical support in the initial days. I would rate the technical support from 7 to 7.5; it may also depend on the different people we interact with, but I would rate it up to 8.

Positive

The initial setup for Workato is relatively straightforward because it is a cloud application. The Workato team provides the necessary support for setup; we just need to specify our requirements, and they will create the access for us.

I have been working with clients for Workato implementation, focusing on consulting and implementing solutions for their business needs. We automate basic workflows and handle various complexities to seamlessly integrate different SAS applications and other applications. Regarding the pricing of Workato, I don't have much knowledge because I haven't purchased it; that information primarily comes from their implementation team that handles client solutions. My overall rating for Workato is 8 out of 10.

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 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 plenty of use cases for Workato. We have a vendor management system, which is a different SaaS product, where Atlassian as a company onboards our vendors. We put a purchase order, they address that purchase order, and then they raise invoices, all on the vendor management system. We need to sync this information to our ERP system, as we use a different ERP for financial management. We sync the data of vendors getting onboarded and raising invoices into our financial system for payments. To sync the data from the vendor management system to ERP, we use Workato for integration. This includes invoices, credit memos, supplier onboarding, and changes to supplier bank details for payments. Internally, we also have an employee expense management system where employees submit expense details for reimbursement. Since this financial information needs to be synced, we sync employee details and expense claims into our financial system, which is again an Oracle product.

I have utilized Workato's real-time data synchronization feature for managing vendor invoices sync to Fusion, which is our ERP application. Previously, we did batch syncing, meaning data synced weekly or daily, causing finance team members to have to review a bunch of invoices at once. With Workato, as soon as an invoice is put in our vendor management system, we sync it within two to three minutes, providing a real-time experience. This process improves vendor relations as it prevents delays in payments that could lead to breaches of payment terms or dissatisfaction.

I find the automation building in Workato quite easy, which is a general feature I appreciate. Unlike other automation iPaaS tools I've used that require installations on my laptop, with Workato, I only need a browser and an account to build automations. They also provide an easy way to parse XML, CSV, and JSON files without needing to know any programming language. If you're familiar with these data formats, you can navigate through building automation easily. Additionally, there's something called SQL queries; it's not a database but an app where developers can parse a collection of data using SQL, which many in IT are familiar with. If a transaction fails, I can replay that transaction with just a click of a button, making it much easier compared to other systems requiring additional setups for failed transactions. Workato is also rolling out amazing features such as workflow apps, allowing easy building of UI-based forms that operate within business processes requiring manual interventions, such as approvals or rejections.

I can assess that Workato's recipe-driven automation has saved the finance AP team around 780 hours of their time in just the last year through a couple of automations for vendor management. That's a quantifiable number focused on just vendor management that I've recently presented to the business.

In my opinion, Workato's licensing model could be enhanced. They have evolved from a recipe-based licensing system to a task-based one, which can be limiting for productivity. An open licensing option would allow for unlimited usage, which would simplify management, although there could be downsides such as paying for unused capacity. Additionally, Workato currently cannot handle huge loads of transactions, which is a significant drawback.

I have been working with Workato for roughly four years, predominantly three and a half, and three to four months on exploring the platform. Overall, it has been roughly four years in total.

Before Workato, we used MuleSoft and custom integrations developed on a Java framework and Spring Boot. The leadership team decided to switch because MuleSoft was becoming costly and lacked the innovation expected following its acquisition by Salesforce.

Workato defaults to AWS for its cloud infrastructure, and we don't have options to deploy it on-premise or on other cloud providers such as Azure or Google, as we do with MuleSoft.

I would rate Workato's stability at 99.999%. I haven't faced downtime, but the open agent component that connects Workato cloud to secure networks shows instability. This component is about 95% reliable, requiring occasional restarts. Workato manages its upgrades efficiently, providing advance notifications and guidance.

As for scalability, if there is a sudden burst of transactions, Workato struggles to handle it efficiently. While I can adjust configurations easily to manage expected loads, it's not ideal for sudden spikes.

I would rate Workato's technical support a 10 out of 10. The customer service has improved significantly over the last two years, making it easy to approach them without ticketing. They provide immediate assistance through a chat option on the platform.

Positive

Before Workato, we used MuleSoft and custom integrations developed on a Java framework and Spring Boot. The leadership team decided to switch because MuleSoft was becoming costly and lacked the innovation expected following its acquisition by Salesforce.

I work for a company which uses Workato to build our automation, and I use the platform to develop certain automations. I am a Senior Integration Engineer at the current position, and as an individual contributor, I write certain automations on the platform itself.

I don't know how Workato was purchased, but not through AWS. To give context, we had MuleSoft with us, and the prices of MuleSoft were increasing, which is one of the iPaaS platforms. The leadership team wanted to see what other emerging iPaaS platform was coming at a lower cost, and if it solved our problems, we would use it. That's when the interest to look out has come in, and I believe it's through the leadership team who knows somebody at Workato that pitched in that idea. It took two to three months of assessment, and then we decided to go with Workato.

Onboarding new resources into our development team is easy due to Workato's usability, enabling them to start delivering projects within a week if they have a couple of years of experience in the integration domain. This is much quicker compared to other tools I've used, which required thorough training and hands-on experience that could take much longer.

I use many of Workato's pre-built connectors including Fusion, Salesforce, SFTP, HTTP, Database, File, S3, SQS, and DynamoDB—probably more than 10 connectors. We even built a custom connector with support from Workato to meet specific needs. The pre-built connectors facilitate real-time sync, helping developers who don't need to know the system behind the connector. They can efficiently deliver automations, enhancing overall developer productivity.

I have experienced Workato's AI-driven insights, particularly for data mappings and document processing features using OpenAI LLM. We also utilize the Insights API to track how many recipes are consumed and our total task assignments under our license. Through custom-built integrations, we receive notifications about sudden bursts of traffic flowing into Workato, thus allowing the operational team to review potential causes for these spikes. We use metrics related to our task budget from Workato to ensure effective resource management.

I consider Workato's pricing to be mid-range, not too expensive but not too cheap either. As they release more features, such as workflow apps and the document processor, these come at extra costs. Currently, I would categorize Workato as moderate in pricing. My overall rating for Workato is 8 out of 10.

My use cases for Workato include business systems integrations, primarily with billing, revenue operations, HR operations, data migrations, ELT, and monitoring.

What I admire best about Workato is that it is really easy to use and features are continually improving. Most recently, I appreciate using the SDKs because they are really configurable to do what I want in a few steps, cost-wise. The platform is highly configurable and able to connect to anything I want.

From using Workato, I have seen benefits such as writing small reusable components, leading to overall development time being quite low for what we need to do. When new requirements come up, it is really easy to make small tweaks or add another recipe if that is the right thing to do.

Based on my experience, it would be really beneficial if the unit tests were improved. It would be helpful if unit tests could use formulas when validating outputs as some data is updated based on the job id or date that the unit test runs. They also do not work as effectively for long-running recipes. I would recommend continuing to add improvements in the unit testing framework.

I have been using it for about 8 years.

I have not had issues with stability. They have the standard outages, but they do not exceed the standard cloud outages.

Workato scales effectively as long as you know how to build to scale.

The customer support team is always willing to help. The first line does not know as much as the higher tier support, but they are able to figure it out and they are really nice about it and communicative.

Positive

In past companies, I used Boomi and Alteryx.

The initial setup is straightforward; there is not really any setup unless you are migrating from a previous tool. Even if you are migrating, it is just building from scratch basically.

The pricing depends on the size of your organization. Higher volume is less expensive on a per unit cost.

I absolutely think it is worth the money to have Workato as a tool. No matter where you are at, if you are limited on people or want your people to do more value-added activities, then it is definitely worth it to set something up and not have to worry about it anymore.

A business user could go in and develop something fine, and it would do what it is supposed to do. Like any tool, Workato performs better with people knowledgeable of how to best build within the platform.

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.

In my previous organization, I worked with Workato for around two years and I've got the chance to use Workato for almost a year, integrating some of the sources with our product.

Our main use case for Workato was that we were getting some data from an API from our customer and pushing that data into our product, integrating Workato to pull in the real-time data.

We also wanted to trigger some kind of real-time notification with the exact count or data we were sending by email, and it was great to get a live report on email.

The best features Workato offers are the variety of connectors that allow you to connect to various sources and communicate with the sources, which stand out in my opinion.

Having so many connectors was valuable for my work because you get to rely on one tool to connect to multiple sources, so it's great to see one tool having a variety of connectors which help you stay in one ecosystem to connect to various sources.

Workato has positively impacted my organization by improving processes overall, as it has saved time because it was easy to connect through the UI without needing technical, detailed coding experience.

The time saved by integrating Workato has changed our team's workflow significantly, as we used to rely on our application development team to configure a Kafka connector for real-time data, but instead, we integrated Workato to push the data directly into our data warehouse, which saved a lot of time for our overall team.

I'm not aware of any improvements needed for Workato; whatever I have used so far has been really effective.

I don't have any comments now on how Workato could be better since I don't currently have any use cases for it.

I have been working in my current field for more than three years.

Based on the kind of work I've done, I find Workato to be stable.

From what I've experienced, I feel Workato's scalability could be great; even though we haven't processed huge data, the performance and speed seem scalable.

I don't know about the customer support for Workato since I have never reached out to them.

Negative

We haven't used any other solution before Workato, so it was the first tool to ease our work.

I don't remember if we purchased Workato through the AWS Marketplace; our DevOps team might have handled that.

I don't know about evaluating other options for Workato; the decision might have been made at a higher level, possibly by the DevOps team or business team.

My advice for others looking into using Workato is to check the Workato marketplace for available connectors if you have multiple sources to connect; it's an easy tool to work with, with a user-friendly interface and a variety of options for customizations.

In my previous company, we were just a customer of Workato.

I haven't been offered a gift card or incentive for this review.

I think Workato is a great tool.

On a scale of one to ten, I rate Workato a seven out of ten.

We use Workato for our G&A across finance, accounting, procurement, audit and compliance, HR, GTM which covers sales, marketing, customer success, as well as IT.

Wherever we need process automation, APIs, reverse ETL, event-based automation, intelligent document processing, or need to build AI agents, that's where we are using Workato.

Currently, I cannot share the exact count of users, but it includes the COE (Center of Excellence) and several lines of business including the marketing and HR departments.

There are several features I find best about Workato, with the first being its ease of use, reduced time to market, and their customer support.

It serves as a one-stop shop where you can maximize coverage on both the automation and AI side.

The initial setup of Workato is easy to use, and the customer support team ensures proper adoption of the Workato platform, helping us solve the right problems. We are getting benefits from it, adding business impact and value.

While there are still a few areas where Workato has room for improvement, they’re making impressive strides in advancing their AI capabilities and enhancing their RPA features. Their recent conference showcased significant progress in this direction and was truly a remarkable experience.

I have been using Workato for almost three years now.

The stability of the product is quite stable.

Their customer success team, support team, leadership and account executives are amazing.

I have used different solutions before.

I have experience in the automation space for more than 18 years, and I have worked on multiple integration platforms including JCAPS, Oracle SOA Suite, Oracle Service Bus, BPM, MuleSoft, Boomi, and SnapLogic.

With Workato, you can automate any use case, but before implementing your use cases, I suggest understanding your processes better.

Try to optimize the processes and make sure you have good data quality because with Workato, you can automate any complex process, but if you do not optimize your processes or work on your data quality, it will be garbage in, garbage out.

I would recommend this product to other people. I rate Workato an 8 out of 10. I believe if they offer RPA capabilities, it will become a Swiss army knife to solve all automation use cases.

Work on the process, data quality, and then focus on the automation.

I have been using Workato for the past two years now. Our current project was doing automation earlier with workflows using MuleSoft. These have now been moved to Workato for integrating systems for B2B. I work with the HR team here. We are trying to automate reports and integrations with HR vendors external to the organization, wherein we are sending files and reports, generating reports for our internal stakeholders, using the data we get from those external vendors.

Currently, I am not using the real-time data synchronization feature. We are mostly working on the files that we gather.

I use the pre-built connectors, such as SuccessFactors, which we are integrating. There are other systems which we are integrating. We have SAP HANA as well as ECC in the current environment, which is being migrated to HANA. We have several projects on HANA as well as on ECC that we are integrating. For HR, it is mainly SuccessFactors and ADP.

We started working on it from past few years, but its approach is different from MuleSoft, where we have multiple layers to do similar things. In Workato, we try to reduce it as much as possible because the services are task-based.

The best features I appreciate about Workato are how intuitive it is, its low-code, no-code feature, and its true cloud-native environment where we don't need to worry about infrastructure settings and fine-tuning. Though I find the task-based usage in Workato challenging, requiring careful workflow design.

The benefits from using Workato include automating workflows using the low-code approach, demonstrating while creating workflows, and making changes on the go. These capabilities enable faster delivery compared to our earlier work environments when using hybrid integration platform or MuleSoft. The delivery time has drastically improved using Workato because of its low-code feature and pre-built connectors which are very easy to use compared to MuleSoft. The ease of deployment is a distinct feature when compared to Tipco, MuleSoft, or any other integration tool.

The delivery time is drastically reduced, allowing changes to be made immediately and demonstrated.

I am currently in the exploratory phase. While the cloud-native aspect is beneficial, having deployment options similar to MuleSoft would be a great additional feature. Their approach aims to remove complexity from development. However, in situations with banking clients or others who prefer keeping functionalities at their own data center, having a mechanism to provide deployment options for private data centers would be beneficial.

I have been using Workato for the past two years now.

I have never faced any issues while deploying.

I have a positive impression of Workato's stability. We haven't experienced any issues so far, and everything is working great.

I have a positive impression of Workato's scalability.

I have not contacted their support team until now. We have been using the pre-built connectors. We will be working on some SDK features as we are trying to explore that. We have a few vendors we are trying to connect and build custom connectors with.

Neutral

We are customers, not a partner. On a scale of 1-10, this solution rates a 7.

Positive

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.