Custom BI Integrations (Public Preview)
This feature requires an Enterprise or higher plan to use.
This feature is in Public Preview. See here for more information on what this means.
AI-first by design
Custom BI connectors ship with Claude skills that handle the implementation work: scaffolding, code generation, testing, and deployment. The skills scaffold, implement, and deploy a connector through guided conversation.
Monte Carlo natively supports several BI tools (Looker, Tableau, Power BI, and more). Custom BI integrations let you bring BI tools that Monte Carlo doesn't natively support, so your dashboards, reports, and datasets show up in the catalog and in lineage alongside the rest of your data assets.
Custom BI integrations give you two building blocks. You can use either one depending on your needs.
Feature Support
| Push Ingest API | Custom BI Connector | |
|---|---|---|
| Asset metadata (dashboards, reports, datasets, owners, URLs) | ✅ | ✅ |
| Table → BI lineage (which tables an asset reads) | ✅ | ✅ |
| BI → BI lineage (dashboard derives from dataset, etc.) | ✅ | ✅ |
When to use each
Push Ingest API — You push BI asset metadata directly to Monte Carlo using the pycarlo SDK or HTTP. Use it when:
- You already have a process that can call an API on a schedule or on change
- You want full control over when and how data is sent
Custom BI Connector — You implement the integration framework that talks to your BI tool's API, and deploy it inside Monte Carlo's agent. The agent handles scheduling, pagination, and delivery. Use it when:
- You want Monte Carlo to automatically collect asset metadata on a schedule (hourly)
- You prefer a managed framework over writing your own push pipeline
Architecture
Both approaches deliver the same data to the same Monte Carlo backend and produce the same result — BI assets in your catalog, connected to the warehouse tables they read and to each other.
flowchart LR
subgraph push ["Push Ingest API"]
A["Your script, pycarlo SDK or HTTP"] --> B["Integration Gateway"]
end
subgraph connector ["Custom BI Connector"]
C["Vendor BI API"] --> D["Your Connector, fetch_metadata"]
D --> E["Agent Framework, scheduling + pagination"]
end
E --> F["Monte Carlo, BI catalog · lineage"]
B --> F
Data model
Both building blocks use the same data model:
- BiAsset — structural metadata about a BI asset: a stable source ID, name, asset type (e.g.
dashboard,report,dataset), plus optional ownership, timestamps, folder, certification status, and lineage.
The schema is defined by pycarlo dataclasses. See the Push Ingest API reference for the full field-by-field breakdown.
Lineage
Custom BI integrations support three lineage mechanisms — use any combination:
| Mechanism | What it produces | How |
|---|---|---|
| Table → BI asset | Edges from warehouse tables to the BI assets that read them | Populate inputs on each asset with the tables it reads |
| BI → BI asset | Edges between BI assets (a dashboard derives from a dataset, a page contains cards, …) — arbitrarily deep | Populate upstream_assets / downstream_assets on each asset |
| SQL query tagging | Table → BI asset edges derived from the queries the BI tool runs | Tag the BI tool's SQL with the asset's ID; Monte Carlo resolves it from warehouse query logs |
Query tagging is useful when the BI tool queries your warehouse directly and its API can't tell you which tables an asset reads. See Lineage via SQL query tagging.
Setting up a custom BI integration
Navigate to Settings → Integrations → Add → Business intelligence and select Custom BI integration.
The form asks for an Integration name and how Monte Carlo should get this integration's BI asset metadata:
- Collect — Monte Carlo collects assets on a schedule using a custom BI connector deployed on your agent. Select the deployment, the registered connector, and its credentials. See Custom BI Connectors.
- Push — You push asset metadata yourself via the Push Ingest API. After the integration is created, Monte Carlo shows you the resource ID, the ingest URL, and lets you generate the integration key used to authenticate pushes.
FAQs
Is this the same as the native BI integrations?
No. Monte Carlo's native BI integrations (Looker, Tableau, Power BI) are built in and require no custom code. Custom BI integrations are for tools Monte Carlo doesn't natively support.
What happens to my integration keys if I delete the integration?
Deleting an integration in Monte Carlo also deletes any integration keys (including Ingestion-scoped keys) associated with it. Any scripts or pipelines using those keys will start failing with 401 errors. Before deleting an integration, make sure no active push pipelines depend on its keys — or create new keys on a replacement integration first.
Updated about 1 hour ago
