Overall Satisfaction with Nintex Process Platform
Nintex is used for business process automation across several business units. It is used within a SharePoint Online context. We are in the process of completing migrating workflows from SP 2010 to SPO. Nintex is being used in cases where an existing process was automated with an older version of Nintex. New needs for process automation are being satisfied using Power Automate when possible. But we feel Nintex is often easier to use.
- Ease of use.
- Breadth of actions\conditions.
- Backed by good support and training.
- Enterprise Pricing - not per user or per process.
- An improved "superior position" story in relation to Power Automate.
- Feature parity to Power Automate—I realize this is overly broad
- An easy, robust method to create custom actions.
- A positive is that business processes have been successfully automated thus achieving business objectives.
- A positive is that automation has reduced the manual effort required and improved output quality.
- A negative, not due to Nintex, is that ROI has not been measured. No baselines or improvements have been quantified.
We use Nintex within the context of SharePoint Online, and the M365 environment in general.
Some, but not many, non-IT staff persons are using Nintex designers, but are able to do so only after training\hand-holding from a technical resource. And, the effort often requires additional hand-holding to achieve the desired results.
Technical staff thinks Nintex stacks up against Power Automate well, short of a string "Connector" story and it is at a disadvantage due to Power Automate being "part" of M365 marketing against that is near impossible. For the most part, we have kept the Nintex platform because of legacy usage. Despite the pricing model of Power Automate, we are using it "by default" for new process automation.