Integrations · Data & BI
Your data stack, connected. Every driver, one governed model.
Data and BI integrations are governed connections between your data stack, warehouses, databases, and BI platforms, and your FP&A stack, so operational drivers flow into your model automatically instead of through exports. Cube connects to Snowflake, BigQuery, Redshift, Databricks, Tableau, and any SQL source.
…and more
Don’t see your system?
We build custom connections to nearly any system or flat file. Tell us what you run and we’ll scope the connector.
Featured integrations
The data platforms most Cube deployments connect first. Every card opens the full integration guide.
Snowflake
Usage, pipeline, and unit economics join your actuals, every sync.
BQGoogle BigQuery
Product and marketing drivers land mapped to your model.
RSAmazon Redshift
Operational tables synced on schedule, traceable to the row.
DBXDatabricks
Lakehouse metrics flow into plans and reports automatically.
TABTableau
The data sources your team curates, joined to the plan.
LKRLooker
Curated metrics flow into plans and reports, on schedule.
PBIPower BI
Datasets your team maintains, mapped into the model.
MDBMongoDB
Operational collections, normalized into finance-friendly rollups.
See it on your own tables.
Bring one schema or a read-only role. You’ll see your drivers mapped and reporting beside the GL in Cube.
How does a data & BI integration work in Cube?
Every warehouse, database, and BI platform reaches Cube through one of four paths. All four end the same way: mapped once to your model, synced on a schedule, traceable to the source row.
Other integration types
What changes when drivers leave the CSV behind?
The workflow, row by row. Both columns are honest.
| The workflow | Manual exports | Connected to Cube |
|---|---|---|
| Getting drivers | ✕Ask the data team for an export, wait, paste. | ✓Drivers sync on a schedule, mapped to your model. |
| Finance + ops | ✕Financial and operational data live in different tools. | ✓GL actuals and warehouse drivers share one governed model. |
| Metric definitions | ✕Every dashboard computes revenue its own way. | ✓One definition, governed in the layer, used everywhere. |
| Refresh cadence | ✕Monthly, or whenever someone reruns the query. | ✓As often as you schedule it, or on demand. |
| Audit | ✕Which query produced that number? | ✓Every figure traces to the source row. |
Every connection, governed.
Read the security overview →Where your drivers land
Governed drivers flow into the tools your team already lives in. Your workflows stay; everything underneath gets smarter.
Claude, ChatGPT, and Copilot work from governed finance data via Cube MCP.
What are data & BI integrations?
Data and BI integrations are governed connections between the systems that hold your operational data, cloud warehouses, databases, and business intelligence platforms such as Tableau, and the planning, reporting, and analysis tools a finance team uses. The integration syncs operational drivers and curated metrics on a schedule, maps tables and data sources to the accounts and dimensions finance plans by, and keeps every downstream number tied to its source row.
In Cube, those connections feed the Agentic Finance Layer, so the same governed drivers power every FP&A workflow: driver-based planning, forecasting, variance analysis, and reporting in your spreadsheets. Accounting, HRIS, and CRM sources join the same model; explore the full FP&A integrations library, the guide to accounting software integrations, or the security overview for the controls behind every connection.
See your data stack in the model.
A demo personalized to your stack: your warehouse, your BI stack, your reports.
No prep needed. Just bring the names of your source systems.
