Generate a custom connector with the AI Xtensions Generator

Note: This feature is in beta.

Generate a custom connector with AI to save time and effort when creating a custom connector.

Tell the generator the name of the service to use and the actions you want the connector to perform, and it generates a draft custom connector for you. You can customize and import the custom connector directly into your Nintex Workflow tenant.

Before you start 

Generating a custom connector saves you from typing the full OpenAPI Specification, but you'll still need to review the draft against the third-party service's API. Before you generate your custom connector:

  1. Make sure you're familiar with creating a custom connector using the OpenAPI Specification.
    You must review the OpenAPI Specification JSON before you publish your custom connector.
    See Build your first custom connector for a refresher on building custom connectors.
  2. Check the API documentation for the third-party service to ensure that it is compatible with Nintex Workflow.
    See Limitations and Known Issues.
  3. Consider the actions you want the custom connector to include and which operations you expect to use.
    Keep these notes and the API documentation handy. They'll help you review the generated custom connector.

To generate a custom connector:

  1. Open your Nintex Workflow tenancy.
  2. Click Xtensions in the left navigation.
  3. Click   in the Custom connector list.
  4. Click Start with AI.
  5. Type a description of the custom connector you want to generate, including the name of the service and the actions it should perform.
    For example: From xe.com, convert one currency into another.
  6. When the list of generated operations appears, clear the checkbox for any operations you don't want to include.
    You can customize or hide the action in the next step.
  7. Click Next.
  8. Review the generated OpenAPI Specification carefully against the API documentation:
    • Check that the host and basePath are correct.
    • Check that each path is defined with the correct HTTP method, parameters, and response.
    • Check that the data type is correct for each parameter and response payload, and that all mandatory parameters are defined as required.
      Some parameters or responses may need specification extensions such as x-ntx-dynamic-values and x-ntx-dynamic-schema to handle dynamic data. You may need to add supporting operations to retrieve data.
    • Check that the security definition is correct.
      If you're using OAuth authentication, make sure your scopes are complete, including the offline_access scope to request refresh tokens.
    • Check that any generated text in descriptions and summaries is correct.
    • Make sure you don't modify or remove the three specification extension fields at the bottom of the file:
      • x-ntx-contract-id
      • x-ntx-render-version
      • x-ntx-generated-by-ai
  9. Optionally, customize the actions:
  10. Click Next.
  11. Review and complete the security configuration for the custom connector.
  12. Click Next.
  13. Either select an icon or upload an image to use for the custom connector.
    The custom connector name and description are automatically populated from the generated JSON. You can edit these if you want to.
  14. Click Publish.