Connections
Set up and manage source connections in the Import Tool so you can import data from external systems.
A connection links the Import Tool to an external source system. You must create a connection before you can configure and run a stream. Within the Connections view, you add the connections, their credentials, configure source-specific catalog or location settings when available, and test that the source is reachable.

Create a connection
Enter connection details
Provide a Name for the connection, then choose the Source type. Supported source types include Celonis and HTTP / REST API.
Enter the credentials and other settings required for the selected source. The fields depend on the source type. The following sections explain the HTTP / REST API and Celonis settings.
After the connection is stored and tested, open Imports and create a stream that uses this connection as its source.
Use a clear connection name that identifies the source system and environment. You have to select this connection later when you create a stream.
HTTP / REST API
Use HTTP / REST API when the source exposes records over HTTP.

On New Connection, set:
Name – a label for the connection
Source type – HTTP / REST API
Base URL – the API root, for example
https://api.example.com/v1Test endpoint – optional path appended to the Base URL for Test connection. Pick an endpoint that needs the stored credential. Leave it empty to test the Base URL itself.
Authentication – the authentication method, for example Bearer token
When Authentication is Bearer token, enter the token in Bearer token. After you save, the field shows Saved — not shown. Leave it empty to keep the stored token, or enter a new value to replace it.
Choose Save before Test connection. You can test only after the connection is stored.
Field discovery
Field discovery tells the mapping editor how to find the fields of this API:
None — each stream samples its own endpoint – the connection is the API root. Each stream finds fields by sampling its own endpoint, or when you choose Refresh fields in field mapping.
To use an API specification, choose the matching format, for example OpenAPI / Swagger (JSON or YAML), WSDL, XSD, OData EDMX, or GraphQL. Then set Provide the spec by, for example URL, enter the spec location, and choose Discover fields.
Save the connection before you discover fields from a specification.
After you save the HTTP connection, configure the request on the stream HTTP endpoint tab. See HTTP endpoint. For a full walkthrough, see Importing Using HTTP.
Celonis
Use Celonis when the source is a Celonis Knowledge Model.

On New Connection, set:
Name – a label for the connection
Source type – Celonis
Celonis team URL – the team URL for your environment, for example
https://team.eu-1.celonis.cloudKey type – API token or OAuth2 (client credentials)
For API token, enter the token in API token.
For OAuth2 (client credentials), enter:
Client ID
Token URL
Scope
Client secret
The OAuth client must include the following scopes for catalog access:
Select Save after you provide the connection details. Otherwise, you cannot configure the catalog.

Catalog
After you save the connection and its credentials, the catalog fields become available. Select the catalog details from top to bottom because each selection makes the next field available. For example, select a Data pool before you can select a Data model.
Data pool
Data model
Studio space
Studio package
Knowledge model
When the catalog selection is complete, select Save.

For Celonis Studio and data-pool permissions, see Importing from Celonis.
Managing connections
From the Connections list you can:
Test connection – verify that the connection still works with the stored credentials.
Edit – update the name, credentials, or source-specific settings.
Delete – remove a connection that you no longer need.
Before you delete a connection, check that no streams still use it as their source. Update or remove those streams first.
Last updated
Was this helpful?

