Nintex Process Platform Reviews

Our organization is a fertilizer company where we develop workflows regarding processes occurring at the plant. Most of them are safety projects, and a few other projects include off-boarding projects, travel desk project, and foreign payment management system.

In regards to workflows on Nintex Process Platform, I would rate it seven out of ten. It is a good platform to work with and many features are available. We use Nintex Process Platform over SharePoint. Most of our sites have been developed with the back-end structure in SharePoint, which we use as storage. Our data structure depends on SharePoint. We use Nintex Process Platform for process automation. Within Nintex Process Platform, there are many options available.

If you talk about saving an item into the system, retrieving items, retrieving multiple items, or retrieving a single item, you can work with attachments and document libraries. There are many other features available as well, such as web service calls and web calls where you can work with SQL Server. Over our past four years of experience, Nintex Process Platform has been sufficient for us to develop full-fledged applications.

There are multiple areas that need improvement. Nintex Process Platform needs integration with other platforms such as Salesforce and other CRM platforms. There should be actions available so we can directly integrate with these systems. Additionally, there is a gap in mathematical actions and logical actions. We need to parse data, and if we receive data in JSON, there is no action available in Nintex Process Platform to parse the data and extract data from that JSON string. Such actions and logical actions must be available in Nintex Process Platform to increase its capability.

For us, Nintex Process Platform is configurable with SQL Server, but there is no configuration option available with Oracle. We also use Oracle in multiple processes, but we have found no way to directly configure Nintex Process Platform with Oracle. We have to use SQL Server in between. We have to create a link server within SQL Server as a bypass to retrieve or post data into Oracle. There were multiple improvement points available.

Performance issues arise if we have multiple joins within the actions, which definitely reduces the performance. I would mark performance reliability at six out of ten.

Performance issues arise if we have multiple joins within the actions, which definitely reduces the performance. I would mark scalability at around six to seven out of ten.

We have reported multiple issues we faced during development regarding different actions within workflows, and we have opened multiple tickets. The support is great. I found the support to be excellent with immediate responses whenever I open a ticket.

Positive

Deployment was not difficult. Although I do not have much configuration experience, I found it easy. I easily configured and deployed Nintex Process Platform over the development server and could easily develop applications there. From development server to production server, the migration is very simple. You can export and import the workflows and forms from development server to production server without any hazards.

We are going to switch from Nintex Process Platform to other tools in the near future. During the past few months, we have evaluated many tools including AgilePoint, ProcessMaker, Nintex K2, Bizagi, Pega, FlowForma, and Info-wise. We are currently finalizing the tool which we should use in the near future. The latest tools available in the market introduce multiple advanced options such as AI-enabled agents within process development and workflow development. Nintex Process Platform is lacking in AI-specific actions. This is the major difference between the latest market available tools and Nintex Process Platform.

We automated processes within Nintex Process Platform. Before automation, we developed our processes in Visio. When we take functional requirements from business users, we first draw the requirement in Visio where we develop the full-fledged workflow and automation processes, then we map these processes into Nintex Process Platform with one-to-one mapping and use SharePoint lists as a back-end structure. We have found no difficulties in the mapping.

There are a few drawbacks with workflows. The primary drawback is that Nintex Process Platform was dependent on SharePoint Workflow Engine. Microsoft has announced that in April 2026, they will stop supporting the workflow engine. As a result, Nintex Process Platform will also become obsolete in April 2026. This is the major drawback for now.

Nintex Process Platform has analytics available regarding processes. If we want to find where the processes currently are, there are options available, but if I assign a number, I would give it four or five out of ten. Most of the time, we get stuck when trying to debug exceptions that are thrown. Regarding the BI aspect, there is no option available in Nintex Process Platform to develop reports directly. We have to purchase other tools to create analytics or reports.

Because Microsoft announced that they will stop supporting Nintex Process Platform and Nintex Process Platform stopped supporting it as well, I will never recommend Nintex Process Platform Workflows or Forms in the near future, but Nintex K2 can be an option. The overall review rating for this product is not applicable.

We use the platform to manage workflows within our organization and to build applications on top of these workflows. It is utilized via smartphones for various internal processes.

The product's primary advantage is its low-code nature which allows for rapid development without extensive coding. It provides many pre-built constructs that facilitate quick solution development.

The tool can be limiting when more complex solutions are required. Improving it to offer greater functionality and less reliance on technical expertise could be beneficial. 

I have been using Nintex Process Platform for 12 years. 

The system has handled our large user base of over 60,000 employees effectively.

We have successfully scaled the solution to accommodate many users without performance issues.

We contact technical support for issues such as security vulnerabilities and patching.

The setup was straightforward for me due to prior experience. Compared to IBM, which has a more complex landscape, K2's setup was simpler and did not present significant challenges. We use ALM tools like Azure for continuous deployment and integration. 

We also evaluated another tool but decided to continue with IBM for our needs.

Nintex helps in managing workflows involving multiple stakeholders. It facilitates proactive actions and escalations when necessary, enhancing stakeholder engagement and process efficiency.

It offers APIs and a software development kit, allowing integration with other tools and extending functionality.

I would recommend it, particularly if it can be made more accessible to business users rather than just technical users.

I rate it a seven. 

First advantage, from a business point of view, is that it's cheaper. From a development point of view, it's easy to develop because it's a low code and low code solution. And almost Nintex provides all the possible solutions in their built-in criteria. So, we have only to configure it. We don't have to write anything from scratch at all.

It's easy to learn. However, there is very little content available for the Nintex also, but they are providing their own documentation and all. So, it's easy to learn also.

Nintex is still at the starting point of integrating with AI. It has integrated with a very small piece of artificial intelligence., like only integrated with the Google Cloud.

There is a benefit, like a no-code and low-code solution. But, again, if you are a developer, especially if you are a hardcore developer, you are using your code knowledge, its skills, and all. And, suddenly, you are moving into the low-code solution, and then you will feel, like, so many things you can't achieve with the low-code solution. 

And in that case, you are looking for some custom development. And it's a little bit difficult in the Nintex area. Because they are totally dependent on the low-code solution, and you are looking at where you can implement your custom things. 

However, you can do that thing, but that will be a difficult task. Also, the outcome, whatever you are trying to get from such kind of custom development, will be a little bit difficult.

Let's suppose, like, if you are working with a medium level of data or a small level of data that will be easier to handle with the Nintex. However, the bulk data on a high level of data would be difficult.

I have been working with Nintex for the past three years. I've been able to create some really good products in different domains, including banking and insurance. Everything seems achievable, but there are a few things I'm missing. 

First, debugging can be a bit difficult in Nintex. You can't debug forms and workflows easily. This is something that could be improved in future releases. It requires some R&D. 

Second, I would like to see more integration with AI. There is some custom integration available through the gateway, but it would be great to have more AI-related features built into the platform.  

I have been using Nintex Process Platform (K2) for three years.

I would rate the stability a nine out of ten. 

I would rate the scalability an eight out of ten.

I am the only one who uses this solution in our company. I am introducing this solution in my company. However, there's a 99% chance we'll stick with BizFlow.

The customer service and support are very knowledgeable. We haven't had many issues, and the ones we have had have been resolved internally. For the few things we have needed to contact Nintex about, they have been very helpful. They have a large support team and are easy to reach. So, we are very satisfied with their support.

Positive

I used BizFlow. Nintex is more of a no-code or low-code solution. If you are thinking about a more custom solution, you will never choose Nintex. But, for a small organization and project, you can definitely go with Nintex. 

On the other hand, BizFlow can work in every scenario, in every work. It’s a little bit difficult to go with the custom things. But, you can achieve whatever you want.

Nintex is around INR 200 per license in India, which is much cheaper. Smaller organizations are always looking for cost-effective solutions, and Nintex provides local solutions with very low pricing. This is one of the main reasons why people are more interested in Nintex.

So, the pricing is affordable compared to BizFlow. BizFlow has a high licensing price, but Nintex is exact opposite and has a low price. 

I would rate the pricing an eight out of ten, where one is cheap and ten is expensive.

If you want to work in a low-code solution, then I would suggest Nintex Process Platform. But if you really want to customize on a very high level and use hard code, then BizFlow is the best tool.

I would recommend checking the feasibility and what kind of thing you want to achieve. That’s why my organization is currently using both of them and also thinking about the third one. Like, if anything is available on the market, that is more suitable with BizFlow and Nintex and comes with some other additional features.

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

Some time ago, I implemented a demo in Nintex for various use cases such as getting emails from the team, reading the email, writing the email, opening the email, and getting the attachment.

My team and I created a demo using Nintex, focusing on getting emails, reading, writing, and managing attachments. However, we did not explore Nintex Process Platform's full potential, and our hands-on usage was limited to demonstrations.

The user interface in Nintex needs improvement. It is not very intuitive and requires changes. Additionally, the deployment process should be easier.

My team and I have been familiar with Nintex Process Platform for about one year, mainly for learning.

I rate Nintex's stability as an eight out of ten.

I rate Nintex's scalability as an eight out of ten.

The technical support provided by Nintex is very helpful, which I rate as nine out of ten.

Positive

The Nintex Process Platform serves as an alternative solution, similar to UiPath. However, our company has Nintex, and thus I recommend Nintex to customers.

The installation process for Nintex required about two weeks.

The installation was supported by the distributor, and I am not certain about the exact number of people involved from my side.

Nintex Process Platform is expensive. Prices relate to both features and the professional services necessary due to our lack of an implementation team.

Overall, I would recommend Nintex Process Platform to others.

I'd rate the solution eight out of ten.

Currently, a notable challenge lies in the alignment of user experiences across the eight or nine applications within the suite. Transitioning between applications can be somewhat cumbersome due to varying user interfaces. However, the provider is actively addressing this concern by consistently rolling out updates every four to five months, aimed at harmonizing and streamlining the interfaces. This ongoing effort is expected to enhance the user experience over time.

In terms of functionality and features, the platform stands out, offering flexibility with the option for both on-premises and cloud deployment. This flexibility extends to the RPA tool, providing clients with choices tailored to their preferences. 

An advantage lies in the shared security and data infrastructure across the toolset, facilitating smooth data transfer between applications. This contrasts with experiences with Oracle, where data transfer may involve complexities such as the need for intermediary file formats like TXL or SCZ.

I have been using Nintex Process Platform for the past five years.

In the past five years, I have experienced and sold various products within the platform, and I am pleased to note that there have been no instances of downtime or performance issues. The stability of the tools, including Nintex, has been consistently reliable during this period.

The scalability of Nintex's product range is highly commendable. Positioned as an entry-level to medium-top product, it accommodates a broad spectrum of complexity in process execution. The distinction between the Flipflare and K2 products lies primarily in the level of development customization desired. Nintex Workflow Cloud caters effectively to businesses with minimal software development skills, offering a user-friendly, drag-and-drop interface with a no-code mindset. This empowers citizen developers to independently manage workflows.

The versatility of Nintex's offerings extends across the business spectrum, making them suitable for small and medium enterprises as well as large corporations. Notably, a substantial portion of Fortune 500 companies, around forty to fifty percent, currently leverage Symantec's products, attesting to their widespread adoption and effectiveness across diverse business landscapes.

Nintex demonstrates a streamlined approach to customer support with a single support email address. This unified contact point simplifies the process for customers, avoiding the complexities that may arise when dealing with different support areas for various products within a stack, a common challenge faced with competitors like Oracle.

Moreover, Nintex offers a robust 24/7 support model, distributed across approximately seven or eight countries. This ensures comprehensive coverage and responsiveness, particularly valuable for enterprise customers requiring round-the-clock support. In the event that an issue cannot be resolved during regular business hours, Nintex commits to addressing and resolving concerns promptly, even outside standard business hours.

I would rate Nintex's support services at a solid eight to nine. I've encountered minimal issues, and the responsiveness has been exceptional. For instance, when dealing with a site license expiration on Black Iris, I reached out, and the matter was resolved within twenty minutes, showcasing their efficiency in handling such situations.

Moreover, for more intricate technical queries, I've escalated concerns to the country managers. In one instance, needing support on specific technical elements and integration nuances, a single conversation with the country manager facilitated a direct meeting with the development team responsible for the product.

Positive

The configuration process with Nintex, especially when using the online tool, Fluent Cloud, is straightforward. While there is some initial configuration required, what sets Nintex apart is its excellent online help feature. Unlike some other platforms, Nintex provides not only articles but also a wealth of how-to videos integrated into the help section. This approach caters well to users, particularly millennials, who may prefer visual resources over traditional manuals.The deployment flexibility offered by Nintex is a notable advantage, supporting both cloud and on-premises models. In my experience, I have worked with both deployment options.

Presently, there is a discernible trend among clients, with a majority leaning towards cloud deployment. This inclination aligns with the prevailing industry shift away from extensive on-premises IT infrastructure. Many clients are actively seeking to streamline their operations and reduce the complexities associated with maintaining large on-premises setups. This shift is particularly evident in the financial services sector, where organizations are committed to leveraging cloud solutions to diminish their reliance on in-house hardware infrastructure. However, it's crucial to acknowledge that concerns persist, especially regarding incident management and disaster recovery. These considerations play a pivotal role in decision-making, prompting some clients to carefully evaluate the implications and safeguards in place for such scenarios.

Regarding the deployment duration for Nintex's workflow, it's challenging to provide a precise timeframe, as it hinges on project specifics. Generally, Nintex's workflow tool is relatively uncomplicated, enabling users to get started with just a few days of training. In comparison, other tools like Automation Anywhere and Oracle often demand multiple weeks due to their inherent complexity.

I would rate Nintex at a solid nine. In my assessment, I haven't come across any automation workflow vendors offering solutions significantly better than Nintex. When examining industry evaluations, particularly from renowned sources like Aragon Research and Forrester's WAV leader report, Nintex consistently stands out in the top quartile for digital business platforms and wide deployments. The recognition extends to other reputable organizations like Gartner and CRM, further affirming Nintex's position as a leader in the field.

So we have a process flow for which we wanted to use Nintex Workflow. So in SharePoint currently, we have set up that Nintex Workflow. So users used to submit and raise requests in the solution, and that is used to trigger the automatic workflows on the fact that a ticket is raised. Then, the approvals are taken. So all those things we had coded in Nintex Workflow. So, the solution was for some kind of an approval process within our company because there are multiple stakeholders, so it goes to multiple stakeholders for approval, and they approve it. All that happens when working with Nintex Workflow.

Within Nintex Workflow, I think the automatic triggering of the multiple workflows and the setting up of the auto trigger of those workflows are some of the valuable features of the solution. So that is nice.

I think we could have more interfaces with other applications. So I think it was lacking a little bit in its multiple in-house processes and other processes. So there is a little bit of a gap in collaboration.

I have experience with Nintex Workflow. I have been using the solution for a year. I am a customer of the solution.

I rate the solution's stability a seven out of ten. Sometimes it breaks, and then we need to manually restart Nintex Workflow, so it had that kind of intermittent disturbances.

I rate the solution's scalability an eight out of ten. There weren't any scalability issues, really. I think that we found it to be a little bit of a scalable device, but we were not able to achieve it. So there were limitations. So, maybe on the SharePoint side, there would be a limitation that we can raise only these many requests, and the space is about to get full. So that kind of scalability issue, I can remember.

In my organization, around 1,000 users were using the solution.

I never contacted Nintex Workflow's support team.

I think the initial setup is fine.

To those planning to use it, I think it's a good tool to start with.

I rate the overall solution an eight out of ten.

We primarily use K2 in conjunction with Kaltura within Teams. We use Kaltura for expenses, email cases, cash advances, retirement, and company management. For company management, it involves addressing issues with account numbers by coordinating with the bank. The login use cases help log those requests and assign them to the responsible users for resolution. We also use K2 for FX services, making subpoenas, and handling hard decisions or licenses. File onboarding requests are not as frequent.

There are a lot of apps in K2, but what I really found that needs improvement is the management section of K2, especially the management server and the admin page where you can manage processes, add users, set security fees, and add licenses.

The reason for this is because the part that is the section of administration, particularly the management called rows, has multiple rules, as many as you want. For instance, you may have around 200 rules, and when you view them, only the first ten are displayed, and you have to click next to see the next ten and so on until you get to the hundredth rule.

On that page, as of today, we only have what we call to fetch, where you can search for a particular rule you're looking for, or else you have to keep clicking until you get to the final page you want. So that's a bit challenging. 

We've been using K2 for five years now. The version we're currently using is 5.3.

K2 is very stable. Actually, we've been using it since 2017, and we haven't had any issues. More than 2,000 people are using K2 in your company.

When it comes to K2 applications, it automatically has access to your active directory to prevent users and the organization from signing up separately. So if you are in the active directory, you can access the platform. And if you are not in that directory, you don't have access. Every access to K2 is controlled by the active directory, making it very scalable.

We opted for K2 because K2 is very easy to use, and it gives you room to customize the way you want your forms to look and the way you want the data to be presented, whether as PDF or SysTrack. It's very easy to use. And we can assign tasks to certain users of our products to review what has been initiated and then approved. So all those things remove the paperwork within the organization. That's the reason why we opted for K2. We don't want the files to be passed around from one person to another. We are just removing that hassle and trying to automate the process using the K2 application.

Setting up K2 is very easy. Before you set up K2, there is a guide that you need to follow, which tells you what you need to do for a good setup. For example, for K2 setup, you need to have your email exchange or SMTP ready, and you need to have your URL mapped. 

There are certain things that you need to have ready before you install the K2 application on your on-prem service. We have documentation on our website that guides you on what you need before you can install K2. So, it is also easy when you have everything ready.

In terms of price, I would say it's affordable.

I would definitely recommend using K2. I would say it's a perfect use case. I would even go as far as saying it's a great choice.

I would give K2 a ten because we have been using it for the past five years without any major issues. Of course, there are some minor issues, but they can be easily resolved. We have the capability to solve them ourselves without relying on OEM support.

K2 provides a straightforward interface, allowing us to configure rules for form controls according to our business requirements. It's user-friendly, and even a ten-year-old can understand how to use those rules.

It's easy to configure your set of rules to make the form controls work perfectly, removing manual work and making processes seamless. You can approve requests from anywhere, whether through a mobile device or even when you're away from the office. It's very convenient.

The main use case is accounts payable. We also implement it for human resources processes like onboarding and insurance plan changes.

The capacity to integrate with external platforms. It's great to be able to call web services or other external services.

There is room for improvement in the user experience in the forms. When we need to develop the forms, we don't have much customization, and I think we need more flexibility there.

It's technically difficult, but it would be great to be able to develop our own code and integrate it into the platform. We could then run our own code for specific actions and requests or even develop a page or form. So, if I can ask Nintex for something, it would be a way to integrate our own code for specific actions. 

When it comes to integration, it could have more options for custom requests.

We use Nintex Workflow Cloud. I have worked with the Nintex Process Platform for two to three years. 

I would rate the stability an eight out of ten. 

Scalability is a limitation of the product. It's not so easy to scale. I would give it a five out of ten. 

I'm an integrator for Nintex. So, the number of users depends on the customer. But we have thousands of users across all our customers.

So, it's suitable for enterprise-level companies. It's more suited for enterprise level, not for small or medium-sized businesses (SMBs). It's too expensive for the SMB market.

The quality needs improvement.

Neutral

I used Microsoft Power Platform.

Power Platform is better. It has more options and flexibility, even though it requires more technical skills to implement. 

Nintex is easier to implement and more user-friendly, but Power Platform can do a lot more.

The initial setup is simple. We have both hybrid and on-premises. We have all kinds of implementations.

Integration: For a technical person, it's quite simple. It could have more options for custom requests, but in general, it works fine.

The deployment process takes a couple of days.

Saving time is the biggest benefit. It gives the customers the flexibility to solve simple automation problems quickly. 

It saves time for both the employees and the company's administration.

I would rate the pricing for Nintex Process Platform as four out of ten; one is high, and ten is low.

It is pretty expensive.

I would recommend it for specific use cases. If it's something simple, I would recommend Nintex. 

For a large number of users, I recommend LeanIX. 

If it needs to be complex, I wouldn't recommend Nintex. I would recommend Power Platform instead.

Overall, I would rate it a six out of ten. 

We use the Nintex Process Platform to connect internal users across different departments, streamlining workflows and collaboration. As an international organization adhering to evolving standards, Nintex provides a flexible and scalable platform that integrates seamlessly with the Microsoft ecosystem to build a comprehensive collaborating environment. It serves as a fundamental layer, enabling efficient communication and data exchange among our teams.

The latest version of Nintex has many features. We have a clear roadmap and the necessary application to integrate it into our platform.

The solution does not integrate with many platforms.

I have been using Nintex Process Platform for several years.

I rate the solution’s stability a nine out of ten.

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

We have the consultant doing the deployment.

The initial setup is straightforward. It depends on the situation and the context of workflow. I take one or two days to complete the setup.

The solution doesn’t have an extra fee. We are compatible with the package.

Nintex is running much smoother after installing the new version of Nintex Connect on our platform.

While we initially tried using consultants, we found it more effective to collaborate directly with our users. This user-centric approach has helped us identify key technical aspects of Nintex.

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

It has a lot of features for creating and managing workflows, as well as for integrating with other applications. Nintex offers features, particularly to ensure a user-friendly experience.

At times, issues arise in certain scenarios. In such cases, the versioning can become quite difficult. There may be no other way but to restart the entire process or rectify it at that point.  

So, there is room for improvement in terms of the stability of this solution.

In future releases, Access-related features are important because a lot of data is stored in Excel in most organizations. So whenever we need to upload this data, we need to have workflow features that can validate each row and other data before inserting it into the software system. These features are not available in the standard version. We are not looking for a one-time import of data. Instead, we want to be able to process the data in real-time using DXL. This is one of the things we are looking for. 

The second is the ability to create Word reports. A report that is created in Microsoft Word.

This is a very common type of report, and it is used to present data in a clear and concise way. I would like to be able to create different types of word reports, such as listing reports and formatted reports. But Nintex does not provide any control over MS Word to control and format it. I would like to see MS-related connectivity with Nintex Workflow.

I have been using this solution for more than six years. However, we used the on-premise version, which had certain limitations in comparison with a cloud version. 

I am satisfied with the customer service and support.

Positive

We have worked with Nintex and SharePoint.

The solution is expensive compared to its competitors. 

We are actually in the process of evaluating low-code tools in this space. We are looking for a private cloud under the Azure cloud environment. 

The on-premise version of Nintex Workflow was good for the workload that we were using.

However, the trend has changed, and now all the features are available on the cloud, not on-premise. So we have to move to the cloud.

We are cost-sensitive, so we can't just move the tool to the cloud directly. We need to evaluate and understand our requirements first. And since we are in the pharma industry, we need to make sure that the software is compliant with Part 11 regulations. For Nintex and other products, we need to develop them with those features in mind. So, that's an additional layer of customization that is required for all these platforms. That's why we are looking for a ready-made product that is compliant with Part 11 and FDA regulations.

So it will be easier for us, and it will reduce the need for customization. So in that sense, we are basically evaluating the different options. It was never a key factor for us, but we are not happy with Nintex, so that's why we are not considering it. This is the product we have been using for the past 6-7 years, and it was one of the best ones because it integrated well with SharePoint. We hardly had to do any customizations in SharePoint because everything was created locally.

If I consider the standard version, I would rate it eight out of ten. However, the enterprise version has some additional features that I would like to use, but the cost in not so fair. So if I factor in the cost, I would rate it lower, maybe around seven out of ten.