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.

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.