Skip to main content

Assets and Connections

This page is the authoritative reference for sources and destinations (assets) in ETL integrations. Assets are connections you create in Matia; integrations use them as endpoints for data movement.

Source and Destination

  • Source: The system from which Matia extracts data — e.g. a database (Postgres, MySQL), a SaaS app (Salesforce, HubSpot), a file store (SFTP, S3) or an event manager (Kafka). You connect a source as an asset (authenticate, configure, name, optional tags and owners). The same asset can be used in multiple ETL integrations.
  • Destination: The system into which Matia loads data — typically a data warehouse (Snowflake, BigQuery, Databricks) or a database. Like sources, destinations are assets you connect once and reuse.

In the integrations table and on the integration details page, the source and destination are shown by type (icon) and name (the user-defined name you gave the asset, not the system name).

Connecting a New Asset

When you Add Integration or Add Asset (in Catalog), you can connect a new source or destination. The flow includes:

  1. Authenticate — sign in or provide credentials.
  2. Configure — connector-specific options (e.g. database, schema, region).
  3. Name (and optional description), tags, owners.
  4. Test connection — verify connectivity.
  5. Connect (or Save as draft).

After connecting, the asset appears in the catalog and can be selected as source or destination when creating an integration.

Selecting an Existing Asset

When creating an integration, you can select an existing source or destination already connected in your environment. Re-authentication is not required; select the asset and proceed to the Configure step.

Asset Names

The source name and destination name shown in the UI are the user-friendly names you set when connecting the asset (e.g. "Prod Snowflake", "Salesforce CRM"). They are not the system or connector type name. Use clear names so teams can identify assets in the integrations table and in lineage.

For adding and managing assets in the catalog, see Add an asset. For catalog concepts, see Catalog overview and Asset types.