Nintex RPA Reviews

We use the product to fetch particular records from Excel sheets and store them in the accounting system.

Nintex RPA is easy to use in terms of recording the steps. We can recognize and repeat the steps quickly. It has competitive pricing compared to other vendors as well.

It is complicated to detect an object using Nintex RPA. There could be some features to fix compatibility issues with firmware. The language on the product’s app could be easier to understand.

We have been using Nintex RPA for three to four months. At present, we use the latest version.

The product is stable, and it has an easy-to-understand UI.

We have less than ten Nintex RPA users in our organization.

The initial setup process is easy.

I implemented the product myself with the help of an installation guide. It took two to three days to complete the process.

The product has reasonable pricing.

We evaluated UiPath And Microsoft Power Automate. Both the solutions are expensive compared to Nintex RPA.

I recommend Nintex RPA and rate it an eight out of ten.

We have two primary use cases. One is the back office. We're a bank and we are automating some work of the bankers - mostly manual jobs like typing Excel data into our legacy systems and the like. The other thing is automating testing. We have really difficult scenarios involving both legacy and web systems. We hadn't found the right tools to take testing all the way from start to finish. But we have found Kryon very effective in that direction.

One way Kryon improves the way our company functions is in testing. Previously, we didn't have full coverage and we couldn't run a full regression day by day, or after major activities such as updates. We had to do it all manually and we didn't feel confident. Now, it's a completely different thing. We're trying to build a strong regression area where we can run a full regression of all our systems by clicking a button. We're not there yet, but we're heading that way. It's going to be a complete change in the way that IT acts because it gives us much more confidence.

One of the main features is its ability to connect into literally everything we've got here. Some of that was easier; some of it took some extra labor. But all in all, it has the capability to connect and to interact with almost every system that we have. That's the main feature. 

The next feature is the triggers. It's relatively simple to activate it. You can activate it via Control-M or via email. It has a lot of built-in triggers which enable us to easily activate the jobs.

The third is the support. We have great support from the guys here. It's not the product itself, but let's call it the "ecosystem" of the product. We have a strong product owner, and they respond very quickly to every question we have. That's a good thing.

The cognitive part, the OCR could use improvement, but I know it's on their roadmap. 

We need stronger governance to know, when a transaction is done, whether it worked or failed; strong logging. That would be helpful.

It's pretty stable. I can't think of a major crash.

We're not there yet, regarding scalability. It's fairly easy to purchase and make another robot, another machine, but we're not there yet. We're not at the limits of use of our first one.

Selenium was only good for web applications and most of our business processes involve more than just web applications. So if we wanted to run a complete test, end-to-end, Selenium didn't really help.

The initial setup took a while because we're a bank, so we have all the security requirements. It took a while but the setup was not very complex. The go-live took a couple of weeks but that was not entirely because of Kryon. It was due to the bank system itself, the firewalls and security.

Our implementation strategy was to go to the back office. We took ten nominees and we tried to pinpoint the one that would be most useful yet which was not too complicated. We gave it to Kryon as a PoC. They came and we said: "Let's take it step by step. Let's see if it works." If it did, we would try another one. We would then try to spread it among our core systems. We would connect it to each core system and have at least one active job in each of them. From there on, we made set up a center of excellence within the bank for automation, and people come to us now and ask us.

A Kryon consultant helped us with the primary deployment, but now it's our own team. Kryon guided us. We went to a three-day workshop with them where they explained it and gave us the primary technological understanding. Our experience with Kryon consulting was that they were helpful and professional. It was okay.

We're connecting with on a daily basis when there is a problem. But we have since made our own team.

We're a relatively small bank. So even if we can automate a decent scenario, we still don't have a lot of users or transactions. So the ROI is going to take a while in that area. In the testing area there is a good ROI, because we're now capable of doing things that we couldn't before. Completely. It's a game-changer.

For example, in the scenario of making a loan, part of the process was typing things into our legacy system. Selenium, the solution we had before, just couldn't do it. We had to abandon the goal of automating the scenario, and now we can. It's a game-changer in that respect.

The truth is, when we brought Kryon, we didn't think about automating testing, and they didn't recommend it. It was not meant to be a Selenium or testing tool, but we thought it could be useful, and it turned out that it was.

We did not evaluate other vendors. We quit using Selenium and, once we got Kryon, we said to ourselves, "Why not try to use it in place of Selenium?" It turned out to be much more useful and much cheaper, because we already had the license so we can use it whenever we want. Selenium was expensive and it only gave us certain aspects. So all in all, going with Kryon was a good thing to do.

There is a vast field of RPA tools. You have to know what you want to do and how to add value to your business. You need to see if what Kryon gives you is the best fit for you. For us, as beginners in the field, it was good, because of the support and the willingness to help us and to be cooperative. That was very helpful at the beginning. So you have to evaluate which step of the RPA lifecycle you are in. I can tell you more, in a year or two, if I'm satisfied when I am more advanced. But for starters, it is a good decision.

In terms of using the solution for the full cycle of automation, from the discovery of processes to turning on the automation, and scaling it up, it's a little bit early to say, because we don't have a lot of experience. And I can't compare it to any other thing that we have, because we're really at the start of it. But so far, it has met our expectations. I didn't think it would go as fast as they described it, and it didn't, but it was fairly rapid, and it has its ROI. All in all, good.

It's not for end-users, absolutely. It's not that. For developers, it is interesting. We didn't actually use developers to work with it. We had more, what I would call an "implementation guide." It takes knowledge and it takes time. There are a lot of technical issues, not only because of Kryon but because of our system and the integration between Kryon and our system. It's definitely not for end-users, regardless of what anybody says. It's not. But it's fairly decent for developers. 

We have our four developers who actually touch Kryon. We have two-and-a-half to three people who are dedicated to deploying and maintaining it, and another one comes and goes. We definitely have plans to increase usage. At the moment we do about 1,000 transactions each day, but we want to get do more.

As for helping our organization embrace digital transformation, we're heading that way. It's only the start, but we have a good vibe here. I could answer that question more comfortably in a year. But I see the way. I see the light.

We had an outside advisor, not Kryon itself, to help prioritize processes that are ripe for automation. We preferred it that way. Maybe Kryon could have given us that service, but we preferred to take an outside advisor.

I would rate Kryon at eight out of ten. It's not as rapid as they describe it and it has its limits. We have met with Kryon a couple of times. The guys were very helpful and said, "We'll bring that into the roadmap," etc. But we hit the limit of the product. For starters, we expected that to happen in year-two or year-three, not three months after trying it. But all in all, it has been a good experience.

I primarily use this solution to substitute processes where humans perform checks that do not need human judgment. These include onboarding, offboarding, and changing a contract. 

Kryon will allow you to automate processes fast and easy and you do not need to be a developer to automate processes. The advanced command will let you integrate with other systems quite easy.

Apart from the usual advantages (recording etc), I think the process that is presented as  'Powerpoint' slides makes it really easy to close the gap between the subject matter expert and the person configuring the robot.

It could be more reliable in spying HTML. I did expect this to be better in the 19.4 version.

I have been using Kryon RPA for almost one year.

As a company in the insurance industry, we use it for various functions within finance, such as identifying duplicate invoices, reporting, some operations functions - moving information from one system to another - as well as claims-processing.

Kryon has saved us a bunch of money and time. Specifically, it sends reminders out for claims that have not been actioned after a set period of time; for example, dormant claims, which haven't been updated or touched in five years. We actually created a job to send out reminders to the brokers to try to get updates. Since then, we've been able to close numerous claims and therefore reduce our reserves by literally millions of dollars.

It has provided overall money savings and overall time savings. We've got dashboards that show our overall stats from all our jobs. So we can say robotics has saved X amount to date, Y hours per department. Some of the jobs measure finances. There are literally hundreds of hours and millions of dollars in savings.

The solution has also increased operational efficiency. The percentage varies per department, but there are some departments that are saving two hours a day of people's time, so that's quite significant. If you think about an eight-hour day, that's 25 percent for a department which is already stretched thin. Time is extremely valuable when resources are slim.

We have also seen a reduction in employee errors. One of our jobs for finance looks for potential duplicate invoices. There were instances in the past where duplicate invoices were sent out, bills were paid twice, etc. It has dramatically reduced that. I don't think we've had one since we implemented the job. The automation searches for anything that looks similar in specific fields, using search criteria, and then produces an exception report. Instead of having someone go through 10,000 lines in a spreadsheet, they then have about 50 lines to compare. Obviously, it's much easier to identify duplicates in 50 lines as opposed to 10,000.

Finally, Kryon has helped our existing workforce embrace the digital transformation of our company. There is, obviously, resistance to change no matter where you go. Certain people will respond differently. But overall, the response has been really supportive and positive, especially from management. They're very happy with the way things are developing, the way time has been freed up. Most of the developers, and most of the people who use the automation, are also happy. There are only one or two people who feel a little threatened by it still. They don't really voice it. It's just that you can sense the resistance. I think it's a fear of their jobs going away. In our case, there's enough work that people just need to be repurposed and do other work. There's more than enough work for everybody. It was never one of our objectives to eliminate full-time employees.

The recording capability is valuable because of the amount of data it captures automatically. It's quite good. It means less development, and fewer configuration settings to fill in after you're done.

It's quite easy to use, end-to-end, minus the Process Discovery piece. The ease of use is probably the best part about it. For developers, the program is very user-friendly.

Process Discovery currently is not working for us. It's not giving correct information, correct stats. It's an issue that is currently open with Kryon as a ticket that they are investigating. In our instance, it did not function as advertised. As a result, business analyst hours haven't factored in because Process Discovery is generally the piece that's supposed to save business analyst time. As of right now, we've saved no time in that area.

Also, troubleshooting and debugging could be improved. It's missing a proper debugger. It's very difficult, based on the log files and the fact that it doesn't have a proper debugger, to troubleshoot issues. It will sometimes end with no indication as to why it ended and it becomes a bit of trial and error. Obviously, that is not a great use of time. If there were better debugging tools and logging, we'd be able to find the issues more quickly and fix them more quickly.

Right now we're having issues, so you've caught me at a bad time. Once you get it in and working, it's quite stable. Part of the problem goes back to the development. Our biggest frustration at the moment is the time to develop, because we are doing a lot of trial and error. It goes back to that debugging and lack of logs. It takes quite a while at this time, longer than we would like, to move a job or prepare it for production. Once it's done and in production, it's very stable. It's the development part that is the problem. Once in production, it is really stable.

We are a small company, so we haven't really scaled that much. We have about five departments using it and we have under 25 jobs. We're not that large at all.

In terms of creating new automations, implementing new robots, we haven't seen any issues at all. It's very simple to scale. Creating a new job, adding new robots, are both very easy to do.

All our bots are unattended, so very few people actually "use" Kryon in our company. We have approximately seven or eight developers in total during different periods of the year. Some are more active than others. For example, in finance, when it comes to quarter-end, they don't really develop. They leave the automation alone for a couple months while they take care of their busy time of the year. It comes in waves.

We have five robots in production currently. As of now, we have no plans for increasing. We've got lots of time to add stuff.

The support is really good. 

Their first-level support needs a bit of work. If we put in tickets, very often we get a bunch of questions from level-one but that information was already in the ticket. We get repeat questions. 

The only complaint I have, if you want to call it that, is that I would like to be able to pick up the phone and call someone. If we enter a ticket, by the time someone replies to it, we have continued working on our issue. The job has often changed, the situation's changed, or the issue may be resolved by the time someone replies a day or two later. Being able to pick up that phone and talk to someone immediately would be a tremendous benefit.

They don't have an extra level of support that you can purchase. There is just our client manager. If we have issues that support is not addressing quickly enough, we just escalate and then they take care of it from their side. They get someone to get in touch with us. But it would be nice to be able to pick up the phone and not even have to enter a ticket. Half of our questions could be answered immediately if we talked to someone directly, as opposed to going back and forth via email. Once it's an email, it's stretching out from a five-minute phone call to three days later before we get the end answer. I'll ask a question; they'll ask a question in reply. It goes back and forth in an email exchange.

There's no live support available unless we pick up the phone and call someone directly, but for that there's no support desk. I'd be calling our client representative who's really a sales guy. He's not a tech support guy. He would follow up with someone in tech support to get in touch with us.

With this client, there was no other solution in use. I use some, myself, as a consultant with other clients. I've been here for the last almost two years. Prior to that, I used Cherwell which is more like an IT service management, workflow-type tool.

The setup was very straightforward. Kryon dialed in remotely and did most of the work, along with our infrastructure guys. There were no issues there. It was really smooth.

They did it in sync with our guys. We had someone with the proper access and rights, so if they needed to do something on the server, for example, we had an engineer with admin rights on the call and able to assist them remotely. They worked closely with our lead engineer for IT to get it in and there were no issues at all.

The installation itself was just hours, literally. It was really quick.

It's the same with upgrades. Upgrades are very smooth and they don't take very much time at all. Kryon staff do the updates as well.

As far as the installation of application goes, there was no strategy. We just followed the steps in order.

Where implementation of robotics as a program is concerned, the strategy was to get some low-hanging fruit, some easy jobs with high ROI, and try and to show success. With that success, we rolled it into buy-in from the rest of the teams. Something else we did as a strategy was that we put a developer in each one of the departments, so it wasn't someone from IT doing the development, it was actually business-users. That way, people's peers would be designing, implementing, and developing whatever is being used in their departments. We got the subject-matter experts to actually design their own jobs. They chose what to automate, when to automate it, and then they would automate it themselves. It wasn't "Big Brother" pushing things on people. What they wanted to automate, and when they wanted to automate it was determined within the department. That created a better buy-in for implementing change and for change-acceptance in departments.

People always have their backs up against the wall if it's someone forcing something on them: "Oh, now you have to use this application." The response is often, "Well, I don't want to."

This way, it was them and their peers deciding what they were going to automate. It was much easier to get their buy-in. They determined as a group what they wanted to automate. It created a better culture for change-acceptance.

Automation Anywhere was the other one they were considering. I think they looked at a couple of others, but that was before I was here. I saw the paperwork comparing the final two and they were Kryon and Automation Anywhere.

You do need someone with some development knowledge. Not necessarily everybody involved has to know development, but as a resource, it would definitely be important to have. A straight business-user who isn't strong in IT or development wouldn't be able to do half the things that we've done. Having someone with a development background, at the very least as a support person, internally, is tremendously valuable.

As for saving time when launching new automations, we don't have anything to compare with because we didn't have an automation solution beforehand. It's new to the company. I would say our developers have gotten more proficient, so we've become quicker at development. As far as the launching now, though, it all takes about the same amount of time.

Regarding business users, with no technical background, it definitely can be used. We have users of all levels of technical skill. Business users can create some basic jobs, but there are some limitations to the product. More technical users can get around the limitations using scripting with JavaScript and the like. If people are familiar with that, it definitely makes the development phase much easier. It's totally possible for business users to use it. We've had users who have done basic jobs, but when it gets to more advanced things or quicker ways of doing things, a little bit of development knowledge goes a long way.

For deployment, maintenance, or upgrades of Kryon, there are two of us. I'm involved in coordinating and our lead IT guy works with whomever they assigned from Kryon. I'm not even necessary for those tasks. Really, just one person is required. I do the change request. I take care of the bureaucracy and the red-tape approvals and the like. Once all that's done, we hand it off to the technical team and there's a single person that does it all. He is the IT lead. As needed, he'll pull in DBAs or whoever, if the situation calls for it. He coordinates with his team.

We have legacy software in our company. Some processes in our company are being done manually. There are very routine jobs, processes where people are sitting in front of a computer and typing data. This software, Kryon, enables us to make these processes more automated.

We program the software, we run the use case with the software and now, instead of things being done manually, they're being done automatically. It's helping leave all this old legacy software which doesn't have APIs. We wouldn't be able to do it otherwise.

We cannot get into this legacy software. There are no APIs. It would cost a lot of money if we wanted to develop something like an API. This software enables us to overcome this API problem, automate things, and do it relatively quickly. It's low-cost development.

We're a bank. We get money transferred to the bank from other banks, but some of the data can be wrong. We know it's money coming to our bank, through a money transfer system in Israel of which we are a part. But if we cannot recognize which account number it belongs to, regulations require us to send the money back to the bank that transferred it to us. This happened every day. Until we had this Kryon RPA solution, there was a person sitting in front of a computer typing these transactions into the legacy system. It was all manual work and the person doing it would work, say, two hours a day doing these transactions. Now it's done automatically. 

So it's not just that we're saving the time of this person having to do this typing, but we have also improved this specific person's job satisfaction. She doesn't have to do this boring, hard work. Not only are we saving valuable time of our employees, but there is added value, like fewer typing mistakes.

The recording feature enables us to record what we're doing, like typing or clicking the mouse, and to identify objects on the screen. We basically teach the program how to type, instead of a person. That's the most powerful feature.

That's valuable for us because it's the only way we can automate this process.

I would like to see a better OCR solution. That's the main thing: identifying unstructured data, like all paper documents and data from pictures. 

Also, because we are in Israel - Hebrew is a hard language - we'd like it to better handle Hebrew.

We had some issues, but it's relatively stable. We didn't have any major issues. Their support helped us a lot. Some of the issues we had were because we didn't know how to work properly with the product. But it's working and it's doing its job. I'm relatively satisfied with the system.

We don't yet have a lot of processes in production, so I don't have experience with its scalability. I don't see any problem, why the product would not be scalable. But we don't have a mass of processes, so I can't say anything further.

So far, we have automated six processes, about one process a month. Of course, we have plans to try to put through two processes a month into production. We're planning on doing tens of processes in the next year. We want even more, but that depends mainly on us.

Technical support is very good. They answer fast and they know what they're doing. We have had a very good experience with them.

We used nothing before Kryon.

It's hard to say whether the setup was straightforward or complex. I think it's quite simple. But because of all the security requirements for data at our bank, we couldn't do it in a straight way. We had to go a very different way, so it wasn't so straightforward. I don't know if it's our fault, because of all the security issues we have, or if it's a product fault. Let's put it at 50/50.

It took about a month-and-a-half, from the beginning of the deployment with Kryon, until we solved everything, and we could run our first process in a production environment.

Our deployment strategy included internal meetings, trying to map the processes we wanted to automate. Second, we started negotiations with Kryon for buying their product. Then we started learning the tool and how to work with it. At the same time, we started installing it on our server in our company.

After we finished the basic installation of the development studio, we started developing our processes. That was the month-and-a-half. We were installing the program and dealing with all the security issues. And at the same time, we mapped our processes and development.

After we finished with them, we continued mapping and identifying the other processes in our company. Kryon has been advising us, not only about installing, but also by giving us best practices on how to map and how to identify the processes that we can automate in our company.

Kryon assisted us with the deployment. It was a very good experience. They were really committed to our success. They were very informative and helpful. They solved the problems and the issues we had to deal with. I have a very positive opinion about them.

We have definitely seen return on investment. We are checking it all the time. By the end of this year we will have returned the investment, and we will start gaining more. Most of the money goes to developers' salaries, people working at the bank, rather than the licensing. Including the salaries, we expect that by the end of this year, we'll return the investment.

For an unattended robot it's $6000 a month. Right now we have three unattended robots.

We checked out Blue Prism and Automation Anywhere. Even though we have deployed Kryon, we are still checking other solutions. Maybe they will be valuable in different processes. 

We decided that Kryon would be the best, mainly because they have the most installations and production in Israel. They have quite a lot of experience.

I would highly recommend getting a commitment from the vendor - and not only from Kryon. It's hard to get the vendor's commitment and to know, when you sign the agreement, what the SLAs for dealing with your problems are, and how committed they are to you as a client.

The second thing is that more important than the source of the RPA solution is the way your company handles the automation of processes. It's a very big issue in a company. Employees are scared they will lose their jobs. It's something you have to deal with no matter what the RPA solution: how you manage these changes in your company. Kryon and others have a very methodical way to do this by creating a center of excellence, etc. It's very important to do this even before you choose your vendor.

You need to address peoples' fears, that's the main thing. A good organization will not send people away, but will find them more valuable things to do, instead of the very routine things that RPA can do instead of them. You have to address many people at many levels, that this is something that you have from now on. Every new product, everything you have, they should know that you have an automation tool that you can use. It's very powerful. It's helping make things more accurate and faster. 

It's a change, not just because people fear losing their jobs, but in many other aspects. Even management has to know about it, about the capabilities of these tools.

The users are developers. We have two developers and I am a system administrator. This program is for developers who develop the processes. Once the processes are developed, we can replace business users in certain jobs. The three of us, and perhaps two others who are administrators of our VM machines and who deal with security issues, handle deployment and maintenance.

Automating a process involving SAP and Excel operations. Such operations require access to SAP TRX, export in Excel file, and running Excel macros.

Cuts time due to the building of a robot which runs during the night to perform time-consuming and tedious activities.

Recording user actions in SAP environment with field input and function activations, such as export to file, variants selections, etc.

I would improve the object recognition features, making it not linked to the screen resolution or the position.

No.

Setup is quite simple and not very expensive, but regarding licensing, I don't know.

No.

No.