Workato: Powerful Tool Backed by Great Support
What do you like best about the product?
What I appreciate most about Workato is its intuitive low-code/no-code interface, which makes it easy to build complex automations across systems—accessible even to non-developers. The platform’s extensive library of pre-built connectors and recipes significantly reduces development time. Features like real-time monitoring, versioning, and robust error-handling contribute to workflow stability and transparency. Additionally, their customer support is responsive and helpful, further enhancing the overall user experience.
What do you dislike about the product?
While Workato is a robust automation platform, there are several areas where it could be improved. The error messages tend to be overly generic, which can make troubleshooting more challenging. Additionally, the visual interface becomes cluttered with larger workflows, impacting maintainability. Enhancements such as more granular version control and detailed logging would significantly improve the developer experience.
What problems is the product solving and how is that benefiting you?
Workato is helping us address the challenge of connecting disparate systems and automating repetitive, manual tasks across departments. By streamlining processes like user onboarding and offboarding, license provisioning, and data synchronization between platforms such as Azure AD, ServiceNow, and internal tools, it significantly reduces turnaround time and minimizes human error. This leads to improved operational efficiency and enables teams to focus on higher-value initiatives rather than routine maintenance. The centralized platform and low-code interface also empower non-technical users to build and manage automations independently, reducing reliance on engineering resources.
Flexible and powerful integration platform for scaling automation
What do you like best about the product?
Workato makes it easy to connect our core systems without heavy custom development. The pre-built connectors, especially for Salesforce, other SaaS apps, and the on-prem connector save us huge amounts of time. I also appreciate the intuitive recipe-building interface, which lets both technical and business users design automations. The platform scales well—from simple notifications to complex, multi-step integrations with error handling and approvals.
What do you dislike about the product?
The learning curve can be real, especially for the connector SDK. Some advanced features require digging into documentation, and pricing can add up if you’re running very high volumes.
What problems is the product solving and how is that benefiting you?
We use Workato to automate contract and data flows between our platform and our clients' source systems. Workato reduces our build times, and shifts the majority of work from Engineering to high-performing backend configuration resources.
Workato recipes automate the end-to-end process—from fetching client data to transforming and pushing it into our environment—helping us onboard clients faster and deliver consistent data ingestion without relying on manual workflows.
Enhance workflow efficiency with flexibility but load management needs improvement
What is our primary use case?
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.
What is most valuable?
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.
What needs improvement?
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.
For how long have I used the solution?
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.
What was my experience with deployment of the solution?
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.
What do I think about the stability of the solution?
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.
What do I think about the scalability of the solution?
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.
How are customer service and support?
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.
How would you rate customer service and support?
Which solution did I use previously and why did I switch?
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.
What other advice do I have?
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.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Amazon Web Services (AWS)
Our apps are talking to each other thanks to Workato
What do you like best about the product?
I actually adore the way of how Workato integrates the low-code interface. It allows me to create advanced integrations between such systems as Salesforce and HubSpot without a line of code. The large and pre-packaged connectors and recipes library is awesome as well. Our marketing leads were simultaneously synced to sales almost instantly with a pre-built recipe. Also the well-designed error handling and monitoring dashboards provide us comfort that everything is going on.
What do you dislike about the product?
At times the pricing may seem somewhat high particularly to small companies just beginning. An interface is quite easy to use, although it requires certain time to learn some of the advanced features and expressions. Even their useful tools do not allow us to debug overly complicated recipes easily. Everything is not always a pure no-code experience.
What problems is the product solving and how is that benefiting you?
Workato even did what we had thought was an impossible task and tackled our enormous issue of having discreet systems and manual data entry. In the past, we wasted time resolving several hours in a week trying to manually transfer customer data between our billing system, HubSpot and Salesforce. This resulted in failure to meet the demand and annoying mistakes and inaccurate information to our sales and support teams. Workato now automates all that data flow and works in the background. We have accurate information in real time in our teams which gives them time to concentrate in interacting with the customers. It has seriously enhanced our data integrity and efficiency.
Powerful and Easy-to-Use Integration Platform with Great Support
What do you like best about the product?
Workato is extremely easy to use, even for those new to automation platforms. I completed my training and created my first recipe within a week. Now, we have around 20 recipes running successfully. The training courses are well-structured and helpful for onboarding.
One of the best aspects is the dedicated support—we can directly connect with Workato's team whenever needed to discuss the best way to implement our requirements. As a B2B SaaS company, our customers use the Workato connector daily. We’ve implemented event triggers to push data to their CRMs or fetch from specific sources.
Workato offers a wide range of features—we’re currently using connectors, triggers, and events effectively. Integration is also seamless. We have multiple recipes tailored for different use cases, and it takes minimal input to build, test, and deploy new recipes end to end.
What do you dislike about the product?
One limitation is the lack of an API to automatically refresh recipes when there are changes. If something breaks in a new version, Workato rolls back to the previous one, but without much visibility into what went wrong.
Additionally, I find it difficult to monitor connector status—there's no clear way to check if a connector is live and functioning properly. Having better operational insight would make troubleshooting easier.
What problems is the product solving and how is that benefiting you?
We’re using Workato both as an iPaaS and an embedded integration platform. Our end users are business users who want to move data between their internal systems and our platform on demand, while also keeping their own systems up to date in real time.
Workato solves a major problem for us: we don’t need to build and maintain custom connectors for every integration request. Instead, we create reusable recipes in Workato, which our users can plug into. This significantly reduces our development effort and time-to-market.
It also handles authentication, data security, and gives visibility into events and job runs, which helps us support and troubleshoot more efficiently. Overall, Workato lets us offer flexible, secure, and scalable integrations to our customers without overloading our engineering team.
Assistance on Certiification
What do you like best about the product?
Its low code no code automation tool which has build ai
What do you dislike about the product?
Call assistance for the Support team it would be great if we had
What problems is the product solving and how is that benefiting you?
It is helpful for OPTIMIZING and integrations automations with low code and no code
Workato tool review
What do you like best about the product?
Workato is a very comprehensive tool and has many useful features. They support is quick to react, not afraid to jump to a quick call and the chatbot are often helpful as well.
What do you dislike about the product?
The AI Copilot implementation while still in beta still needs some work, it seems to work worse than the actual chatbot AI.
The main thing that I am missing in workato is easier log inspection. Right now if you are using For each loops it is hard to see all the information that it goes through.
What problems is the product solving and how is that benefiting you?
Workato is an automation tool and there are many tools that can make automations in a low code/no code format, however workato has a lot of governance features that allow to distribute it on a wider scope in the organisation.
Data processing efficiency increases with workflow automation but could improve on handling high volume data
What is our primary use case?
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.
What is most valuable?
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.
What needs improvement?
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.
For how long have I used the solution?
I have been currently using Workato and implementing the solution for the clients for more than 3.5 years.
What do I think about the stability of the solution?
Workato is quite stable, and they are continuously improving the product's stability by implementing various connectors that are already available.
What do I think about the scalability of the solution?
I am not sure about Workato's scalability, as that falls under the Workato team's expertise. We focus solely on implementation.
How are customer service and support?
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.
How would you rate customer service and support?
How was the initial setup?
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.
What other advice do I have?
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.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Amazon Web Services (AWS)
Workato offers cost-efficient integration and ease of training
What is our primary use case?
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.
What is most valuable?
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.
What needs improvement?
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.
For how long have I used the solution?
I have been working with Workato for five years.
What do I think about the stability of the solution?
I have observed some minor stability issues with Workato, particularly related to connectors failing occasionally and delays in report sending.
What do I think about the scalability of the solution?
Regarding scalability, I haven't experienced any issues in my past projects; I find it easy to scale up or down.
How are customer service and support?
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.
How would you rate customer service and support?
Which solution did I use previously and why did I switch?
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.
What was our ROI?
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.
What's my experience with pricing, setup cost, and licensing?
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.
Which other solutions did I evaluate?
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.
What other advice do I have?
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.
Workato Experience
What do you like best about the product?
The way we reduce the entire hassle of connecting different app by using connectors in Workato. The Customer Support is also good and they would help u with recipe ur working if u face any errors.
What do you dislike about the product?
There are many features that are hidden behind other public ones that are helpful. I think that they could also bring something that would reduce the need for AI hub inference.
What problems is the product solving and how is that benefiting you?
Workato is solving the problem of reducing huge process of connecting to different apps and also by reducing the time consuming task by using various connectors to various different tasks in the environment.