Made me love programming again
March 07, 2019
Made me love programming again
Score 10 out of 10
Vetted Review
Verified User
Overall Satisfaction with Workato
We use Workato mainly as a way to integrate the different systems we have. Our strategy is based on finding the best possible solution for every problem or area we have, then integrate them. Examples of these problems are the billing process where taking hours logged in different applications (such as Jira, Daptiv, Harvest, etc.) and converting them into invoices, can take the information from Project Management, Accounts and Finance. Another example is to have information flowing to the right person at the right time, like identifying the problems we have in our processes and automating reminders or actions requests using Workato and Slack.
- No code builds of integration processes.
- Customer technical support.
- Extending their connectors through SDKs
- Debugging a recipe can be painful. I have spent a lot of hours with customer support helping me and teaching me how to debug the recipes, but I think they could do a better job by coming up with some kind of debugging feature.
- We reduced invoice errors to almost 0% in a few months.
- We created conversations using Slack and Workato to smooth processes and act when it is necessary, and requests actions to the right people at the right time to reduce errors and increase efficiency.
- We integrated with on-premise resources to leverage our own infrastructure.
- We might have another revenue generation possibility offering the implementation services of Workato to some of our clients.
From what I could see, Zapier was very limited against what Workato was offering. The model of Zapier, at first sight, was very easy to understand: you pick 2 connectors and create a process in the middle, but that's where Workato made the difference, on how easy the recipe building can be and how complex can it get as well (for example, by creating a step that executes Ruby code).