Authentication mapping at import

Authentication visibility within our platform is typically limited to the workspace level. In most cases, users must map authentications when importing workflows and projects across workspaces.

The table below summarizes authentication selection via UI and API:

Selection of Authentications​

Copy

During an import, users will be presented with a list of authentications for the required service, categorized as follows:

• Related Authentications: These are authentications that were either last used or created in the same workspace for this particular import.

• Other Authentications: This category includes a list of authentications matching the required service, although there is no certainty that they match the required scope. It is the user's responsibility to verify that the authentication scope is appropriate.

Creating New Authentications:​

Copy

Users have the option to create a new authentication with the pre-selected required scope if necessary.

This can only be done through the UI.

Custom Service Authentication:​

Copy

If the imported project or workflow relies on an authentication based on a Custom Service, users will be prompted to:

1. Choose or create the required Custom Service

2. Create an appropriate authentication based on the selected or created Custom Service

Can I perform the project import via the API?​

Copy

Yes. However, the initial project creation or import must be done through the UI to resolve authentication mappings.

Subsequent API imports will rely on the authentication choice established through the UI journey.

How does the API handle authentication choices?​

Copy

The API will resolve the authentication to the most recently used authentication for the specific import.

We recommend importing the project via the UI once to ensure that the correct authentication is memorized for future API imports.

What happens during the first import into a workspace?​

Copy

The first import can only be done through the UI. During the first import into a workspace, users are prompted to choose or create an equivalent authentication associated with that import in the workspace.

What if a project and its workflows have been imported before in the same workspace?​

Copy

For subsequent imports in the same workspace, the recently used authentication will be highlighted as "last used" and preselected. When using the API, the recently used authentication will be used by default.

How are authentications categorized in the UI when selecting one for an import?​

Copy

Authentications are categorized into two groups:

• Related Authentications: These are authentications last used or created in the same workspace for the specific import.

• Other Authentications: This category includes a list of authentications matching the required service, but without certainty that they match the required scope. Users should verify the authentication scope.

Can I create a new authentication during the import process?​

Copy

Yes, users have the option to create a new authentication with the pre-selected required scope if needed. This can be done only through the UI.

What happens if the project/workflow uses an authentication based on a Custom Service?​

Copy

If the project/workflow relies on a Custom Service, users will be asked to choose or create the required Custom Service first. Afterward, they can create an appropriate authentication based on the chosen/created Custom Service. This can be done only through the UI.

Important Changes to Import Authentication Mapping

Copy

Before:

• Previously, users were restricted to choosing authentications created specifically for the import they were performing. In cases of the first import, users were compelled to create a new authentication for the import. Additionally, the UI would suggest the oldest authentication created for the specific import.

• When importing projects via the API, the authentication choice defaulted to the oldest authentication created for that specific import in the workspace. Even if newer authentications were created during the UI import process and associated with the import, the API would still adhere to the oldest authentication created during the initial project import.

After:

• Users can now select any existing authentication in the UI that matches the service.

• In the UI, authentication selection will default to the last used authentication for this import in this workspace. If not present, it will default to the most recently created authentication for that import.

• When using the API, authentication will resolve to the most recently used authentication for this specific import.