Workato provides an AI-powered enterprise automation platform designed to help organizations integrate applications, data, and processes. The platform supports security, governance, scalability, performance, and availability, enabling IT and business teams to connect systems and automate workflows. Users can access and adapt pre-built automation “recipes” from the Workato community to address a range of integration and process automation needs. This approach enables organizations to improve operational efficiency and utilize their data and systems more effectively.
Do You Manage Peer Insights at Workato?
Access Vendor Portal to update and manage your profile.
Ease of use, ability to work with a wide variety of endpoints and data formats, cloud interface.
Provides multiple features like API management, ELT capabilities. JSON logs are documenting every step which helps in tracking. Provides secure on-premise connectivity.
1) The recipe editor interface is perhaps my favorite thing about Workato. It makes building and testing a recipe very simple. I can have an automation running in a matter of minutes because of how intuitive the recipe editor is to use. The drag and drop nature of pills to use for input/output, the logical paths you can implement, the instant validation for missing required parameters, incorrect formula code, etc. You can build and test as you're building recipes with ease. The overall user experience inside the recipe editor is perhaps Workato's strongest flex. 2) Workato is very flexible in terms of the skills required to get effective use out of the product. Any non-development minded person can go in and create simple recipes that meaningfully move the business forward. Even for non-devs, it is simple for them to work with some of the most advanced features like Workato's Agentic AI offerings, requiring little to no code to stand up enterprise-grade LLMs. At the same time, developers will find powerful tools at their disposal to also make meaningful impacts for the business (things like API management, connector SDK, data tables, using custom Ruby/Python/JS as an action step, CI/CD, developer API, data logging, etc). So whether you're a business major fresh out of college, or a seasoned dev - Workato gives everyone the ability to make a positive impact to the org. 3) Always innovating and pushing the product (and industry) forward. As a Workato user for nearly a decade, I have seen the product undergo constant updates that have all meaningfully enhanced the product. Workato listens to its community for sought-after features. Workato's forward thinking is definitely way ahead of competitors
Terminology is sometimes confusing. Engineers seem to be a bit stubborn about adding features that might help end users (open to fixing broken things, but less so with usability issues) - for example, no easy way to test run a job. No easy way to clear job cache.
Documentation requires more improvement. Hard to use, learn and understand for non tech users. Very costly than its competitors
1) Workato can be a bit expensive to buy into for some businesses. I would love a Workato-Lite platform for my own personal use. Workato uses task-based pricing where the more actions a job takes, the higher the task-usage. As a result, I often design automations and integrations around this constraint, which works out in the end because by designing for efficiency and optimization means that the overall recipe design is better for it and it is easier to scale this way as well. 2) Governance/RBAC can be a bit of a challenge. Our organization has over 50 users within Workato, each with different security clearances, roles, departments, etc. While it is possible to segment Workato in such a way where people only see what they need to (especially by using some of their add-on offerings like Automation HQ). Maintaining strict governance across the org can be time consuming and challenging. 3) Lack of ability to implement usage limits per user/role. As mentioned in point #1, Workato uses task-based pricing. Workato is also very powerful. This can lead to a situation where a novice Workato user accidentally builds a recipe that can consume several million tasks in a matter of hours. Being able to enforce certain things like Max task limit per recipe or even an estimate on how many tasks a recipe is expected to consume on a normal run. I would like to limit certain users from using certain actions, or enforce best practices (like naming conventions) using validation rules that can be built in.