The existing action to externally start a NWC workflow from O365 requires the full start URL with token - the main issue with this is that the url has to be hardcoded, so the only way to replace an expired token is to open the workflow and update it manually.

Even with one workflow this would be annoying to keep track of and you'd have to schedule a day annually where you refresh the token and replace the url (else the 365 workflow will start failing to call NWC), however many of our workflows call NWC more than once, then there's the issue of keeping track of these token epiries across all projects. This maintenance is tedious and time consuming.

Solution 1

Allow dynamic input (variables, list lookup) in the start url field. I understand the existing action is set up so the entered url can be looked up and the startdata schema returned to show the available input fields (which frustratingly don't support array data types, but that's a different issue), however I feel like as long as the user has entered a url first, the schema should generate then stay fixed (ever after url changes) unless they explicitly click a button in the action config to fetch the latest schema.

This would allow users to update the token from a separate list (or variable) without having to re-enter all their startdata fields in the wf action config again. While this eases the process it doesn't solve the issue of needing to manually remember to regenerate and update the token.

Solution 2

Completely rework the 'start NWC workflow' action to use a connection and a workflow dropdown. Connection dropdown should allow for NWC connections to be created in the connection manager - selecting a connection then populates a workflow dropdown with all the external start workflows the authenticating account has access to. When a workflow is selected from the dropdown, it can pull back all the startdata fields. Ideally the connection could store tokens, and manually call the NWC API to regenerate (and replace) any expired tokens making the process completely automated.

This would be a far simpler user experience and also completely remove the need to manually regenerate and update the url/token when calling NWC workflows from 365.