As a Nintex partner, I have been playing with the Nintex Cloud preview, together with a customer that already works with Nintex Workflow for SharePoint. It was just a (part of a) day, but the following is a list of suggestions for Nintex Cloud. My role on this playground was to assess the API part of Nintex Cloud.
Nintex Cloud functionality:
I'd like to see improvements with the Nintex Cloud API. Currently, It's only possible to start a WF with start data using the API. I'd like to be able to get much more information about workflows and instances, for example for dashboarding and custom API use (abstracting the WF engine for consumer apps).
Regarding Nintex Cloud API:
Victor Vogelpoel - GeONE B.V.
Thank you for your comprehensive list of feedback. We welcome all feedback, and you'll be happy to know that many of these items are already on our road map. We are continuing to receive feedback during our Advance Preview, which we are taking into consideration as we prioritize the work we plan to take on in the coming months.
What level of integration does NWC have in mind for O365/OD4B? I'm surprised to not see this as a connector out of the gate.
I was just dabbling with the external start feature and noticed that I had no way of interacting with lists, calendars, etc.
Thanks for your feedback. We actually released the Microsoft OneDrive for Business connector last night, so you should now find that in your list of available connectors and actions.
Regarding O365, we don't currently have a connector out of the box but we do support external start, which allows the designer to trigger a workflow from an external source, as well as the ability to query a web service. We are looking at whether to build an O365 connector or build different functionality that may solve some of the same use cases, so any scenarios or feedback you have to understand the need for this would be greatly appreciated.
Thanks for the response Renai Bell!
My question really spawns from some experimentation with NWC's external start feature. I am LOVING the ability to initiate workflows from any third-part system, but at the same time work closely with Office 365 and was hoping to consume that third-party input into O365's calendar, SPO lists, etc.