Automate® Pricing Overview

What I like best about Automate Robotic Process Automation is how easy it is to build workflows without needing to code. I’ve used it to automate repetitive tasks like report generation and data entry between Excel and our ERP system. It integrates smoothly with Outlook too, so we’ve got bots pulling attachments and filing them correctly without lifting a finger. It’s saved us a lot of manual work and reduced small errors that used to slip through. Review collected by and hosted on G2.com.

I would say what I dislike about Automate RPA is that it does not always do system updates well. Our bots stopped working a few times after an OS or app update then reconfigured parts of the workflow. Additionally, some deeper integration options between those platforms we use in the web and how far we can go with automation are also missing. At times it’s created extra work, because we wanted the bot to do the job in its entirety. Review collected by and hosted on G2.com.

It is easy to learn and begin to use. However with the later updates, it becomes increasingly more difficult to use because you have to work around issues with the web browser actions. Review collected by and hosted on G2.com.

I do not like that it does not have a cloud hosting option. It would be fantastic to give people that option if they were to want that. Also, cloud hosting makes it really easy to test out all the features. Having self-service trials on a cloud hosted version would be a lot easier for people to try it out and see how it works.

The big thing lately for us is that Automate is constantly breaking current functionality when it comes to the web browser actions. If you are not using these, you will likely love the product.. But web browser actions doing what you tell them to do is critical for our business use case

Support seemed great at first, but that was due to working with some bad vendors in the past. Now that I have taken a deep dive into support, I've learned that the customer facing support team is fantastic, but nothing seems to happen once things get escalated in terms of the bugs I'm finding. They'll make a hotfix that fixes the one singular issue that I point out, however it may or may not make it into the next release. At one point they made a hotfix and said that it was just for our company's use with the way we use Automate, even though this was in fact was a change they made that broke existing functionality of the web browser actions..

I've also accidentally been tagged in email threads for similar escalated support issues with other companies by senior staff.

Again, first line support has been great, but once a ticket gets escalated and deep in the weeds, there's not been much help other than hotfixes that do not resolve the root issue of releasing changes without properly testing that they do not break existing functionality.

Because of these issues, we have attempted to upgrade from 11.6 to 11.7 (which horribly failed and 11.7 subsequently got pulled and re-released). Then we were testing 22.1 which also got re-released as 22.1.1. Initially we could not upgrade to 22.1.1, but after rebuilding one of our big processes entirely, we were able to get it to work with 22.1.1 and work around the issues that this update has with performance on the execution server.

23.1 was a dumpster fire of broken web browser actions that I very quickly identified bugs on using public-facing websites. 24.1 fixed a few of those, but left some bugs still standing, and broke some new things with web browser actions.

In short, I've been working with Autoamte on escalated tickets for a couple years now. Half of our environment is on 22.1.1 and the other half is on 11.6 Review collected by and hosted on G2.com.