Nintex RPA Reviews

Our primary use case for Nintex RPA involves getting documents from emails, reading those documents, and transferring them from the IRD to finance. We are also exploring the LP and Intech features for more advanced use cases.

Nintex RPA helps our government and public sector customers with automation. It is especially useful for operational tasks like handling statistics and services.

While we have only explored the simple use cases so far, Nintex RPA has good integration capabilities, such as working well with Gmail and Outlook to automate document handling and notifications.

We need better training and community support in Indonesia. It would be helpful to have more representatives who can provide training and share knowledge, as our team lacks the deep skills required for RPA.

We have been working with Nintex RPA for one to two years. During this period, we have been collaborating with our internal team for various use cases.

On a scale from one to ten, I would rate the stability of Nintex RPA as an eight out of ten. It is quite stable.

I would rate the scalability of Nintex RPA as a nine out of ten. It is quite scalable.

The support from Nintex is very good. I would rate it as nine out of ten.

Positive

The initial setup was managed by our distributor as we do not have the expertise to handle it ourselves.

Our implementation was done in collaboration with a local distributor in Indonesia who handled the installation due to our lack of specialized skills.

Although Nintex RPA is expensive, it is somewhat affordable considering its features. I would rate the cost aspect as an eight out of ten.

We are also partnering with other vendors such as Microsoft, Oracle, and IBM.

I'd rate the solution eight out of ten.

We use it for discovery on desktops to understand what operations are actually doing. Using task mining capabilities allows us to record activities and identify efficiencies and potential process improvements.

Kryon RPA has improved our operational efficiency. 

It has helped us identify areas where frontline staff aren't following standard procedures or using unexpected systems, giving us better insight into our end users' workflows.

The process discovery feature of Kryon RPA enhances our automation strategy.  It reveals activities on the user's desktop, capturing hidden knowledge not mentioned in interviews.

The task mining aspect has been the most valuable for us. That's why we actually bought it. 

Extracting meaningful data requires significant effort. You need a dedicated business analyst who can understand the output.

We used it for two years. We use the latest version. 

I would rate the stability an eight out of ten. It is very stable. 

It's reasonable enough. I didn't notice any major issues.

To analyze and make sense of the data generated by Kryon process discovery can be a lot of effort. It's not as automatic as some might think. It really depends on how many processes you have and how actively you use them. 

But the scalability aspect isn't necessarily about deployment or technical maintenance. It's really about how you analyze and gain insights from the data gathering.

I'd rate the scalability a seven out of ten because the solution has been scaling well for a long time. It's very easy to deploy. But getting value out of it at scale can be a challenge, just like with any deployment.

We use it mainly for process discovery. We actually proceed it from different teams. So, we have 15 licenses that we rotate with different people, actually through different teams. 

So, we do discovery for the online team; we gather the results after about two weeks to a month. We analyze those results, and then we deploy them again on the analytics team.  We regularly deploy it to different teams. So, it's in constant use.

It just runs on the systems through discovery mode most of the time.

The customer service and support are quite good. I'm quite happy with it.  

We are happy with the support we get. 

Positive

We have our own RPA. We have other RPA tools, but for process discovery, we didn't have anything. We saw Kryon before other RPA options.

I would rate my experience with the initial setup an eight out of ten, with one being difficult and ten being easy to setup. It wasn't very difficult.

It was relatively straightforward, though aligning it with our security protocols took some effort.

We deployed it on the cloud. 

The cloud here means the clients reside on our physical machines, and we connect back to the cloud that stores the data. I'm not sure where the cloud is located, but we feed the data back to the Kryon Cloud.

We did it in-house. The number of people required for deployment varies. A normal project team suffices, depending on the aspects of deployment. 

It depends on the scope. We mainly used Kryon process discovery in a very limited manner. So, a team of five could manage it and redeploy when needed.

From the proof of concept to production use, the entire process took maybe four months. That was because we had to go through a lot of compliance reviews and checks.

It is very cheap. I would rate the pricing a three out of ten, with ten being expensive. 

You just have to pay for your own people to analyze the output from the tool.

We evaluated others, but they were significantly more expensive.

So, the price was the major deciding factor. Moreover, Kryon got more capability in certain areas, but the price was just limited.

Overall, I would rate the solution an eight out of ten. 

I would definitely recommend using this solution. Decide what you need from the solution. It's not generic. So understanding the purpose why you're buying this product exactly.

We use Nintex RPA in a complex environment and for working with legacy systems as well as with open systems and outside the company environment. We use the tool in order to do daily tasks that replace employees. 

It has improved operational efficiency, reduced manual workloads, and increased accuracy in repetitive tasks. The platform’s user-friendly design and automation capabilities contribute to streamlining processes and achieving overall productivity gains.

The solution could be good, but suffers from some unexpected flows. Sometimes it stucks or stops - which requires some manual intervention. No newer versions!!!

Initially, it improved operational efficiency, reduced manual workloads, and increased accuracy in repetitive tasks. The platform’s user-friendly design but very old .The automation capabilities contribute to streamlining processes and achieving overall productivity gains. 

Nintex RPA’s drag-and-drop design interface, automation capabilities, and integration with some systems are helpful. Its ease of use and ability to automate repetitive tasks efficiently contribute to its popularity. Helpful aspects include:

1. Visual Design Interface: The drag-and-drop interface allows users to design automation workflows graphically, making it accessible for those without extensive coding backgrounds.

2. Cross-Platform Integration: Nintex RPA supports integration with a wide range of applications and systems, enabling automation across diverse platforms and enhancing its versatility.

3. Reusable Components: The ability to create and reuse automation components (such as workflows and actions) helps streamline the development process and maintain consistency.

4. Scalability: Nintex RPA is known for its scalability, allowing organizations to scale their automation initiatives as per their needs, from simple tasks to complex business processes.

5. Error Handling and Logging: Robust error handling mechanisms and detailed logging features assist in identifying and resolving issues, enhancing the reliability of automated processes.

6. Community Support: Not relevant for 2025. No comunity.

7. Security Features: Nintex RPA often includes security features, including encryption and user access controls, which ensure the protection of sensitive data and compliance with security standards.

Improvement areas and additional features for Nintex RPA should include:

1.  AI Integration: Integration of more advanced AI capabilities for improved data recognition, natural language processing, and decision-making within automation workflows.

2. Expanded Library of Connectors: Continuously adding connectors to popular applications and systems ensures broader compatibility and facilitates smoother integration with a variety of platforms.

3. Collaboration Tools: Introducing features for collaborative development and version control can enhance automation developers' teamwork and streamline automation project management.

4. Mobile Accessibility: Improving mobile accessibility for monitoring and managing automation workflows on-the-go can be beneficial for users who require flexibility in their work environment.

5. Low-Code Enhancements: Further simplifying the low-code development process can attract a broader user base by making automation accessible to those with minimal technical skills.

6. Machine Learning Integration: Integrating machine learning capabilities directly into the platform could enable more intelligent and adaptive automation, allowing processes to evolve based on patterns and insights.

7. Community-Driven Content: Encouraging and facilitating a community-driven platform where users can share custom components, templates, and best practices could enhance the overall user experience.

I've used the solution for 8 years (I also used older versions).

Stability depends on versions and the amount of robots. In newer versions it is more stable as long as you use about two to three robots. 

The solution is not scalable.

I don’t have enough experience to speak to support services. 

Negative

I didn't use other solutions previously, however, I have since used UiPath and found it more stable (but it costs  more).

The initial setup is usually easy. 

We worked with a vendor - a very experienced one. 

The ROI was good, however, it depends on implementation.

It was one of the cheapest in the market for small businesses. Now Microsoft does the same with less cost.

I have evaluated:

• IBM RPA
• UiPath
• Microsoft’s Power Platform

Don't choose it as the company is dead.

We use it to automate some processes that require no human intervention. Currently, we have three projects: dispute resolution, settlement reconciliation, and consolidation.

I find it very easy to use and customize. The bot can be configured dynamically to use dynamic values, and we can use attended bots to interact with the flow of the bot. Also, it's very seamless to interact with Excel files and web app pages. So far, we have not encountered any issues while building using the action blocks.

We have also used its functionality to call REST services and SOAP services, and we can make use of JavaScript or Python scripts. There are a lot of functionalities that we can leverage.

Areas, where I see some room for improvement would be the use of reading details from an Excel file. Most of the time, it's difficult when I say looping through a huge data set, and it's very difficult for the bot to interact with those data sets unless it starts offering the Excel file. As of today, from the reports I've worked with, I noticed that most reports are empty columns and two rows. So if Kryon can associate with that and extract those deposits into a variable, and the tools can easily fit out to column dash and two rows and columns, it will be nice. But as of today, the bot doesn't have the functionality to detect variables. We have to do it on the Excel file itself.

I also noticed that when it comes to the use of bots, not everyone has the same knowledge, and it can be difficult to do certain research unless you have advanced knowledge of what you need to do. I also noticed that in the community, most people don't use it, and it's quite difficult when you need certain support.

We started using it about a year ago, in 2022. The version we use is 22.3.1.

Based on how we use it, it has no breakdowns. It's very stable. I mean, it's been months since we encountered any breakdowns.

Everyone has access to it, so around ten people are using Kryon RPA in our organization.

We have contacted the customer service and support team before. We were facing some issues with the console, which is the administration page where we see expenses, expanded entries, bots, and successfully run lines. At some point, we were unable to connect to the page, so we had to contact the support team. They came in and resolved the issue.

The support was good, but our relationship with Kryon's support team is very good. So I would rate it as good.

Positive

I have in-depth knowledge of Kryon RPA and other similar tools. I have used Ui Path and Blue Prism in the past, and I find Kryon to be similar and easy to use.

I have a good understanding of all the action blocks and how to use them, which makes it easy for me to set up and use Kryon.

I would say the installation is not complex. When we did our own installation for a vendor due to some permissions and restrictions, it took us around two to three days. But normally, if we don't have those issues, I can say the installation is quick and straightforward. It didn't even take me a full day to install and set up the solution.

The price is affordable. The license is based on the number of bots and users.

We had some back and forth using the setting tools of the RPA solution and noticed that other RPAs were costly. We found that Kryon RPA was cost-effective and had features other apps didn't have.

I would give Kryon RPA an eight. As a developer, I find it easy to use. The codes are written in a language that is understandable. They also have documentation available on their website that explains how the tools work. The way the tools are built is simple to understand. The steps can be split into different parts, and there can be more than one step for a particular bot. The fundamental aspects of the process build are easy to understand. Additionally, the build has current and account notes explaining what each step does. 

Overall, Kryon RPA is easy to understand, which is why I gave it an eight. I would definitely recommend using the solution. 

We're predominantly focused on the contact centre because that's our primary core business, and a lot of RPA use cases are in the back offices. The challenge for contact centres over the years for all RPAs has been that it's hard to establish the business case. The complexity of that environment includes determining and prioritizing which process you want to automate first.

We have done quite a number of back office stuff, but our vision is to link the back office to the front office in terms of customer experience. We are a speech analytics company, and we specialize in that area. We have challenges with corporates because every vendor comes in with a return on investment equation, but there's only so much that our customers will do. We saw that combining our capability with what RPA can do would really help with the business case for automation.

The full-service automation aspects and the process discovery are the most valuable features of Kryon RPA. The process discovery is where you spend most of your time in RPA. We're not a big professional services company and don't want to build a massive team. So, the more we can automate on the front end, the better it will be for us.

Kryon RPA's automation, process discovery, exit deployment, bots management, and change control management are really good.

The process discovery tool of Kryon RPA could be improved because of its limitations. I'm looking forward to the new release, which will fix these limitations.

I have been working with Kryon RPA for about three years.

Kryon RPA has decent stability. Once you've built your bot, they run really well. With RPA, you're always a victim of what the client does. The biggest challenge in RPA is managing the customer. A customer might do a version upgrade on something that's out of our control. However, from what we can control, Kryon RPA is a stable solution.

I rate Kryon RPA an eight out of ten for stability.

Most of my deployments have been pretty small. On average, they're about 50 users at the end of the solution. We don't have thousands of users sitting at the end of these things. The console that manages all the bugs you deploy is really good. The chances of our company getting involved in a big telco are very, very small. We're using Kryon RPA mainly for organizations with 200 users and below based on per division. Kryon RPA is well suited and well priced for organizations with 200 users and below based on per division.

Currently, the two customers that use Kryon RPA are in maintenance mode with us regarding change control and management. Our clients are medium sized businesses.

Based on my experience with other RPA products, I rate Kryon RPA an eight out of ten for scalability.

Kryon RPA’s technical support is very good.

Positive

I rate Kryon RPA a six or seven out of ten for its initial setup.

The pilot phase we did the first time went really well. The deployment with Kryon RPA is ongoing, and there are always improvements. We are pleased that we were able to deal with the security aspects of managing and dealing with customer data. We're dealing with tier-one organizations in terms of managing their data and getting through security.

Compared to its competitors, Kryon RPA's pricing is very competitive. We've priced Kryon RPA based on the use cases that we're getting and the return on investment. Its list price is one dollar, but we got it for 30 cents because the pricing was negotiated.

Along with licensing, we paid Amazon to set up the Amazon infrastructure to support the software. We also got the whole environment certified as an ISO-certified environment. Additionally, there are resourcing costs because we set up a fully managed service proposition around it.

We had to pay about 30% additional cost in addition to the standard licensing fees while using the solution.

I rate Kryon RPA a four out of ten for pricing.

The reason we selected Kryon RPA was because of the automation capability of the process discovery. It's a little bit immature, but the new release will fix a few bugs in the product. The product has the potential to speed up the discovery process. The new version will overcome some of the solution's limitations and make it a better product. The automation capability or the RPA aspects of the solution are pretty much the same as what I've found in most RPA tools. It all depends on the environment you're integrating into.

Kryon's gone through some changes because they got acquired by Nintex. In that period of acquisition by Nintex, it's been a bit uncoordinated in terms of support and other things. But Nintex is getting its act together and integrating the product into its portfolio. That's a natural thing that happens following an acquisition.

Overall, I rate Kryon RPA a seven out of ten.

I have been using it for a few clients and office stations, including banking, insurance, and a major internet provider. 

The most valuable features of Kryon RPA include exceptional in-build management, simple transcription management, and deployment features. 

The user-friendly environment allows for easy learning, and the end-to-end workflow management is excellent. Additionally, the maintenance and management costs are comparatively low in terms of licenses, and the adaptability is also noteworthy. Overall, they have developed good features.

There are a few areas that can be improved. Firstly, Kryon RPA needs to enhance the robustness of its multi-board architecture to ensure the availability of bots on multiple machines. 

Secondly, Kryon RPA should focus on improving document extraction. When compared to other integrated products, such as those offered by its competitors, its document extraction capabilities need more attention. 

Additionally, Kryon RPA should work on enhancing the allocation response for multiple bots to maximize their utilization.

These are the key aspects that require improvement, along with the inclusion of a high availability feature. While I hope the data is stored in the cloud, I'm not entirely certain. However, it's crucial to ensure seamless integration with third-party vendors to enhance the usage of the product console.

The security aspect of Kryon RPA is good, which is why several banking and financial institutions are using it. As for stability, it ultimately depends on meeting the expectations of the individual customers.

I would rate the scalability a seven out of ten.

The support provided by Kryon, along with the learning academy and online forums, has been quite responsive.

The initial setup of Kryon RPA can be considered moderate. It is neither overly complex nor extremely easy. However, the configuration deployment and client version setup are relatively more user-friendly compared to other products.

Initially, the deployment was mostly on-premises as we explored the project's capabilities and conducted proofs of concept (POCs). This was during a period when the organization was also using AWS and Azure. However, gradually, we migrated to the cloud to leverage the product's features and capabilities. Initially, on-premises deployment was necessary for testing purposes. Now, the implementation and deployment process has been simplified, and we primarily use cloud apps.

The initial setup itself only took a few days. However, the duration of implementation and deployment depends on the complexity of the project or process being automated. Once the implementation is completed, the migration to the production environment is usually quick, taking only a few hours or days, but in some cases, it can take a few weeks.

The implementation timeframe varies based on the complexity of the specific use case we are working on.

The pricing is moderate compared to other products, and I would consider it to be economical.

The licensing features are very good, including the option for shareable licenses. The overall cost is moderate and economical.

Overall, I would rate the solution a seven out of ten. 

Kryon RPA is used in different departments such as Human Resources, Programming, Planning, Production, Commercial, etc. I use it when I program tasks for clients, in particular, to program the bots in client environments.

What I like most about Kryon RPA is the user experience. I also find the layout and design of the solution better for programming compared to other RPA solutions.

What needs improvement in Kryon RPA is the support. Sometimes, the solution has problems, so I contacted support, but I didn't receive immediate help from the team. You have to wait a while before the problem gets solved. This happens a few times in terms of getting cases solved.

It would also be better if Kryon RPA had a cloud version because currently, from what I know, it only has an on-premise version, though I could be wrong about that.

There isn't any additional feature I'd like added to Kryon RPA because it's a good service, but the support is very, very bad, so that area could be improved.

My experience with Kryon RPA is two years.

Kryon RPA is a stable solution, but its stability depends on the version installed in your environment. The most recent version of the solution isn't as stable and has a lot of problems that even the support team isn't able to solve. It's better to use an old version of Kryon RPA that's more stable than the newer versions.

Kryon RPA is not scalable. Other RPA software has more scalability.

On a scale of one to ten, where one is bad and ten is good, my rating for Kryon RPA support is four. The response time from the support team and the time it takes to solve problems need to be faster.

Neutral

The initial setup for Kryon RPA is very easy, and if you compare it with other RPA software, it's easier.

I saw ROI from Kryon RPA, but I don't have the exact values, and that would be confidential. If I were to rate ROI on a scale of one to ten, I would give it a seven.

I have experience with Kryon RPA for many versions, such as 19.3, 20, and 21. I'm a developer who provides services to clients, so I develop and create tasks in Kryon RPA for clients.

Two professionals take care of the deployment and maintenance of Kryon RPA. One specialist deploys it, and the other person is in charge of the IT infrastructure.

My advice to others looking into implementing Kryon RPA is to deploy in small blocks that can be reused in many jobs or many other tasks.

My rating for Kryon RPA is six out of ten.

Nintex RPA doesn't require much coding, and you can drag and drop the activities.

Nintex RPA is not suitable for PDF automation.

I have been using Nintex RPA for the last one year.

I rate Nintex RPA an eight out of ten for stability.

I rate the solution a nine out of ten for scalability.

I rate the solution’s initial setup an eight out of ten.

I am using the latest version of Nintex RPA.

Overall, I rate Nintex RPA a nine out of ten.

I primarily use Kryon RPA for attended and unattended bots and back-office automation. I've also used it for fulfillment cases in the retail domain, where it's been working quite well.

Kryon could be easier to use, especially in comparison to UiPath.

I've been using Kryon RPA for five years.

Kryon RPA is very stable - we've not had many disruptions, and the product is updated regularly.

The scalability's good, and it's flexible in terms of how you want to scale it up.

We've received good support from Kryon.

The initial setup is straightforward, without any issues.

Kryon is slightly more expensive compared to UiPath.

We evaluated Automation Anywhere and Blue Prism and found Kryon to be more approachable.

I would recommend Kryon to those thinking of installing it and would give it a score of nine out of ten.

I use Kryon RPA to make bots for the telecommunication and banking industries. 

I like Kryon RPA's ability to use automated and manual processes with any bot.

Kryon RPA's integration with other solutions could  be more seamless. 

I've been using Kryon RPA since 2019. I started at my previous company about four years ago, then I took another position at Banco Pichincha Ecuador. I'm a development architect working as an independent consultant at the bank. 

Kryon RPA is scalable. It's easy to create bots and schedule when they should run.

Kryon RPA's interface isn't as developer-friendly as UiPath's. I'd also like to see more seamless integration with other solutions. For example, with UiPath, we can use a lot of APIs. I also like Orchestrator from UiPath. We can control all of the robots that we're developing in the machines in the bot runners. UiPath Apps is a new tool that I like.

Microsoft also has some amazing tools, like Power Automate Desktop, Power Apps, and Power Automate Online. These tools can integrate with bots on Power Automate Desktop.

I Kryon RAP 10 out of 10. I recommend starting with easy processes. You should discuss the processes with the client, and go over things like cost, tools, time, and other things that are critical for the business.