Microsoft Power Automate is an advanced automation platform offering a range of features, including AI-powered automation, robotic process automation (RPA), business process automation (BPA), digital process automation (DPA), and process/task mining. The platform aims to empower organizations to securely automate their operations at scale by leveraging low-code and AI technologies.
$15
per month per user
Nintex Process Platform
Score 8.5 out of 10
N/A
Nintex offers a platform that helps companies discover, automate, and optimize business processes.
Power Automate is very well integrated with Microsoft office 365 suit, Teams channel and SharePoint online. The workflow UI is very user-friendly and the users from non-technical background can easily understand the tool and start automating any simple and complex workflows. …
Power Automate is a no-code/low-code solution tailored for workflow automation, data integration, and AI integration, making it an excellent choice for Microsoft-centric organizations. OutSystems, on the other hand, is a comprehensive application development platform, offering …
I have many years of experience with Nintex applications and it stands up very well against Microsoft Power Automate. I hope Microsoft Power Automate can become the better workflow application. With the Integrated AI builder and continuous updates I expect they can become the …
Nintex is a more powerful workflow tool, but Microsoft is closing the gap with Power Automate. Microsoft Power Automate can do simple tasks very well, and they both can connect to multiple other systems very easily.
Both have their use cases. Nintex Automation Cloud allows external users to submit forms, which Microsoft PowerAutomate or PowerApps doesn't allow. (Power Pages is very costly)
We had a requirement to get all members of an AD group from Azure AD into SharePoint online list which Nintex Workflow for O365 can't do it and we chose Microsoft Flow to perform that action.
In my opinion [Microsoft Power Automate (formerly Microsoft Flow)] is heads and shoulders above Nintex. It was much easier to learn to use and had a much cleaner UI. Nintex and Power Automate both had connections to a lot of platforms but since we used a majority of Microsoft …
Nintex is far easier to use, both O365 and Cloud versions, than Microsoft Power Automate. Nintex used to fall short due to not having the connectors that Flow has, but their Cloud version is catching up very quickly.
Nintex is well suited for highly big enterprise apps, it does come with its own cost and challenges as well. [Microsoft Power Automate (formerly Microsoft Flow)] is greatly suited for creating simple to medium workflows and automations that can be done at every department level …
Power Automate is much easier to learn than Nintex Workflow, with much easier ability to test and debug. Nintex however has a much better workflow approval process with more mature functionality.
Like all plugin type enabler programs, Flow bridges a gap that SharePoint couldn't fill on its own. SharePoint allows for some helpful automation of collaboration, but where it falls short is where Flow has an opportunity to elaborate. On-Prem Nintex and SharePoint 2016 are …
We selected Microsoft Flow because we are Microsoft house. But regardless of that fact, the outside software and services it can interface with is what i feel really sets them apart. The multitude of actions and triggers included in Flow as well the interface is where Flow …
Nintex Process Platform was and still is by far the most flexible and easy-to-use than any of the other form creation and workflow designer apps we looked at.
Nintex Process Platform is much easier to begin with as low code or no code tool, which reduced amount of time and effort to learn and we can start working on it within a few weeks after taking the training session with Nintex. We can build the same application with same …
We got Nintex before microsoft flow was around and K2 at the time was more expensive and didn't have the mobile apps option. SharePoint is licensed per SharePoint Webfront end WFE server and we only had one WFE server.
microsoft flow and power apps requires additional conenctor …
We use Nintex for any workflow that interacts with our users. It provides a much more professional and clean interaction and is easier to design that Power Automate. Power Automate is better at handling some technical scenarios and has good error handling capabilities, but …
Nintex Process Platform is a very affordable and economical tool as it reduces time wastage and operational cost, unlike its alternatives. This tool offers outstanding and responsive technical support services to its customers.
Once you have O365, the obvious choice of tools would be the ones that are part of the platform and are included in your subscription, like PowerApps and Flow. Still, we often choose Nintex Process Platform instead.
Regarding forms, Nintex Process Platform provides a more …
I used SharePoint Designer and Microsoft Visual Studio. We are testing also Microsoft Office 365 Power Automate and Power Apps which are in a competition to the Nintex Workflow Cloud. K2 was not tested but in the focus, at the end the pricing was to expensive for small/mid size …
Nintex is still ahead of the curve on many of its competitors for a number of actions they offer. We do frequently evaluate other tools as many other offerings are rapidly closing the gap. Microsoft Flow has come a long way in the past year and I foresee them giving Nintex a …
Nintex just works and has been working for the past 12 years. It's very easy to use, very efficient and productive. I'll say it's the No1 Digital transformation platform in the world.
Nintex Process Platform is great for more complex and heavy processes as compared to some other similar tools. Additionally, it offers great support in case of any issues.
Power automate offers tough competition to Nintex Process Platform when it comes to citizen development, since MS pushed that option right into the SharePoint list.
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 …
Microsoft InfoPath. We felt InfoPath isn't as flexible and the functionality it offered was limited compared to Nintex. Also there was information that InfoPath was going to be discontinued (at that time).
Nintex is easier to learn than PowerApps. Powerautomate has better performance and flexibility than Nintex Workflow. We selected Nintex for its mature capability and "no-code" functionality.
These used to be great tools until the new pricing model made them really painful and expensive to use. Nintex pricing is more reliable and we can plan better.
Also PowerApps/Flow don't seem as intuitive to learn, they need some 'development' background.
ITLAQ's SPARK/SPARKnit is not in your list of products. SPARK provides all of the basic functionality of Nintex forms and workflow at a much smaller price. The Microsoft Power Platform is inexpensive, but slightly more difficult to use.
Microsoft Power Automate is the best tool to extend Microsoft services you already use. Hands down. Prototyping workflows is very easy in Microsoft Power Automate. It's also the best choice for sending custom cards through Teams and email. It's the easiest way to get data from Microsoft Graph.
Nintex is best suited when processes are drawed by the business and then can be furter enhanced by IT professionals. When only used by business units we see that there are some lose ends in processes and some bagic process knowledge is needed. Therefore it is wise that the persons in the business who will use Nintex have some basic knowledge on how to set up business processes
Adding Machine learning features like the "Image and Text Automation" component, which allows bots to extract data from unstructured sources like scanned documents or PDFs.
Natural language processing (NLP) features to understand and interpret human language, which can be useful for tasks like customer service or data entry. mostly for middle east countries where Arabic language is used.
Integration with external systems where many industries uses their own legacy systems and they need RPA bot to interact with their systems as well.
Adding More OCR tools for Document data extraction and dynamic content.
The tool is very useful when used with its various native connectors, taking great advantage of the integration between the components and systems of the Office365 universe. However, its cost is still high, and automation using more advanced components containing AI resources becomes unfeasible for some companies. Due to the financial crisis that many companies are currently experiencing, investment in automation systems or tools is taking a back seat.
We are currently investigating which collaboration platform best suits our needs. Chances are that we move to SharePoint Online and then we're going to also consider the microsoft power platform (power automate and power apps) to develop forms and workflows. Aspecially the pricing model for the cloud is currently a blocking factor to go for the Nintex solution in the Cloud.
Power Automate has an intuitive interface that is easy for novices to use. It doesn't require programming knowledge, however having that experience will help troubleshoot potential issues if they do arise. There are advanced features that allow the use of "code-like" steps that will help power users get more advanced automations set up quickly.
Based on the on-prem experience with this tool, I believe that they have a lot of potential to help the online version catch up to where the on-prem left off. Nintex developed their online version and it is not as fully formed or capable compared to the on-prem version, and the licensing model scales back what we would have liked to be an expansion or at least continuous improvement of existing flows. It is also not near as user friendly specifically to non-developers and has an uncanny similarity to Microsoft Flow in the online instance. Consistent with my reviews of the tool - I believe they have some good approaches to design thinking that, if translated well from on-prem to online, could make this a clear winner again.
The Nintex Process Platform has never crashed or had any availability issues during my usage. However there was an issue that was of my own making that caused a slowdown of the system. I had set up a process to run once a day and check for employees on a list that had certain parameters selected, and for some reason that I had to troubleshoot, the process instead ran constantly, which filled the cache quickly. I ended up having to dismantle that process so the system didn't crash.
Unlike any other process automation product out there. Not only is it a low-code, easy to use tool for building processes in environments like SharePoint or Salesforce, they have really started to expand their tool-set by offering tools to manage other things like process mapping, RPA, mobile,etc.
both Community support and Microsoft official support typically respond to (and resolve) reported issues in a VERY expedient manner, usually going above and beyond for education and bugfixing. I have been thoroughly impressed with the level of support I had been provided in the past.
The support team works as fast as they can and they are usually fast to solver the issues. Sometimes they need more time to solve one of them because our workflows and so on are more complex than usual clients.
after reviewing the main features of Power Automate, the Microsoft trainer focused on some of our real life use cases implementation, from simple to more advanced.
although it was productive, it is more difficult to stay focused and in a 7 hours a day online training (including screen share issues and the fact that the trainer just can't precisely show the exact location of your mistake)
I used the Nintex training software, it was easy to watch and follow along. It didn't go too fast and was descriptive enough to understand what the steps needed were in order to produce efficient workflows and user friendly forms.
I had to migrate from Robocorp to Power Automate. The automation was using API and sharepoint. So it was better to use Power Automate instead of Robocorp so we did the migration. in some areas the migration was easy but creating flows and making it smaller codes was difficult. Debugging the code was tough so we took lots of time.
test runs for key persons to insure the system is set up prior to rolling out I think the platform is good, I think the roll out and the local implantations is where we are failing as a company in using Nintex
Power Automate is a no-code/low-code solution tailored for workflow automation, data integration, and AI integration, making it an excellent choice for Microsoft-centric organizations. OutSystems, on the other hand, is a comprehensive application development platform, offering rapid app development with both low-code and traditional development options. This platform is well-suited for organizations seeking custom application development. Nintex specializes in workflow and process automation with a strong focus on SharePoint and Office 365 integration. It also includes advanced features like document generation and robotic process automation (RPA).The choice among these platforms should align with your organization's specific needs, considering factors like integration requirements and the desired level of technical expertise. In the bottomline, it's up to cost and licensing.
It's much more reasonably priced and we were able to actually experience the platform for a bit before we made a decision. And by the time our demo was finished we had already started depending on it for some of our processes so it would've been very hard to separate from it
The scalability is really bottlenecked by the imagination of the user. I was able to make processes for my own personal usage, making my daily tasks easier. I was also able to make processes that affected hundreds of employees, making large standardization and efficiency gains. So either way, the system is used the same way, and I was the limiting factor.
We have saved our company thousands of dollars by creating our own customer support system rather than using a 3rd party tool.
The ability to generate documents/PDFs in workflows has solved a great number of process issues for us and groups who had previously been using paper documents.
Automating many permissions updates through workflows has been a huge time saver for repetitive processes.