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.

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.

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.

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.

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