Publish custom connector

After you have created, configured, and validated a connector, you can publish the connector for use.

Prerequisites

Ensure that you have created a custom connector. See Create custom connector.
Note: You will be unable to publish a connector that has errors. In such a scenario, fix the error and then publish the connector.

Procedure

  1. Log in to your Control Room.
  2. Navigate to Manage > Packages.
  3. On the Packages page, click the Connectors tab.
  4. From the Connectors tab, select the connector that you want to publish.
  5. Mouse over the three dots icon to expand and click Publish package.
    • The Status of the connector changes to Publishing in the Connectors tab and might take some time to publish. After the connector is published as a package, the package is moved to the Published tab.
      Note: The Published tab displays packages that are either pre-installed with the Control Room or custom-built using the Package SDK or Connector Builder (after publishing). For the Packages published by the Connector Builder, the Created from column shows Connector whereas the packages built using the Package SDK or that are pre-installed show as SDK
    • When you publish a package for the first time, the package is automatically assigned the default version 1.0.0. When you republish a package, you are prompted to choose an Update Type: Major, Minor, or Patch.
      • If you choose the Major update type, then the first digit in the version number is automatically incremented. For example, 2.0.0.
      • If you choose the Minor update type, then the second digit in the version number is automatically incremented. For example, 1.1.0.
      • If you choose the Patch update type, then the third digit in the version number is automatically incremented. For example, 1.0.1.
    • You will receive notifications depending on the type of events that you have enabled after publishing a connector. For more information, see Enable or disable event categories.

    When you publish the connector as a package, the package is marked and signed as headless where the back-end APIs provide access to features and services. After the package is published, the package is available in the Bot editor and API Task editor.

Next steps

Packages