UiPath Reviews

We had two distinct automation needs. First, we aimed to simplify the process of obtaining weekly updates on new employees. This involved automating navigating a portal, identifying new employees, and distinguishing between contractors and full-time employees and aims to streamline maintaining an accurate and current employee database for your company. 

The second use case focused on case number categorization. We needed to categorize cases originating from sources like SSM, DC Salesforce, and others into different categories, such as origin-related or finance-related, to prioritize and address them based on their urgency and type.

It offers an advanced and in-depth set of features, allowing for intricate and specific automation tasks. It is designed for a more user-friendly and localized experience, catering to individuals who aren't necessarily focused on development. 

The ease of use in both running and developing automation bots is a key factor for us. We also measure customer satisfaction not only in monetary terms but also in terms of the hours saved. For example, if we can save ten thousand hours in a year, it's a substantial achievement because it translates into cost savings for the organization. Ultimately, the hours saved through automation equate to tangible financial benefits.

The concept of process analysis would be helpful. Having a tool that can assess the entire workflow of an automation created by someone would be highly beneficial. This tool could identify areas where enhancements or improvements are feasible, simplifying the process of refining and optimizing automation workflows. In the case of case number categorization, we encountered an issue. While creating the automation, the system was designed to detect and categorize cases into various specified categories.

I have been using UiPath for a year and a half.

The performance of the automation largely depends on the developers and the environment. For unattended automation, ongoing monitoring is necessary, especially when your team is actively making changes to the interface of the platform or system you're automating.

It is highly scalable as it can be deployed to handle large datasets and execute numerous processes concurrently. This scalability enhances its efficiency and productivity, making it a valuable tool.

My company made the decision to opt for UiPath over other vendors approximately five to six years ago. The primary reason for this choice was its superior technology and the seamless integration it offered for running our processes.

The initial setup was straightforward.

It doesn't have many direct competitors that offer a comparable blend of advanced automation features and competitive pricing. What sets them apart is their commitment to continuous improvement and innovation, evident in their advertising and technology enhancements. 

Overall, I would rate UiPath nine out of ten.

We automate business processes that take up a lot of effort and manhours. Our company deals with a lot of documents. 

The most valuable feature is Task Capture. 

We work with Google Cloud and are excited about the possibility of a partnership. 

I have been using the product for six months. 

The tool is very stable. The product's stability depends on the processes you configure it with. 

UiPath's scalability is impressive. 

UiPath's support is great. 

Positive

The tool's deployment was straightforward. There were a few inefficiencies within my company. 

We currently have the tool deployed across different business lines suffering from silos. In the future, we may move towards a centralized structure. 

We have seen ROI with the product's use. 

We want to reduce our employees' demand hours and have them focus on high-value tasks. 

UiPath has fundamentally changed our organization, and we want to learn more about its capabilities. 

The tool has freed up our resources' time. 

I rate the product a ten out of ten. I like working with the software. It might be daunting to start automation and get employees to accept it. However, having a good rollout plan and strategy will ease your concerns. 

We use the solution to automate our processes. 

The tool's most valuable feature is its embedded activities. 

UiPath needs to be easier to use. 

I have been using the product for two years. 

I rate UiPath's stability a nine out of ten. 

I rate the solution's scalability a nine out of ten. 

The tool's tech support is good. 

Positive

I have used Blue Prism before. 

The tool's deployment was easy. 

A consultant helped us with the tool's deployment. 

We have seen ROI with UiPath's use. 

The tool's pricing is fairly reasonable. 

We wanted to minimize manual work so that our employees could utilize their time efficiently. 

The solution has helped us save employees' time and money. 

I rate the product a nine out of ten. You should utilize the training, practice exams, and all other information in UiPath. 

Our company uses the solution to understand documents, process invoices, move data from one system to another, conduct background investigations, and other day-to-day use cases for federal and state offices. 

For one use case, we built a sandbox for malware analysis using the bot. 

For another use case, we scan thousands of resumes to find an individual with a specific skill set. 

We have completed 90 automations with mostly attended bots that we have built. We are not using AI much right now, but plan to use it to solve problems in the future. 

The solution can be used across systems or with more generic use cases. 

It is easy to go to the code level and write automations that only require a couple of lines of code.

Training materials should include behind-the-scenes information such as what goes on underneath the infrastructure and how components interact with each other. This type of information matters more to solution architects than high-level buildings or components. 

The solution has a few bugs that need to be worked out. 

I have been using the solution for three years. 

The stability has been good so far but we do not have much volume. We handle diverse implementations that include five to ten bots. We do not yet have the load to fully rate performance. 

The solution is a good platform for scalability and accommodates multiple nodes. 

Technical support has been pretty good and we have a direct contact who is very responsive. It sometimes takes a day or two to make contact, so technical support is rated a nine out of ten because there is room for improvement. 

The user community is helpful and it is easy to find answers or at least a direction for solving issues. 

Our team utilizes the Academy for certifications and finds it useful because it provides high-level information about features. 

Positive

We did not use another solution. 

The setup is cumbersome for on-premises because documentation is outdated or instructions are not clear so we have to get clarity from support. 

The setup for SaaS is easy because you can log in and start using it immediately. 

We implement the solution in-house using a hybrid model. Some federal government offices are very particular about exposed data so we use on-premises for them. Others are more open so we prefer to use the SaaS platform. 

We also work with many business groups to promote RPA and set up their infrastructure environments in the solution. 

The solution's ROI is that it saves time, eliminates errors, and reduces repetition. Tasks that used to take days are now completed within seconds or hours. 

The solution is more expensive than Power Platform which offers many connectors to third parties. 

For example, an unattended bot costs $50 per month on Power Platform so it makes sense for developers who work on the Microsoft Platform. 

The solution can run $10,000 per year. 

Prior to using the solution, we looked at Automation Anywhere but did not enjoy developing with it.

Many other products such as ServiceNow, Pega, or SAP have RPA but use their own domains. They also require many blocks of code to automate. 

We will be looking at Power Platform's next iteration because we are not sure about the future of the solution's partnership with Microsoft. 

When implementing the solution, go small first. Do not jump directly to the most complex case for automation or you will get lost and think the solution is ineffective. 

Start by building small workflows, realizing the gains, and slowly increasing performance. 

I rate the solution an eight out of ten. 

We use it for the automation of internal HR processes in our company.

It helps with the ease of implementing new logic from business requirements, which very rapidly change.

UiPath has also helped because fewer people are engaged in the processes we automate, and they can do more important things. It saves our staff time, on the order of 80 percent. In terms of employee satisfaction, I don't really know how they feel, because they are not in my department, but I believe that when you don't have to do such routine, repetitive work, you can have a coffee and come up with ideas on how to improve the automations. That is, by far, better than clicking and typing thousands of forms.

Also, there is less chance of a person making a mistake. If a given operation would take one person, for example, two days to do, the automation can do it in one hour, or even 30 minutes. It is very useful. We saw benefits with the first automation that was implemented, because it started to work and free people from routine work, within the first second of the automation working.

We have a lot of automations that involve filling forms on the internet and creating events in a calendar. There are a lot of fields to fill out. When creating these meetings, you have to add a description and pick the actual time. All this stuff should be done precisely, because if there is a mistake, somebody will not come to this meeting, or the information will not be applicable. Now the number of errors is zero because robots don't make mistakes.

We also don't need to involve the IT department, and we now have 15 automations. The group of people who implement it do the maintenance as well. We don't need IT and, actually, everything works fine without any maintenance. The problems come when there are updates, but the time needed for maintenance is very small.

Because we don't need to create virtual machines to install the solution on-premises, the cost is as little as it can be. Of course, we have to create several virtual machines for actual clicking, because the robot works the way a human does. But it has definitely helped with our on-prem footprint because we don't have to install the core of the system on-premises. I know, from my experience, that those kinds of core components take a lot of hardware resources. They would not require just one virtual machine; it would be a bunch of virtual machines. It is definitely very efficient to use the cloud solution from UiPath.

UiPath reduces costs because it reduces the time it takes to create automations. You don't have to write the actual code. You just build automations with higher levels of abstraction and you don't have to worry about what is done behind the curtains.

The best part is the way UiPath provides the ability to automate everything, including the architecture and Orchestrator. The interfaces are very user-friendly and intuitive. It's very easy to build automations. Someone who is not very technical can understand quite a lot and start to automate.

All automations are built starting with process analysis, then robot building, and monitoring. One person can gather the requirements, build the automation, and monitor it. This end-to-end coverage is very important. I can't even imagine how it would work if not in this way. This is the essential part of the automation: the idea, the implementation, and the maintenance.

UiPath's approach allows adding new workers, new agents, or robots to perform quicker and in parallel. For example, if you create two extra virtual machines with two extra robots, a whole bunch of operations will be performed three times faster. This kind of implementation is very convenient. And, we can change the way automations are deployed in Orchestrator and make it more efficient as well. We can do all these kinds of things really easily and quickly, like in minutes or less than an hour. That helps to scale things. You can change something in an automation in several minutes and deploy it or publish it in Orchestrator, and it already works. The challenge of implementing innovation can be addressed very quickly and very efficiently. The challenge is that we have to change our automations because other applications change with time. They have new user interfaces. But we don't need to upgrade anything to automate.

Several of our team members are studying the UiPath Academy courses at this moment. It has definitely helped because they get to know about new features that make automations more mature. One of my colleagues said, "As I read and study more in this course, I begin thinking more creatively and in more interesting ways." That means their understanding is growing and that it is changing their perceptions of what they can do with UiPath.

The information in the Academy is structured, starting with simpler concepts and moving to more advanced levels of knowledge, gradually. Also, you really learn about things you haven't used before. Thirdly, it leads you to the certification exam and getting the certificate on passing this exam. That makes you a good candidate for better jobs.

UiPath also has a very nice community of developers. When I face problems that I can't resolve by myself after several hours, I Google it in the UiPath Community and almost every problem can be solved by searching their resources. I work with different vendors and not all of them have such a big and open community. This is a real advantage. I'm not very familiar with other communities in RPA, but I can say that this community is, by far, more useful and more open than any other vendor's community I have seen.

I faced a problem when a new version of UiPath Studio didn't work with an older version of the packages that were part of our project. The problem is that when I have to change something just a bit, I actually have to rebuild the automation with new versions of these libraries. There is no backward compatibility. 

This question was addressed to an engineer from UiPath in the Community but I haven't gotten an answer. This is quite a hard question. So, I just create new automations with new approaches, which takes some time.

I have been using UiPath for about eight months.

The solution is very stable compared to other enterprise tools. Even if there is an error, if you handle it properly, everything works perfectly. From the point of view of UiPath developers, everything is done on a very high level.

It is scalable. However, to see the scalability you have to use the Enterprise Edition, because the Community Edition doesn't allow you to use more than one robot. But the mathematics are very easy: The more robots you have, the faster everything happens.

The number of automations will grow in our company.

I haven't used their technical support.

The initial setup was easy. It took a few hours.

We are using the Community Edition. The cost is only that of the virtual machines.

The pricing of the Enterprise Edition is a bit high. It's several thousand dollars a month. That's too much, because not every enterprise or organization can build such useful robots that will make it worthwhile for them to pay this much. Maybe the cost of the program could depend on the number of automations, or the complexity of the automations.

The solution is cloud-based, but you have to have some components deployed on the local computers. That is the architecture of UiPath, but the base of the infrastructure is in the cloud.

My advice is to just implement and begin automating. You don't have to even learn something before it, because everything is very intuitive.

We have a variety of projects we use it for. We have automated about 72 processes within six verticals, including sales, finance, HR, and purchasing.

It has helped our client save thousands of dollars, for sure. That is really what they have found to be the biggest benefit of using UiPath. The cost of the product is low because they're using it continuously. It saves cost and it helps them gain more returns.

Our main projects are mostly around SAP and Excel. We have used most of the features available, especially the ones that support SAP and Excel activities. Those are the ones that we have found to be most useful.

UiPath is easy to use and there is less coding. That is very helpful for the development team when it comes to building projects. It's very flexible and really makes our team more efficient. The turnaround time of development is good. 

There is some scope for improvement, especially in the area of variables. Some variables are used in specific workflows and some variables are global. It would help if there was a repository that would showcase which variable is global and which is local to a workflow.

UiPath should also help us whenever we are changing versions. Whenever we make those changes, UiPath should help by documenting the versions and sending us comments on the changes made in UiPath. If that were available, that would really help.

I would also like to see something related to auditing. That would really help the development and peer review teams to identify the gaps, instead of going through the sequence one by one. If there were an auditing tool that clearly brings out issues, that would really help.

We have been using UiPath for four years.

UiPath is a stable solution.

They are plugging in a lot of features that are really helping our teams. It is scalable.

For this year, we don't have plans to increase our usage of the solution, but it depends on our client.

The technical support is good and they respond to us all the time. Whenever we require support, they are with us.

They have a standard questionnaire that we have to complete and send in, and they come back with standard responses. At critical times, instead of the standard response, if they could do a direct call that would really help us. Instead of one or two levels of questionnaires, if they could directly get on a call, that would help us. Hence I rate them eight out of 10.

Positive

I was not part of the initial setup, but I am involved in the renewals.

The renewals could be easier. The documentation is lacking. When you are renewing your licenses, you might encounter errors but there are no proper documents available to explain how to handle these errors.

In terms of maintenance, our automation processes require some attention but UiPath, as an application, does not, other than updates.

There is ROI over a period of years. From the second year onward, it would be around 25 to 30 percent.

The pricing and licensing are okay. It's quite affordable.

There are a few things that come with additional cost. They are mostly features. For example, Document Understanding is an additional feature that you have to pay extra for.

I would recommend it to new users who are choosing among automation tools. 

Also, if a company is new to it or the users who are setting up are new to it, they should be aware of the preparations involved in setting up the environment and setting up UiPath. That can be a little challenging if they are not aware of certain things.

I rate UiPath at eight out of 10. There are a few features or approaches they could enhance, such as an option to view all the variables, as I mentioned earlier. Also, since the code can be very big, we might be searching for certain things that are not available. I'm more concerned about the debugging and evaluation parts. 

And in Orchestrator there are a lot of features they can enhance.

We suggested UiPath for one of our company's clients to automate DevOps processes. This is a part the company doesn't want to touch. They tried automating with Ansible Playbook and Terraform. We wanted to eliminate human intervention altogether. We are still transitioning from dev to staging and then production. We have done most of the research. We will move from staging to production if it works with our architecture and can be scaled.

Our client is one of the biggest companies out there. There are maybe a million users worldwide. They primarily focus on the Asia-Pacific region, but there are also users in Europe and the Americas. The client has several web applications and a hybrid structure. Some data are on the cloud, while other data is on the on-premise servers. We created solutions for them over the years. We have an SI and DevOps team working in parallel for years. Our goal was to automate everything that could happen without intervention. 

It's a massive project that will take time, and we still haven't moved out of development. We try to make the processes more streamlined. All the associates are researching it and working on their parts. Right now, I can only say how it has benefited me. I've automated some fundamental DevOps tasks. 

It saves a lot of time because you don't have to come in on weekends to provide service or troubleshoot. You can automate these tasks and schedule them to run automatically. You can optimize your work and how you spend your time. For example, some services need to be routinely patched, so we automated patching every third Sunday. However, we still needed to come in on weekends to troubleshoot after the patch was applied. 

We have shadow scripting to automate these processes, but we had to go online to see if it's up and the ports are open. I automated this with UiPath and scheduled it for the weekend, so I no longer need to come in on weekends. It saves around two to four hours per week. That is about 16 hours a month. It wasn't easy in the early stages. It took around two months to understand the tool. I was also working on other projects simultaneously.

There is a recording feature that copies each step of a task. You can automate every process via this recording. It's a cool feature that helps you define the variables. I also like their trial version, which lets you experiment with the solution and learn the capabilities before buying the license.

I still haven't used the drag-and-drop APIs, but I look forward to this feature. We currently use Jenkins for our continuous integration tools. There are some APIs from Jenkins, and we extract the job details from those APIs.

UiPath's interface and user experience could be improved. The name is UiPath, but their UI is not that great. It's outdated. It seems like a 2014 or 2015 software. They should look at other products on the market.

Another thing is that UiPath lacks online training resources. Maybe they can start their own YouTube channel. You have to rely on the documentation to learn. There are some resources, but they aren't available on the official site.

We have been using UiPath for six months.

UiPath is quite stable. I haven't seen any downtime. I can also pause the upgrade itself if I don't want the upgrades to cause instability. The long-term version is available as well.

We are still in the development stage, so we don't know whether it will be scalable. 

I have never had a need to contact UiPath support. I usually try to Google answers or figure the issues out on my own. 

I am from the build release team, so I automate the deployment and build process. I work on CI/CDs and try to automate most things. The deployment was highly complex. I was new to this project, so it was challenging for me. I was learning on the job and trying to understand the process itself because it was already partially built when I joined, and I was responsible for making some of it. 

The application takes about 10 to 20 seconds to install, but it will take around a week to build the infrastructure. We are just replacing the web service, not the whole application.

We tried a blue-green strategy for implementation. We built blue nodes and ports similar to production and shifted the web services to the new one. If it is up and running and everything works fine, then we can close the previous one, and we can redirect traffic to the new one with the help of load balancers.

We have 25 people on our DevOps team who do everything from architecture to automation. They're not just dealing with one web application. There are hundreds of applications. I worked on several applications building the architecture and helping. For example, let's say we build or add some features to a project. To automate those features, we need to understand them and how it works on Kubernetes or other platforms.

It definitely needs maintenance because we deal with a large user base. It requires a lot of maintenance and downtime to make things work during staging and development. Maintenance is always necessary, and we are the ones who maintain it. We have four or five people on call weekly to maintain the solution. They are the responsible people or points of contact for the developers or application owners if something goes down or goes wrong.

UiPath's price is reasonable. It's not so high relative to the capabilities. I don't know about different licenses or more premium versions. Prices are negotiated on the corporate level. 

We considered Automation Anywhere. However, It doesn't allow for an extended trial. We needed to purchase a license after 50 tasks, and we didn't have enough budget to experiment. Blue Prism is also there. We had the same problem. There wasn't a trial version.

I rate UiPath eight out of ten. UiPath has excellent features, but you need to be patient enough to learn.

UiPath offers direct integrations with multiple platforms that we need, like Google Drive, Slack, Visio, etc. For Slack, UiPath automates the process when we upload a new file, document, or a new version of it. It automatically sends an email or any other sources that we automate through it. That is our main use case.

We upload a lot of content for our website or internal work on Google Drive. When a team member uploads content, we do not get a notification from Google Drive that a document has been uploaded by someone unless they share it. With UiPath, we have automated it so if someone uploads a document in a Google Drive folder, we get an email on a certain email address that a document has been uploaded. Or, when there is a version change, we also get an email. So, we have automated these kinds of processes using UiPath.

It is mainly the automation process for internal tasks. All our direct integrations are for internal work, mainly email triggers that we built using UiPath. These are very useful.

The direct integrations are most valuable. You can directly link your account to multiple platforms, such as Google Drive and Visio, without using an API.

We have used the Orchestrator's trigger creation workflow to create multiple triggers for our automation processes.

It could be improved with tutorials or documentation-wise. Some of the features of the artificial intelligence or Orchestrator have been a little confusing for me. So, I would like an easy YouTube video tutorial or quick demo call. It would be much better for every user if they could introduce that.

Around six to seven months ago, I started using UiPath.

UiPath has always been up so stability is not a problem.

It is really scalable, even for large businesses. We are pretty small, but as you grow, UiPath has great options for scaling up.

We currently have two people using it: the co-founder and me.

I haven't needed to contact their support yet.

We previously used basic process automation platforms.

We switched to UiPath because it offered better features that we needed. For example, its direct integrations are pretty useful. It has every integration that we directly need so we don't need to use APIs or code anything. It is simple and direct. That is the main reason that we use UiPath.

It was straightforward from the process of registering your account to creating an organization, then doing the integrations. The process was really easy and did not take too much time the first time. I think it took us an hour to deploy.

We are on the Community plan, so it has great return on investment.

UiPath has saved our staff time. Using the automation of UiPath, it triggers an email or notification for a process that we have created. This keeps us informed at all times. However, if we don't use it, content may get missed and we would lose a lot of opportunities.

The pricing is good. They offer a Community edition that we currently use, which is free. Their paid pricing is pretty affordable for businesses as well.

I went to review websites and saw that UiPath is great.

In case you are not going to drag and drop APIs, they should definitely go and have a look at direct integration. 

I would rate the solution as nine out of 10.