dbt Integration
SignalPilot integrates with dbt to bring your transformation layer context into data investigations. Access model lineage, documentation, test results, and column-level metadata without leaving your notebook.What dbt Integration Provides
Supported dbt Versions
Setup: dbt Cloud
1
Get Your dbt Cloud API Token
- Log in to dbt Cloud
- Go to Account Settings → API Access
- Generate a new Service Token with these permissions:
Metadata API(required)Job triggers(optional, for freshness checks)
- Copy the token
2
Find Your Account and Project IDs
From your dbt Cloud URL:
https://cloud.getdbt.com/deploy/{account_id}/projects/{project_id}3
Configure SignalPilot
Add to your
signalpilot.config.json:4
Verify Connection
In a SignalPilot notebook, test with:
@dbt show modelsYou should see a list of your dbt models.Setup: dbt Core
For dbt Core, SignalPilot reads your manifest and catalog files directly.1
Generate Manifest and Catalog
Run dbt to generate the required artifacts:
2
Configure SignalPilot
Add to your
signalpilot.config.json:Using dbt Context
Model Lineage
Ask about dependencies to understand data flow:Test Results
Check data quality before investigating:Column Lineage
Trace where data comes from:dbt Commands
Best Practices
1
Document Your Models
Well-documented dbt models make SignalPilot investigations faster. Include column descriptions, especially for business logic.
2
Run Tests Before Investigating
Check
@dbt tests before deep investigations. Failing tests might explain data anomalies.3
Use Lineage for Root Cause
When data looks wrong, trace lineage upstream. The issue often originates in staging or source models.
Related Resources
Context Aggregation
How dbt fits into the MCP architecture
Slack Integration
Combine dbt context with Slack discussions