Documentation Index
Fetch the complete documentation index at: https://docs.trydatawise.com/llms.txt
Use this file to discover all available pages before exploring further.
Connect Datawise to dbt Cloud to enable transformation-layer lineage and map dbt model dependencies onto your warehouse schema.
Prerequisites
- A dbt Cloud account with at least one project and job configured.
- A dbt Cloud service token with
read access. Generate one under Account Settings > Service Tokens in dbt Cloud.
- Your dbt Cloud Account ID and Project ID. Find these in the dbt Cloud URL:
https://cloud.getdbt.com/#/accounts/{ACCOUNT_ID}/projects/{PROJECT_ID}/.
Connection Setup
Go to Connectors, click Add Connector, and select dbt Cloud.
Required Fields
| Field | Description |
|---|
| Account ID | Your dbt Cloud account ID. Found in the URL when logged into dbt Cloud. |
| Project ID | The dbt Cloud project ID to connect. |
| Job ID | The dbt Cloud job ID Datawise uses to pull run artifacts. |
| API Token | A dbt Cloud service token with read access. |
| Access URL | Your dbt Cloud access URL. Default: https://cloud.getdbt.com. |
| Data Platform | The underlying data platform. Select Snowflake, BigQuery, or Postgres. Must match your connected warehouse connector. |
| Name | A display name for this connector in Datawise. |
Optional Fields
| Field | Description |
|---|
| Run ID | A specific dbt Cloud run ID to ingest from. Leave blank to use the latest successful run. |
| Data Platform Instance | If you have multiple warehouse instances, specify which one this dbt project targets. |
| Node Name Pattern | Filter which dbt nodes Datawise ingests. Uses glob syntax. |
Settings
| Setting | Default | Description |
|---|
| Include Column Lineage | On | Map column-level dependencies. Required for column lineage in the Lineage view. |
| Skip Sources in Lineage | Off | Exclude dbt source nodes from the lineage graph. |
| Use Incremental Lineage | Off | Only process lineage for nodes that changed since the last run. |
| Prefer SQL Parser for Lineage | Off | Use SQL parsing instead of dbt manifest metadata. Useful when manifest lineage is incomplete. |
| Enable Stateful Ingestion | Off | Process only new or changed nodes on subsequent runs. |
Schedule
| Field | Description |
|---|
| Run on a schedule | Recommended. Datawise needs fresh run artifacts to reflect the latest dbt model state. |
| Schedule | Cron-style schedule. Default: every day at 00:00. |
| Timezone | The timezone used to evaluate the schedule. |
How It Works
Datawise pulls from the dbt Cloud API using the Job ID you provide. It fetches the manifest and run artifacts from the latest successful run, then builds a model dependency graph. This graph maps onto your warehouse lineage so when Schema Radar detects a schema change, Datawise resolves which dbt models depend on the changed table.
Testing the Connection
If the test fails, check:
- That the service token has read access at the account level, not scoped only to a specific project.
- That the Job ID belongs to the specified Project ID.
- That the Access URL is correct for your account type.
After Connecting
Once connected:
- dbt models appear in Data Assets alongside your warehouse tables.
- The Lineage view shows model-to-table and model-to-model dependencies.
- Schema Guardian PR analysis references dbt model impact when a breaking change is detected.
