Credentials store the login details IMSURGE needs to connect to external systems, such as API keys, usernames, and tokens. Once saved, you can use the same credential across multiple integrations and pipelines without re-entering it.

Credentials give IMSURGE access to external systems. They do not move, transform, or process data on their own.

How Credentials Fit into the Workflow

Credentials are the first step in enabling any data flow. Integrations rely on credentials to authenticate, and pipelines rely on integrations.

flowchart TD
    A[Step 1: Create Credentials] --> B[Step 2: Create Integration]
    B --> C[Step 3: Create Pipeline]

Managing Credentials

You can manage all of your stored authentication details from the Settings › Credentials tab in the IMSURGE UI.

  • Create Credentials: Navigate to Settings › Credentials › + Credentials, choose the vendor, and enter the required fields. Use a descriptive name, such as Aeroqual Production API.
  • Edit Credentials: If a token expires or a password changes, update the credential in one place. All integrations using it will automatically use the updated values on their next run.
  • Delete Credentials: Remove credentials that are no longer needed to keep your workspace organized.

Reference

The required fields depend on the system you are connecting to.

Start with that system’s guide in the Integration Library.

If that guide links to a page in Integration Library > Credentials, use it for the exact setup steps and required fields. Examples include Eagle.io Credentials and Specto DataLake Credentials.

Aspect Details
Encryption All secrets stored in Credentials are encrypted at rest and cannot be viewed in the UI after saving.
Permissions Assign only the minimum level of permissions required for the integration. Avoid using administrator-level keys unless necessary.