Xtensions

It would be great if a Data Lookup using a Connection defined in an Xtension with parameters populated could be edited at the form stage when External Data is configured to use it. For example if a Data Lookup constructs a JSON request body contai...

Xtensions currently supports OpenAPI V2. I'm logging this item to see how interested people are in the support for OpenAPI V3.

Streamlines creation Workflows using other often used component workflows, without the need to scroll through a long list of workflows and one can properly define required and optional field for the component workflow when adding it as an Xtension...

Add support for the OneDrive document interaction graph API, specifically for excel documents as an option to add support for excel as a data source. currently the only options are to use a 3rd party service to convert to a json at cost or use goo...

OData support would significantly expand what Nintex Workflow can communicate with

Currently if a xtension responds with a code other than 2xx the call is considered to be a failure. However many APIs legitimately return a status-code other than 2xx. For example if you query a service and no results are found, many APIs return ...

Retrieve workflow NWC Forms variables and values via API (OData) from custom connector, returning the result as a single JSON object

When an Xtension is updated, the only way to refresh the actions within the workflows (as per the documentation) is to delete them, drag a new copy and reconfigure.We get that this is needed for not breaking existing workflows, but what is sorely ...

With a prop of MaxCount, e.g. 999

Add Content-Type Support for application/pdf and application/zip. This hinders us from fully integrating apis without custom code.