Click the custom connector for which you want to add a version.
The displays the connection details page.
Click Versions.
The page displays all the versions of the connector.
Click Create. This displays the Create new version page with the new version
number. The steps to create a new version are similar to that of creating a new custom connector.
It means that you can create a version with direct or indirect connectivity.
Click more_vertActions to select one of the following options:
View Details: To view the custom connector version details.
Deprecate Version: To deprecate the version.
Delete: To delete the version.
Export: To downloads the connector version as a JSON specification file. For more information, see Export and import.
Export and import
You can share the connector between different Google Cloud projects by exporting and importing the connector specification. You can export any connection version and then import the specification to the same project or different Google Cloud projects. Exporting deprecated connector versions is not supported.
Required roles and permissions
To get the permissions that
you need to export and import a custom connector,
ask your administrator to grant you the
following IAM roles:
Security Admin (roles/iam.securityAdmin)
on the project in which the secret is present. Alternatively, you can also ask your administrator to grant you or the service account, the secretmanager.secrets.getIamPolicy and secretmanager.secrets.setIamPolicy permissions on the project in which the secret is present.
Browse and select the JSON specification file for the custom connector. If you are importing the connector to a different project, then the Service account field is not prefilled.
Based on whether the connector already exists or not, the following scenarios are possible:
Connector with the same name doesn't exist: The Create custom connector page appears. The connector version in the imported JSON is prefilled. This version can't be changed.
Connector with the same name exists but the same version doesn't exist: The Create version page for that connector appears. Connector properties like connector type, name, description are prefilled from the existing connector and are not overwritten from the imported JSON. However, the connector version details and name are read from the imported JSON. Only the version name can be edited.
Connector with the same name and version exists: A warning message appears stating that the version already exists and a new version will be used when you import the JSON specification. If you click Import, the Create version page for that connector appears. Connector properties like the connector type, name, description are prefilled from the existing connector and are not overwritten by the imported JSON. However, the version details are read from the imported JSON and can be edited. The latest available version number is used for the version name.
Fill the remaining details and click Create. The connector is created with the imported JSON specification.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-26 UTC."],[[["\u003cp\u003eThis document guides you through creating and managing custom connector versions within Application Integration, including how to create a new version with direct or indirect connectivity.\u003c/p\u003e\n"],["\u003cp\u003eYou can manage a custom connector version by viewing details, deprecating, deleting, or exporting it as a JSON specification file.\u003c/p\u003e\n"],["\u003cp\u003eConnectors can be shared between different Google Cloud projects by exporting the connector specification as a JSON file and then importing it into another project.\u003c/p\u003e\n"],["\u003cp\u003eImporting a connector specification allows you to create a new connector, or add a new version to an existing connector, depending on whether the connector name or version already exists.\u003c/p\u003e\n"],["\u003cp\u003eTo export or import custom connectors, ensure you have the required IAM roles, including \u003ccode\u003eStorage Object Admin\u003c/code\u003e and \u003ccode\u003eSecurity Admin\u003c/code\u003e, or the equivalent permissions.\u003c/p\u003e\n"]]],[],null,["# Manage custom connector version\n\nSee the [supported connectors](/integration-connectors/docs/connector-reference-overview) for Application Integration.\n\nManage custom connector version\n===============================\n\n|\n| **Preview**\n|\n|\n| This product or feature is subject to the \"Pre-GA Offerings Terms\" in the General Service Terms section\n| of the [Service Specific Terms](/terms/service-terms#1).\n|\n| Pre-GA products and features are available \"as is\" and might have limited support.\n|\n| For more information, see the\n| [launch stage descriptions](/products#product-launch-stages).\n\nCreate a custom connector version\n---------------------------------\n\nTo create a custom connector version, follow these steps:\n\n1. In the [Console](https://console.cloud.google.com/), go to the **Application Integration \\\u003e Custom connectors** page, and then select or create a Google Cloud project.\n\n\n [Go to the Custom connectors page](https://console.cloud.google.com/integrations/custom-connectors)\n\n This displays the list of custom connectors.\n2. Click the custom connector for which you want to add a version. The displays the connection details page.\n\n3. Click **Versions** .\n\n The page displays all the versions of the connector.\n4. Click **Create** . This displays the **Create new version** page with the new version number. The steps to create a new version are similar to that of creating a new custom connector. It means that you can create a version with direct or indirect connectivity.\n - For creating a version with direct connectivity, do steps (from step 3 onwards) as documented in [Create a custom connector with direct connectivity](/integration-connectors/docs/create-custom-connector#create-a-custom-connector-with-direct-connectivity).\n - For creating a version with indirect connectivity, do steps (from step 3 onwards) as documented in [Create a custom connector with indirect connectivity](/integration-connectors/docs/create-custom-connector#create-a-custom-connector-with-indirect-connectivity).\n\nManage a custom connector version\n---------------------------------\n\nTo edit a custom connector, do the following steps:\n\n1. In the [Console](https://console.cloud.google.com/), go to the **Application Integration \\\u003e Custom connectors** page, and then select or create a Google Cloud project.\n\n\n [Go to the Custom connectors page](https://console.cloud.google.com/integrations/custom-connectors)\n\n This displays the list of custom connectors.\n2. Click the custom connector that has versions. The displays the connection details page.\n\n3. Click **Versions** .\n\n The versions for the selected connector appears.\n4. Click more_vert **Actions** to select one of the following options:\n - **View Details**: To view the custom connector version details.\n - **Deprecate Version**: To deprecate the version.\n - **Delete**: To delete the version.\n - **Export** : To downloads the connector version as a JSON specification file. For more information, see [Export and import](#export-import).\n\nExport and import\n-----------------\n\nYou can share the connector between different Google Cloud projects by exporting and importing the connector specification. You can export any connection version and then import the specification to the same project or different Google Cloud projects. Exporting deprecated connector versions is not supported.\n\n### Required roles and permissions\n\n\nTo get the permissions that\nyou need to export and import a custom connector,\n\nask your administrator to grant you the\nfollowing IAM roles:\n\n- [Storage Object Admin](/iam/docs/roles-permissions/storage#storage.objectAdmin) (`roles/storage.objectAdmin`) on the Cloud Storage bucket\n- [Security Admin](/iam/docs/roles-permissions/iam#iam.securityAdmin) (`roles/iam.securityAdmin`) on the project in which the secret is present. Alternatively, you can also ask your administrator to grant you or the service account, the `secretmanager.secrets.getIamPolicy` and `secretmanager.secrets.setIamPolicy` permissions on the project in which the secret is present.\n\n\nFor more information about granting roles, see [Manage access to projects, folders, and organizations](/iam/docs/granting-changing-revoking-access).\n\n\nYou might also be able to get\nthe required permissions through [custom\nroles](/iam/docs/creating-custom-roles) or other [predefined\nroles](/iam/docs/roles-overview#predefined).\n\n### Export a custom connector\n\nTo export a connector version, follow these steps:\n\n1. In the [Console](https://console.cloud.google.com/), go to the **Application Integration \\\u003e Custom connectors** page, and then select or create a Google Cloud project.\n\n\n [Go to the Custom connectors page](https://console.cloud.google.com/integrations/custom-connectors)\n2. Click the custom connector that you want to export. The custom connector's overview page opens.\n3. Click **Versions**. A list of versions of the custom connector is displayed.\n4. Click more_vert **More Actions** and then click upload **Export**. A JSON specification file for the custom connector is downloaded.\n\n### Import a custom connector\n\nTo import a connector version, follow these steps:\n\n1. In the [Console](https://console.cloud.google.com/), go to the **Application Integration \\\u003e Custom connectors** page, and then select or create a Google Cloud project.\n\n\n [Go to the Custom connectors page](https://console.cloud.google.com/integrations/custom-connectors)\nThe **Custom connectors** page appears.\n2. Click download **Import**.\n3. Browse and select the JSON specification file for the custom connector. If you are importing the connector to a different project, then the **Service account** field is not prefilled.\n\n \u003cbr /\u003e\n\n | **Note:** Ensure that the connector that you want to import is not deprecated.\n\n Based on whether the connector already exists or not, the following scenarios are possible:\n - **Connector with the same name doesn't exist:** The **Create custom connector** page appears. The connector version in the imported JSON is prefilled. This version can't be changed.\n - **Connector with the same name exists but the same version doesn't exist:** The **Create version** page for that connector appears. Connector properties like connector type, name, description are prefilled from the existing connector and are not overwritten from the imported JSON. However, the connector version details and name are read from the imported JSON. Only the version name can be edited.\n - **Connector with the same name and version exists:** A warning message appears stating that the version already exists and a new version will be used when you import the JSON specification. If you click **Import** , the **Create version** page for that connector appears. Connector properties like the connector type, name, description are prefilled from the existing connector and are not overwritten by the imported JSON. However, the version details are read from the imported JSON and can be edited. The latest available version number is used for the version name.\n4. Fill the remaining details and click **Create**. The connector is created with the imported JSON specification.\n\nQuotas and limits\n-----------------\n\nFor information about quotas and limits, see [Quotas and limits](/application-integration/docs/quotas).\n\nWhat's next\n-----------\n\n- Learn about [all tasks and triggers](/application-integration/docs/all-triggers-tasks).\n- Learn how to [test and publish an integration](/application-integration/docs/test-publish-integrations).\n\n- Learn about [error handling](/application-integration/docs/error-handling-strategy).\n- Learn about [integration execution logs](/application-integration/docs/introduction-logs)."]]
