Nintex State Machines and moving to Microsoft Power Automate

Budget and costs are always a concern especially when migrating or operating in the cloud.  We’ve recently helped clients convert Nintex Workflows to Microsoft Power Automate in order to help lower the subscription costs of Nintex.  

One of the larger challenges presented in these conversions is the state machine action offered by Nintex.  State Machines offer the client the ability to repeat actions or multiple parties dependent on an outcome. For example, a multiple party approval process that may move forward or backward through the process depends on whether the current party has approved the item or document.

Nintex workflow offered a pre-configured action to allow the users to create a state machine including the individual processes and statuses.

When migrating from Nintex to Microsoft Power Automate, there are a few things to consider, especially with a complicated workflow like a state machine.  The first is the fact that Power Automate does not have a matching action that duplicates a state machine. There are some other methods to achieve the same functionality such as a switch statement.  

Power Automate flows also time out after 30 days, this presents another potential issue if the process currently in place make take longer.  To avoid this issue in flow, we can split the Power Automate flow into separate smaller flows. One Power Automate flow will act as a controller, using an HTTP request action to call the needed Power Automate flow that will serve the actions for the current state of the machine.  Breaking up the Power Automate flows into smaller flows allows us to mitigate the 30-day timeout issue.

The ability to make an HTTP request and to start a flow via an HTTP request is a very powerful tool in Power Automate providing plenty of flexibility to fit the client’s needs.  If you have any questions or have encountered difficulty in your conversions, contact us at 724-423-9290.

Scroll to Top