Nintex Process Platform Reviews

Well-suited: our entire digital transformation process has been made so much easier using Nintex, from the ease of building forms to the power of creating flows. Having a consistent interface is really huge too, because so many of our users are not very technologically savvy, so giving them a familiar form makes training easier and lowers resistance to change.

Less well-suited: for just a really "dumb" form that the average user can create, with no workflow behind it, we have them use the O365 forms. That way, they can get a results breakdown without a workflow behind it and we don't have to provide much support for it.

It does everything you need it to do but doesn't do it in a user-friendly and quick way, so it's difficult to really recommend, however, based on the options out there it's the most cost-effective platform to offer the number of features it does offer. For example, it doesn't work with the Salesforce Process Builder and uses workflows and alerts to handle automations. But letter generation works, however, this side of things can break if the relationships aren't set up properly, which again, takes someone with a good understanding of the platform, so not user-friendly for the everyday user.

Our use case is creating forms directly from Salesforce. If anyone is looking for an easy way to create Acknowledgement Letters, send them to the appropriate person, and log that the letter was sent I would highly recommend Nintex.

Nintex process is well suited for complex approval process and forms. Considering scenario, if we have more than 10 to 12 level approvers and each approver takes time to approve the request and the reporting for approvals needs to be generated via approval dashboard, Nintex Forms with Workflow is well suited for that complex scenario. Also, implementation and maintenance are easy compared to OOTB workflows and other tools coming from the Power Platform. The beauty with Nintex is it is tightly coupled to the Office 365 suite and doesn't leave the scope. Even though there is licensing cost involved, in the end, it saves other development and maintenance efforts that could be caused using OOTB approaches.

If it is a simple approval process, like collecting feedback and simple approvals, and audit approvals are not required, this still can be implemented using Nintex. However, it could be costly because of Nintex's license charge incurred per workflow and on a per-year basis. This kind of scenario can be easily achieved by the MSFT power platform, which comes to users via organization subscriptions.

I believe that Nintex Process Platform is well suited to a use case where those who are implementing it are fairly tech and software savvy. The platform is fairly robust and can be customized to a significant degree, but it does take some time to familiarize oneself with it fully. I would say that where it is less appropriate is for users who are not power users and would struggle with customizing the system to adapt to their needs. Such users would likely struggle with the UX and become frustrated.

This is really well suited because of the following advantages:
1) It instantly transforms data stored in Salesforce CRM into mission-critical documents - like Quotes, Contracts, etc.
2) Very smoothly integrates with a Salesforce CRM org via App Exchange managed package.
3) Support is really good, you get a response within a few hours of raising the case.

This is not my first time using Nintex. I have used it for years and when people ask about Nintex and other systems, I always seem to fall back to Nintex because of the ability it has to make things work. I always tell people that with Nintex, the limit is their imagination. If they can imagine a software process then it can most likely be built into Nintex Process Platform.

With Nintex Forms, you can create dynamic online forms to capture and submit accurate and current data from wherever you are. User-friendly design canvas, drag-and-drop controls, and advanced business logic make it easy to customize forms.

Nintex workflows: Do not use Nintex for small approval workflows. This can be easily done with Microsoft standard workflows.

We have found it's great to remove phone calls to the IT team, we take far less calls with a self service portal. It also creates users pretty easily in O365 so those little tasks have been taken away from the team so we can improve other systems rather than fix users issues/update details. I can see how this could really help other departments and we are looking to add it to these areas soon.

We tried to automate licensing but the XML querying is awkward and we find repeating sections hard to work with if you want to get data out of it.

Nintex focuses on process automation and they are very good at it. Any business process an organization has that requires approvals and especially where those approvals vary (e.g., higher request PO amount requires more approvals) are well suited to automation with the Nintex Platform. Nintex also has a robotic process automation (RPA) tool, which allows for automation of manual processes using any software accessible by a user's workstation. And Nintex offers a process mapping tool that allows organizations to map business processes (manual or automated) in a standardized manner in a central portal.

Nintex Platform is well suited for form design and workflows--great and easy to use, also Nintex Sign. Nintex Foxtrot RPA is a heavy software and not easy to use!

I like what it does, but hate supporting it. It takes so long every time someone asks for updates and I really don't understand how to implement

Well suited:

• Process and approval digitalization, user handling, and workflow optimization like HR processes or rebuild automation for the approval matrix.

• It's well implemented in the system architecture with Microsoft products.

Less suited:

• Some parts that are useful are not implemented in the on-prem version of Nintex. What is in some parts is making life a little bit difficult because user finds the solution in the cloud version and wishes that it was also possible in the on-prem version.

• Some technical scenarios are not possible. For example, ADFS or something similar, but that's not directly a problem from Nintex itself. This is a mix from Microsoft and the engine.

Nintex Platform is well suited for SharePoint. We have used Nintex Planform in several departments for lists and forms to allow for rich user experience while being able to control how the form works. The workflows have provided many instances of turning manual processes into automation, such as paper forms being filled out now use Nintex Platform forms with workflows behind the scenes that notify the owner of the document. Agents can fill out information through a form, and the information is sent through a workflow to our department, agents can request a calendar appointment through SharePoint, and Nintex Platform creates appointments on Outlook.

I have had to contact Nintex a few times regarding questions or issues about the product. I have always had a technician respond within a few hours, and they continue to reach out and ensure that the problem is resolved before closing the request. The technicians are knowledgeable and helpful.

Nintex is great to use as I've stated before, and I implement it for business users company wide. It has allowed for automation of so many manual processes and created ease of use while maintaining a nice user interface with the forms. The business users enjoy the forms that they work on and the automation that takes place.

Nintex allows for several things to be used in making manual processes automated. It can be used for simple things such as small SharePoint lists to large scale projects such as extensive workflows and forms.

Nintex is an extremely versatile platform and can help drive automation in any area of your company. We are considering it for our onboarding and off-boarding processes.

Nintext Process Platform is great for automating certificates and other processes!

One can run Nintex Platform as a workflow owner; you can define exactly which roles/people/groups can have access to an item at any given time during the workflow process. You're lucky to be in an organization that only has 1 regulated process in SharePoint.

From our company's perspective, we can save at least thirty percent in terms of time spent on manual processes, and documenting approvals and process flows.

It helps in:
Drag-and-drop workflow editing.
Superb workflow automated and logic rule creation.
Built-in task assignment and management.
Strong integrations.
Native Nintex Mobile app.

By having all the information at our fingertips, our organization could make informed decisions about what to automate, how quickly to make it happen, and where one could encounter stumbling blocks.

This is great for pre-filling contracts for Salesforce. Once you build the template, it is very easy to make updates. In our case, the state will update the forms every few months so its very nice that I don't have to completely remake the document every time.

Currently, I give Nintex Process Platform a rating of "1" because of the missing ability to trigger a workflow when a field changes. This was present using Nintex on SharePoint On-Prem. It's missing for the Office 365 version.

The Workflow designer allows the creation of processes that are much more complex than "out-of-the-box" SharePoint. However, you should be cautious of trying to build in too much complexity.

Nintex Process Platform is a good start for many automation efforts, but teams will likely need additional tools beyond that.

Nintex Forms is well suited for customizing forms to make them more friendly and appealing to the end-user compared with the default forms provided by SharePoint. It is also very good for creating workflows to digitalize daily work processes. These enhance the productivity by several folds. Nintex Forms and Workflow are strong points of the Nintex Platform.

Very suitable in approvals, docs review, feedbacks, document generation, and Hr operations like scheduling interviews, and managing candidates. As well as employee onboarding, access management, and data deletion. Not very suitable for managing FOs that should generate multiple child items.

Nintex is best-suited for customers with lots of small, simple workflow needs and where cost isn't an issue.

Nintex Platform does integrate well with MS Office 365. Users are easily added to workflows and forms and the SharePoint integration is well done. However, critical functionality is missing. For example, a form that has calculations between fields can't be printed by the user (this is called the "Responsive" form) and a form that does have print functionality (called the "New Responsive" form) will not calculate simple formulas. Nintex support is unable to provide a time-frame for when this critical issue will be resolved despite acknowledging it months ago. The only case where I would recommend this to a colleague is if they had simple forms where Office 365 and SharePoint integration were needed but required no calculations.