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

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

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

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

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

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

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

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

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

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

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

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

I would rate the scalability of Workato an 8.

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

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

Positive

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

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

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

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

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

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

Overall rating for Workato: 8 out of 10.

I have used Workato for almost six months in my company to integrate different platforms using this Workato tool.

The main use case of using Workato is that Workato is an integration platform, whereby if I want to integrate one platform with another, such as integrating SAP with Freshworks, I have to use Workato as a tool to integrate these two platforms with each other.

The process of integrating SAP with Freshworks using Workato is pretty straightforward, and I really appreciate Workato in terms of integration because it is very simple and user-friendly when it comes to coding, and most of the part is a non-coding part. When there is complexity in functionality for one system, we have to do the coding on Ruby, which is also a fun part. I have used many integration tools other than Workato, and I find Workato quite easy to understand and fast compared to Integration Hub of ServiceNow, which is quite detailed and a little complex. Therefore, I found Workato easy and the speed is quite good.

The best feature of Workato is the ability to create a flow, and the majority of the things are already available in the module, which I find valuable. Additionally, if we have a demand for a specific tool, we can connect with the support team, and they can provide us what we need. Another valuable aspect is that there are many things publicly present in their library to use, and if I need to create an integration for a particular system to another, there might already be something available created by other users in public repositories.

The public repository helps me significantly because when I know the PRD document of the customer and understand their use case, I can look first in the public repository for something similar instead of creating everything myself, thereby saving my time. If I find something similar, I can take it as an example, utilize it in my personal flow, reduce my work on that particular task, and incorporate that chunk of flow into my own flow. Hence, the presence of numerous flows in public repositories is quite helpful.

Workato has positively impacted my organization, depending upon the customer's preference for which tool to use. While some customers prefer Workato due to its good customer support, it's ultimately based on the customer's needs, and we can perform integration using various tools available in the market. Personally, I enjoy using Workato, and my company feels that it results in significant time savings since it is easy to understand and allows new team members to onboard quickly. My superiors appreciate it as it enhances speed and accuracy, allowing QEs to understand and test completed tasks easily.

The positive impact on my team's speed and accuracy is evident whenever we start a new project, as new team members face challenges understanding how we use Workato. However, the best thing about Workato is the amazing and detailed documentation available on their website, which makes understanding and using the tool easy and fast. Even individuals without a coding background can contribute to projects quickly, as we have had freshers join with limited exposure to coding who can still catch up and integrate with projects swiftly.

Regarding improvements for Workato, there was an incident when we wanted a specific feature implemented, and the process was quite lengthy as we had to raise a ticket, track the ticket, and wait for the team to address it. Given the millions of users of Workato, when a customer has a specific requirement, it reflects a possible shortcoming in team resources. However, it's understandable given the high volume of tickets, and I believe Workato may be working on this aspect by leveraging AI tools in the future, which points to this being more of a manpower issue than a critical flaw.

I believe the process is already efficient, and I don't think I'm in a place to suggest improvements since I find Workato very amazing and well-kept.

I have been working in my current field for over one year and nine months, approximately.

We have never faced reliability or downtime issues with Workato; it is very stable.

Workato is very scalable, and we can scale any project using it, so scalability is not an issue.

I would say customer support is good, but I cannot classify it as very good as my personal experience varies.

Neutral

I have used multiple tools for the same integration before Workato, but it was not a personal choice; it was driven by my organization's requirements based on customer needs. I prefer using Workato because it's user-friendly while other tools tend to have much complexity due to being very detailed integration tools suited for large systems Oracle and SAP. Each tool has its own strengths and weaknesses, depending on the customer's requirements and our development needs.

I have definitely seen a return on investment from using Workato, notably in time saved and the reduced need for employees since it requires less time to understand and a handful of people can manage much larger integrations with this tool compared to others.

My advice for others looking into using Workato is to thoroughly review the Workato documentation, as it is very detailed, good, and easy to understand.

I think we have covered almost everything regarding Workato.

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