Asset Types

This page is the authoritative reference for asset types in the Matia catalog. Each type is added via Catalog → Add Asset and then selecting the appropriate option (Add a source, destination, warehouse, BI integration, or dbt).

Data Warehouse

• What: A connection to a data warehouse (e.g. Snowflake, BigQuery, Databricks). Used as the destination for ETL integrations and as the source for reverse ETL (and for observability monitors).
• Add: Add Asset → Add a warehouse → select connector → authenticate, configure, name, test, connect.

Source (ETL)

• What: A system from which Matia extracts data in ETL integrations (e.g. Postgres, Salesforce, HubSpot). Represented as an asset so it can be reused across integrations.
• Add: Add Asset → Add a source → select connector → setup flow.

Destination (ETL or Reverse ETL)

• What: A system into which Matia loads data. For ETL this is usually a warehouse; for reverse ETL it is an operational tool (e.g. HubSpot, Salesforce). Each is an asset with a user-defined name.
• Add: Add Asset → Add a destination → select connector → setup flow.

BI Integration

• What: A connection to a BI or analytics tool (e.g. Tableau, Metabase, Omni). Used for lineage so you can see which warehouse or dbt assets feed which reports or dashboards.
• Add: Add Asset → Add a BI integration → select connector → setup flow.

dbt (Orchestration)

• What: A connection to a dbt instance (dbt Core or dbt Cloud). Matia parses dbt projects to build lineage between warehouse tables and dbt models. dbt jobs can be triggered as post-run actions for ETL integrations.
• Add: Add Asset → Add DBT → select connector → setup flow.

Summary

Type	Purpose in Matia
Warehouse	ETL destination; reverse ETL + monitor source; catalog hierarchy
Source	ETL source (extract)
Destination	ETL (warehouse) or reverse ETL (operational) load target
BI integration	Lineage to reports/dashboards
dbt	Lineage; post-run triggers for ETL

For adding assets, see Add an asset. For lineage, see Lineage.