Flow to Nintex

When you use Nintex workflows and you are considering to switch to Flow. Or when you use Flow and want to switch to Nintex it can be difficult to make the right choices. In this series of posts I am hoping to help you make the right decision for your organisation.

There are quite a few things that  you need to consider when you compare Nintex with Microsoft Flow. I this series I am considering:

  1. Solution architecture
  2. The operations (steps) available
  3. The UX of the development tools
  4. Cost / licence models
  5. My/Your experiences

For all of these solutions I will mainly focus on the cloud version of Nintex

Solutions architecture

When comparing Nintex and Flow there are some major differences. One of the main differences is the scope of the products.

Create a Flow

Create Nintex workflowCreating workflows and flows

Nintex very much lives within the SharePoint domain and this already starts with the way we create workflows and flows. Nintex is installed as an app in your Office 365 SharePoint Online site and Flow is completely separated away in its own application. Of course you can create flows that are connected with SharePoint’s lists and libraries but you could use Microsoft Flow to connect to many more application and create a flow that doesn’t use SharePoint at all.

But there is more. There is also Nintex cloud.

Nintex Cloud

With nintex Cloud you get more of an Flow experience.


Important choice moment: Do you want to restrict your processes to start from events in SharePoint? Or would you be looking at Nintex Cloud or Microsoft FLow

Creating your steps

In flow when you add an action you get offered loads and loads of action that integrate with many products. Most of these actiosn are easy to configure and this makes Flow very much aimed at the Poweruser within your organisation as well as your more advanced developers.

Choose an action

Nintex has the same option to add steps and as shown below you can see that it is possible to run actions into both Microsoft products like Yammer but also 3rd party integration like WordPress and Twitter.

Add steps Nintex

In both products it is possible to connect to custom APIs. Flow uses its Powerful connector model making it possible for your PowerUsers to create a custom connector through the Flow Designer interface and Nintex will let you create custom actions with Visual Studio. So I guess this is down to personal preference. Do you prefer to use Visual Studio or do you prefer to use the Designer interface that you use to design your flows.

The Nintex Cloud option you get more of modern experience

Operations Nintex Cloud

With the connector based model Nintex Workflow Cloud has followed the Microsoft Flow example and it is easier to manage your connectors and connections into your 3rd party solutions.

Tasks and history lists

As Nintex comes from a SharePoint background it will store a lot of the workflow information in SharePoint lists. With the Log in history list items are added on a regular basis to SharePoint lists. This can be very useful for debugging purposes as you can expose input and output from your steps in your workflow in your SharePoint lists.

TasksLogin HistoryWorkflows will also very often include all sorts of tasks these tasks can be approval task sand they can be other tasks that people may need to complete. These tasks are stored in task lists in SharePoint. In general this will help you if you want to present these tasks to users in any other way. e.g. through a web part on a site listing all the outstanding tasks. It is of course still quite important to manage the number of items that appear in both these lists.

Flow is slightly different here. The approval tasks are stored within databases in the Common Data Services. The flow system can get better control over the task data. Another major benefit here is that there is a single database that holds all approvals rather than task lists that are stored across multiple lists across multiple sites.

With Nintex Cloud you as the assign a task action available to you. This already feels a lot better than SharePoint based task system that the app version of Nintex has been using for years.

Cloud Task

Like with Flow these tasks are now not stored in SharePoint anymore.

App integrations

Nintex workflows has a great tool for creating forms, Nintex Forms. This will make it easy to create custom forms within your SharePoint online environment. Creating custom forms and connecting this to your workflows is one of the great benefits of purchasing both applications in a single package. I’m always promoting to use products that work together from the same supplier. With my Document Management background I found often that office integrations are the week link in Document management solutions as your Office applications like Word and Excel are upgraded and older version still need to be supported.

With Microsoft Flow the forms products, in some cases replacing InfoPath, is something that works well with PowerApps. With PowerApps you can create your custom list forms and on top of that you can create standalone apps, connecting in many of your existing datasources.

Next steps

As part of this series I will soon look at the following areas for both Nintex and for Flow.

  • The operations (steps) available
  • The UX of the development tools
  • Cost / licence models
  • My/Your experiences

Make sure that you follow my blog and you will receive an email when I post about this. To follow by blog please click on the link near the top of this page

By Pieter Veenstra

Business Applications and Office Apps & Services Microsoft MVP working as a Microsoft Productivity Principal Consultant at HybrIT Services. You can contact me using contact@veenstra.me.uk.

4 thoughts on “Comparing Nintex workflow with Microsoft Flow – part 1”
  1. Great article Peter. I did want to point out one thing that may help explain a point you make.
    Important choice moment: Do you want to restrict your processes to start from events in SharePoint? Or would you be looking at Nintex Cloud or Microsoft FLow…

    This isn’t entirely a choice Nintex put in front of their customers. They have initiation options in the O365 tool called Component Workflow that allows a workflow to be called via web service, not bound by New Item in SharePoint. They also fully support hybrid O365 to Cloud and vice versa both in product (Call Workflow action in O365 to Nintex Workflow Cloud / Create Item in SharePoint from Nintex Workflow Cloud) and from a licensing point of view – a workflow is a workflow in their workflow packs, doesn’t matter where it’s built/deployed anymore – unlimited user interactions, unlimited instances.

  2. I was just wondering about this today (why use Nintex since Power Automate delivers so much) and stumbled upon your blog. Een Nederlandse analyse; top! But only a part 1 so far? I hope you consider making a part 2. I might be able to contribute in the near future.
    I’m now using Power Automate since Nintex O365 doesn’t have a simple way to load records from Excel files (which customers use a lot), and found the debugging and tracking of the workflows much much better in Power Automate; it gives realtime updates, shows the records, gives highly detailed information if records fail to load, etc. The Nintex “log to History” is awfully clunky at best .. Groetjes uit Australië

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.