5 - Nintex Workflow Cloud
-
Add connector to Google Drive Team Drives
Google Drive connector only supports personal drive access. To use NWC in enterprise environment with Google Drive, Team Drives access is required
5 votes -
Add Tables to ServiceNow Connector
The addition of the ServiceNow connector is HUGE for us! However, the major of usage for Nintex forms is with Call records, and/or Incidents.
I'm requesting that you add the Calls and Incidents tables to the available tables options in the ServiceNow connector configuration.
6 votesThank you for the feedback Joshua, I’ve added this to our backlog. I feel we can deliver this within the next 2-3 months, I’ll keep you posted on the status.
-
Collections and open API the problems
There should be bi-directional linkage between arrays containing items as object and collections in nintex.
Open API v 3.0 should be supported.
1 vote -
Box - 'Share Folder link' action
Box - Share Folder link action:
This is supported in the Box API so can we have a 'Share Folder Link' action (or make the existing 'Share file link' action applicable to both scenarios) so that the share link can be used to update other line of business systems such as Salesforce?
7 votes -
Please add an Exchange Online connector
Please add Exchange Online triggers and actions to Nintex Workflow Cloud. I would love to be able to use the following examples:
- Run workflow when an email is received
- Move email to folder
- Get email
And I also would love to be able to get these ability for Office Group Mailboxes.
72 votesWe have recently added an Exchange Online connector.
We are not able to start a workflow based on an e-mail yet, but this will be coming later this year as well.
-
Add Oracle Connector to Nintex Workflow Cloud
Will you please add an Oracle Connector to Nintex Workflow Cloud that would permit workflows to log in to an Oracle database as a user and perform tasks that the user is authorized to perform (e.g., Create, Read, Update, Delete, Select) operations? Thank you.
40 votes -
Call a web service action with credential/token from existing connector
Most of the REST API endpoints required to supply Authorization: Bearer as part of the Header, if a different version of the "call a web service" action is provided with the capability to make use of the Connector(s) in Nintex Workflow Cloud, that will open up the opportunity of all available endpoints of the external system to which we are integrating with.
e.g. All the Actions of the Sharepoint online covers only few endpoints of the Sharepoint Online. The proposed version of "call a web service" will make the Sharepoint Connector to be used to access all the available Sharepoint…
11 votesHi KK, thanks for the suggestion. As we’ve recently released Nintex Xtensions, why not build a Connector using the Nintex Xtensions Framework?
This makes the action much more reusable and easier to configure. Or is your request to do with something else?
Thanks!
- Don't see your idea?