UiPath Reviews

We use UiPath to automate simple, everyday processes like email automation.

We have deployed UiPath both on-premises and in the cloud.

Using UiPath to build automation is easy compared to the other automation solutions I have used.

UiPath enables us to implement end-to-end automation, which is important because it helps us eliminate human errors.

The UiPath User Community is good.

The UiPath Academy courses are helpful, and all of our team members use them. We have learned a lot about UiPath from the courses.

UiPath helped to speed up our digital transformation and reduce the cost of doing so. We did not require any expensive or complex application upgrades or IT application support to speed up our digital transformation.

We have repeatedly tested our processes with humans and with UiPath. We consistently achieve better results with UiPath because it eliminates the possibility of human error in our reports.

UiPath saves our staff time by reducing the manual tasks.

UiPath has saved us money by eliminating the need for a person to perform repetitive daily tasks.

The ease of automation using UiPath is valuable.

UiPath should add support for more programming languages, such as Python, in addition to VBScript, to help developers with their coding.

I have been using UiPath for just over one year.

UiPath does sometimes go down, but compared to other automation tools I have used, it is more stable.

The technical support is good. I received a response within one day the last time I contacted them.

Positive

I have used Automation Anywhere for some projects, but UiPath is far better because of its easy-to-access and informative User Community.

The initial deployment is straightforward. All we have to do is publish and grab the data linked to the orchestrator. One person is required for the deployment.

The implementation was completed in-house.

The price is a bit high, but UiPath is worth the cost, given its ease of use and features. We sometimes use Automation Anywhere instead of UiPath to save costs, but UiPath is our preferred choice.

I would rate UiPath nine out of ten.

No real maintenance is required for UiPath.

UiPath is easy to use and automates well. It is also good at identifying errors compared to other solutions.

We use UiPath in all business areas like finance, HR, accounts payable, production,  etc. 

UiPath's entire package is valuable. It is a user-friendly solution. 

UiPath needs to incorporate French and Portuguese language-based training. It is not easy for people without an IT background. 

I have been using the product for four years. 

UiPath is stable. 

We have rolled out about 20 citizen development programs. We aim to reach 100 by the year's end. We use it all over the world. It is scalable. 

We chose UiPath because it is easy to expand the benefits program. 

The tool's deployment is time-consuming. 

UiPath is expensive. 

We implemented UiPath to increase quality and take away repetitive tasks from employees so that they could focus more. It helped us to cut down on time. 

The tool has helped us save a few minutes of employees' time. 

I rate it an eight out of ten. 

We are primarily using the solution to automate manual processes for users. The solution helps reduce their efforts. We connect it to databases and do web automation.

The solution has helped us to reduce costs and lessened manual effort. We've been able to cut back on employee costs by reducing human interventions. 

The automation is very good. I like that I can connect various databases and our framework templates. It is effective for building automation.

The orchestrator functionality is good.

We've found the solution offers good cost savings. It reduces the need for human effort. It can cut down the costs of an entire unit via automation. Automating the process has been quite effective. When humans are involved, it sometimes can take days and now we can get those tasks down to a few minutes. By reducing the time it takes to resolve problems, our customers are happier. 

It has helped us implement end-to-end automation. It's very important for us. It really helps us in the current market and will help us save on future costs.

We have user forums if we have any issues. We can always post questions there. We also have a Community Enterprise Edition that helps practice and gain certifications. It helps us to gain experience with UiPath.

It can do whatever a human can do and mimic their actions.

I've used the Academy classes. There are UiPath docs, and you can go through the material, however, the courses are helpful for learning. We can go through tutorials to learn how to build a use case or sequence by ourselves. It gives us use cases to build on our own. It's really helpful that we can go ahead and mimic their steps and create our own work.

The solution reduces the cost of digital transformation. Even if the processes are complex, we can manage it. Once we understand a process, and we are able to build something end-to-end, it helps digitize processes, which translates to benefits and cost savings. 

We've been able to reduce human error. My process is very complex. Even an expert may not be able to do the process I am automating. I'm talking about 100 to 200 steps. That's a lot of places to introduce human error if you don't have automation. 

It's freed up human time.

UiPath has helped save costs. The clients have been happy with the results. 

The issue we have is around security and internal policies. If I want to update a queue item to the orchestrator, not only from UiPath but from Javascript, I can only use an item from UiPath. It's restrictive, based on our company guidelines. 

If there is any change in the selector in any application, we have to make changes accordingly in the code. Then we have to redeploy it again. It's one of the challenges we have. We cannot automatically change the selectors in the bot. 

My client has very old and complex applications. Getting that sorted for the bot can be very difficult at first. There may be a few extra steps in production.

I do need to check continuously for messages in Slack to work through processes. I have to run my bot every minute. There is some complexity with automating my bot through UiPath. I'm not sure if UiPath completely supports Slack automation. I've seen tutorials that show you can automate in Slack, however, I've had some real problems with the process. 

The stability of UiPath is very good. However, to build a bot requires us to go through many phases. Bot development is easy, however, getting access to applications can slow the process down.

We're using the solution around the globe. We are using the solution in different areas in India and we have many teams using UiPath. 

The scalability of UiPath is very good. I'd rate it nine out of ten. 

Technical support has good knowledge of what's happening. Whoever supports the bots, however, needs to have good knowledge. 

Positive

I did not previously use a different solution. UiPath was something my client wanted. 

The implementation was easy. Once we connect our bot to the orchestrator, it's very easy to publish to the orchestrator and move it. 

We deploy our code in a remote VM. Due to the license issues, we cannot have UiPath installed in the VM, where we deploy our bots. We have to do it via the orchestrator. There may be licensing issues that make it difficult to deploy UiPath to virtual machines. If we have any issues, debugging is difficult. 

We do have templates related to the company and use those to build automation. 

There is maintenance required while using the solution. Once you commit your code, the maintenance is pretty easy. We upload our code to the orchestrator. Beyond that, we may need to handle updates of UiPath. 

We did use a third party to get some credentials. Everything else was handled in-house. 

We have seen an ROI in the form of reducing employee costs. 

I don't deal with the costs. The company is handling the licensing. 

I did not evaluate other options before using UiPath.

I have not yet used UiPath's AI functionality. 

I'd rate the solution nine out of ten. 

I would advise others to make sure they learn the solution and gather knowledge in order to understand how to start before jumping into real use cases. 

The use cases depend on the processes. The processes we have so far have been complex. It took almost six months to complete each process. We required four developers per process. We have been working for the same client since 2021. Before this, we worked for other clients and automated almost five to ten processes, but they were not critical processes like what we currently do.

UiPath is user-friendly. Our customers get to see what is happening on the screen even if we deploy it on another machine. They can easily see what is happening in the background using log messages in the Orchestrator. People always have concerns about how well the credentials are stored. UiPath uses Thycotic Secret Server to ensure the credentials are not shared with anyone else except the client.

We are working on processes that involve Excel automation. We can use our coding knowledge for these processes. If we have someone who knows coding, instead of writing lengthy codes, we can finish it within a second. Even if it is a big Excel, we can achieve our needs within fractions of seconds. Activities like InvokeMethod are really helpful while doing Excel automation. New releases come up very frequently. The vendor is working very hard to make it a very efficient tool.

Support should be improved.

I have been using the solution for four years.

The tool has 100% stability.

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

We found some issues with Salesforce Activities. We have raised a ticket with the support team. It has been almost a month, and we don’t have a solution yet. It's already in UAT, and we might deploy the bot by the end of the month. However, we haven't received any response from the support team. Whenever we call support, the support person says that they will get back to us. We didn't get a solution for the issue we raised.

I have contacted the support team for previous projects. The team did not take much time to resolve the problem. But this time we had difficulties resolving the issue. I'm only satisfied 80 to 90% with support.

The deployment was straightforward. If everything is in place, we can deploy the product in a few minutes.

The solution does not require much maintenance. It is a stable platform.

UiPath's cost is a bit high compared to other RPA tools. However, a few clients prefer to use UiPath. It will be helpful if UiPath reduces its cost a little bit.

We are using UiPath for our current project. It's already in the UAT phase. We plan to put it in the production environment by the end of this month. I started my career with UiPath. I am still working on it.

It is easy to build automation using the product. I have also used Automation Anywhere and found some difficulties when using it. Some features available in UiPath are missing in Automation Anywhere. It is very easy to drag and drop activities in UiPath, and we can add multiple conditions within one activity. I couldn't find these features in Automation Anywhere. It is one of the biggest advantages of using UiPath. More than 100 activities are available in UiPath to do Excel automation. Other RPA tools do not have such features.

The product enables us to implement end-to-end automation. The same can be achieved through other RPA tools as well. A few of our clients prefer UiPath because of the features and support we get from the tool. Some things cannot be achieved through other automation tools. If someone wants to automate or scan a PDF, we cannot achieve it through other automation tools. UiPath has a lot of options for the users. We can also integrate third-party tools into the solution.

If a company uses five employees for a process, it would need only one employee after it is automated using UiPath. The other four employees can be allocated to other tasks. It will depend upon the complexity of the process. A company might require one or two employees after the automation if it is a complex process. They would have a support team to help them, but sometimes, clients want someone from their side to check things.

We couldn't save costs in a few processes because of the complexity of the processes. Almost 80 to 90% of our clients benefit from UiPath. If a company invests in UiPath, though the cost is a little bit high, it is a one-time investment. Later, they can see profits from this investment. It is not seen immediately, but the tool is definitely helpful for clients.

The tool reduces human error. If some people do a job daily, we can do that job using UiPath. If a human takes an hour to complete a job, UiPath could do the same job in one or two minutes. It cannot do it 100%. Some cases might require human intervention. If there are no multiple scenarios or edge cases, then it's very easy for the developer to train the bot. If we get the proper requirement, we can definitely achieve it through UiPath with zero error. The current project that we are working on is in the UAT phase. We come up with new scenarios every day. I cannot say that any process can be done with 100% perfection.

We have freshers in our team who do certifications in UiPath Academy. People who complete courses on UiPath Academy will get some basic knowledge of web automation and Excel automation. They will feel confident achieving something using UiPath. If we put someone directly into the project without the basic knowledge, they may find some difficulty. UiPath Academy courses help us get some basic hands-on knowledge of UiPath.

UiPath’s user community is one of the key assets for any UiPath developer. We get information on new updates, versions, and activities from the community forum. During development, we might get stuck while implementing things like Excel automation, web automation, selector issues, logic issues, and coding issues. If we get stuck while doing something, we can post it in the forum and get a solution. The community is very helpful for all the developers. I work for almost four to five clients and three to four companies. Most of the developers are part of the community.

Most things can be achieved with the product. I would advise people to use the platform. We get responses to our queries very quickly on the forum. Whoever is available will respond to our queries. We also have an internal WhatsApp group where we can post our queries.

Overall, I rate the solution a nine and a half out of ten.

Our use cases are generally related to front-end UI-based automations that emulate tasks done by teams. For example, we do front-end SAP automation for data entry and scraping or posting data to websites that are related to the organization. We use UiPath for other automations like extracting and manipulating data from Excel. The primary use cases are in finance, HR, and operations. In logistics, it's used in full-sprint solutions.

UiPath's ability to do end-to-end automation is crucial. If we do the automation in bits and pieces, it's challenging to integrate it. The best part is that the turnaround time is drastically reduced because the process isn't being put on hold in between two manual interventions. The more permissions we apply, the more we reduce the turnaround time. However, the smaller automations don't impact the turnaround time that much. If the logic is set correctly, it can completely eliminate human error. 

The UiPath community development forum is helpful. Developers can access all the information they need if they get stuck. For our use case, we refer to OpenMedia, not any particular program. To understand what are the RDP use cases. I personally follow primary and secondary research forums as well as McKinsey's technology consulting newsletters and documentation.

The UiPath Academy explains various use case scenarios through videos and training sessions. It's all practical, hands-on instruction instead of purely theoretical. That made a significant difference by increasing our confidence in the product and ability to create our own automation. You can track each team member's training steps in parallel because everyone needs to be on the same page.

Uipath doesn't necessarily reduce our on-premise footprint. We use UiPath to automate configuration integration, so I can't say there is any direct impact because RPA is now just part of our on-prem ecosystem. The solution doesn't require expensive or complex application upgrades, but certain applications need scripts to be enabled to get UiPath working on their front end.

It saves time, but the amount varies. Each process has a different impact depending on the frequency of that process. If a process is running daily, the values are high, but sometimes it's low. The organization aims to have one bot per person, so everyone has one attended bot that can replicate their monitor network. It's the equivalent of adding one FTE per year by default per person. Every person can have a bot, scale up the work, and get more done in a day. 

The amount of money saved also depends on how often the process runs. We pay per bot, so if the bot isn't running frequently, we might not save any money. However, if the requirement is to do many more tasks than a single person can handle, it makes sense to use a bot, and we can save a lot of money that way. Sometimes, we have different goals beyond just saving money or reducing the time that our staff members spend on tasks. We might deploy a bot to improve the user experience and save the user some time. In some cases, we might not see short-term savings, but we'll see a benefit from it in the long run as the process volume increases.

The feature I like the most is ONEWEB UI automation. UiPath's OCR technology also works well. There is another feature called Action Center that lets you decide what happens after the data is captured. It passes the data into Action Center, where a person can review and approve it before it goes to the next step. It helps us manage our attended bot processes.

It's generally easy to build processes because of the drag-and-drop configurable suite. However, more complex expressions may require some kind of functional coding. UiPath also has some prebuilt functions in its training module that can be utilized to enter the expressions and get the job done. That's one workaround.

UiPath's built-in integration with Python scripts could be more robust so that I do not have to depend on another technology and I can do everything on one platform. 

Each program you write on UiPath contributes to bot consumption and utilization. As you add more bots, your costs will increase for more actions. Python is open-source, so it is totally free. Depending on our automation needs, we go back and forth between these two technologies. Better integration between these two tools will help organizations cover all areas of automation without more cost-effectively. 

I have used UiPath for approximately two years.

I rate UiPath nine out of 10 for stability. We haven't faced any challenges with UiPath's stability because it is a SaaS product. It runs on the UiPath cloud, and things are working fine. 

UiPath is fully scalable. I haven't faced any challenges in terms of scalability because the cost is not per user or per process. It is priced according to the amount of bots being consumed, so it all depends upon the complexity of your own project. If the complexity is lower you can reuse and share 

I rate UiPath support nine out of 10. They always respond with solutions within the time established by the SLA. 

Positive

We were working with Power Automate. It has benefits from a cost perspective. The cost per developer is much lower relative to UiPath. Power Automate is a more cost-effective solution for larger enterprises. However, UiPath has more technological capabilities, and it's more user-friendly for developers, which is why UiPath is being adopted more over Power Automate. At the same time, Power Automate is continuously improving, so it may reach the same level as UiPath in the future. 

We are using the cloud version of UiPath, which is hosted by the UiPath team themselves. We do not use a private cloud. The network configuration didn't take much time. The deployment involves setting up a UiPath account and configuring permissions. It is a SaaS platform like Office 365.

The deployment time is just the amount of time required to develop processes for the project. It depends on the size and complexity. A project with hundreds of activities might take a few months, but a simple project with only two processes can be done in a few hours. 

I rate UiPath eight out of 10. 

I work on database automation. We just delivered a dynamic workflow in an Excel automation as well. We work on many types of formulas. In addition, we develop physical automation. For example, we created a process that posts many photos at once on many groups.

We are able to produce output with UiPath in less time. Where a manual process takes one to two hours, we can develop a UiPath solution that takes 15 minutes. In terms of saving time, one bot has saved 60 to 70 percent of the time the task used to take. We have also seen human error reduced by about 60 percent. 

We have automated processes with 20 to 25 bots, and our organization is very happy with UiPath.

It's easy to go with UiPath. It's user-friendly, and any IT person will find it easy to use. It can be learned in six months to one year.

Also, we can use Orchestrator with Action Center for end-to-end automation. With Orchestrator, we can schedule automations.

I would like to see the setup improved. First we install it, then we log in with Orchestrator, and then we have to log in to the UiPath website. I would like all this to be merged into one setup.

I have been using UiPath for 2.7 years.

The stability of UiPath is a nine out of 10.

The scalability is between eight and nine out of 10.

Support can take a lot of time, two to three days to receive a response.

Neutral

I have developed Excel automations with Power Automate.

We are using the Community Edition of UiPath and it is deployed on our servers. We use it in one location in one department. It was not a complex process to install it, although there was a little bit of complexity to it.

If there is any activity or anything changes in the environment, maintenance of UiPath can be required.

We have saved both time and money and have definitely seen return on our investment.

The price of UiPath is not too expensive or too cheap. It's in between.

We have four people involved in deploying automation: one developer, a team lead, and two DevOps developers.

My recommendation is to learn flow development.

We are a distributor and most of our customers were manufacturing and financial companies, so the use cases fell into categories like financial, accounting, and procurement departments. We used it to improve business processes.

With UiPath, my clients were able to free their employees and staff for other types of work. They saw value in that. Staff didn't have to get up at 6 AM or work around the clock in front of a monitor all day. It freed up staff that had been doing menial, manual, repetitive tasks to do something more valuable.

In some cases, it reduced the time it took to get a task done from hours to a couple of minutes. Workflows that would take up to four or five hours were reduced to taking 10 to 15 minutes.

It also definitely reduced the amount of human error to almost zero. 

UiPath Studio has all kinds of tools and it's practical to navigate around the application. Implementing any project can be done very quickly using UiPath. Also, the robot capacity is phenomenal. They work as long and as much as you need them to and provide optimal performance.

Building automation with UiPath is easy and takes a small amount of time. It's really intuitive and doesn't require advanced development or any technical skills. It's easy for anyone to pick up and understand. Any lower-skill employee or developer can learn to use it quickly.

We would usually do a pilot project with a company and, afterward, transfer all the knowledge and capabilities to them so that they were able to develop things themselves. Especially with the UiPath Academy, which provides online courses, and the UiPath forums, everyone could learn how to use it. My clients had no problem picking it up after our first pilot project. The advanced developer courses help a new developer quickly learn how to use it.

There can be technical issues, but it's rarely about a server quitting. They are more like connectivity, platform, and software version issues, but there are no issues with UiPath performance.

I would also like to see UiPath assist clients in scaling up their usage of the application because most of our clients had trouble expanding their usage into other departments. It was hard for them to calculate the exact value they were getting. Some of our clients were flying blind.

Some of our clients hadn't really seen enormous impact from implementing and using automation yet. They had just started, and they saw the value in it, but it was hard for them to expand or add more value to automations with UiPath.

I worked with UiPath from 2019 to 2022.

It can take their technical support some time to respond. And sometimes, the assigned staff doesn't have the right knowledge, but that doesn't happen often.

Neutral

The initial setup is straightforward. Our clients did ask for tips and tricks, but they didn't need a full consultation. They managed it themselves. It's really intuitive.

UiPath pricing is high and sometimes it's quite complicated as well, because there are loads of components and loads of product portfolios. It works, but it could be better. The pricing could be more attractive.

UiPath definitely speeds up digital transformation but whether it reduces the costs of doing so depends on a number of factors.

Over the years, UiPath has done a pretty good job of continuously improving its product by adding robot capacities and changing versions. In terms of features, they have everything covered, with AI features, data mining, process mining, and all that was done quite ahead of everybody else.

I would say that UiPath, as a company, was better in the past. Nowadays, I have less confidence in the company's situation, not that I don't think it's stable. And their ability to improve is a 10 out of 10.

My advice is to study your use cases and go to the UiPath Academy. You'll find everything you're looking for and there is a big community. UiPath is easy to use, but you have to understand your work processes thoroughly and not just depend on the application to help you.

Our primary use case is for RPA. We use it for checking invoices and sending out electronic letters. It is also going to check the absence entered by people when they are sick and see if those fill-outs are correct.

UiPath enables us to implement end-to-end automation. It is very important. It makes us more efficient. It does not require that much labor.

We find UiPath quite good in terms of ease of building automations. It does not require an enormous amount of knowledge. It is quite easy to use, but we need to do some scripting and programming in addition to the software.

We use UiPath's AI functionality in our automation program. It is necessary to interpret PDFs. We only use it in one process so far. It has only been six months, so it hasn't enabled us to automate more processes overall.

UiPath speeds up digital transformation and reduces the cost of digital transformation. This digital transformation does not require expensive or complex application upgrades or IT application support.

UiPath has reduced human error. In the use case for checking the invoices, it helps us to handle an invoice more correctly and send the invoice to the correct person internally so that it does not go in a loop somewhere.

UiPath has freed up employee time. By the end of this year, it would have saved us two whole man-years.

UiPath has saved us costs. In the six months of running it, it has saved us something like one and a half million.

The software does what it is supposed to do. I do not have any specific features that are valuable. We mainly use it for automation. We use the standard application screens. It meets our requirements.

We would like to use several modules of UiPath, but they are very costly. All the additional features that we need are there, but they are in the modules that we have not bought.

Its stability could have been better. 

It was installed around September of last year.

The stability could have been better. We started out with one developer license and then we had another developer license. When both developers are working in the cloud platform, it shuts down. I am not sure if it is solved yet.

I do not know about the scalability yet. I hope it is scalable.

We have not used their technical support. We used the UiPath community for some issues. We were trying to learn how to program, and we were stuck and trying to figure out how to do certain things. We posted a couple of questions to the community. There are always people there who are willing to help and come up with good ideas to solve the problems that you have been stuck with.

We did not use any solution previously.

It is in the cloud. Our cloud provider is Digital Workforce.

The deployment took four months. It was straightforward. There were no issues. The integration between the cloud platform and our internal networks with the firewalls was really smooth.

It does not require any maintenance from our side.

It was Digital Workforce that showed us that this is how we would want to do it. We based everything on their strategy.

With the rate at which we are going with automations, it should take us a year and a half or two years.

UiPath has several modules that we would like to use. They will enhance our installation, but they are very costly. 

We are quite happy with the solution as it is. If I were to go for UiPath again, I would not choose Digital Workforce as a supplier.

I do not have any experience with any other solution, but we have had some glitches, so I would rate UiPath an eight out of ten.