Service / connector mapping at import

Custom service mapping

Copy

If your project makes use of a custom service then, on first import, you will be asked to map it to a service in the destination workspace.

Note that the new version (currently being rolled out) support this for both HTTP client / GraphQL client steps and for connectors created with the CDK / Connector builder while the legacy version only supports this for HTTP client / GraphQL client steps which make use of custom services:

Custom connector mapping (new)

Copy

If your project contains a connector that was built using the CDK or Connector Builder, you will need to make sure it has been shared with both the source and destination environment.

When importing you will be asked to map the custom connector if an exact match cannot be found:

If the connector is not found in the list then there may have been issues with the deployment and sharing process.

Make sure you have followed the guidance on deployment using the API or deployment using the CLI remembering that you need to make sure you have:

• Shared in the correct region

• Shared with the correct emails for users in the destination environment

• Checked that the deployment status is complete