Connect your data

Bind a report to your live sources.

A Rahoto report is a runtime, not a file. Instead of pasting numbers in, you connect a source once and bind tables, charts, and values to it — so the report reads from your data and refreshes instead of going stale.

What you can connect

Rahoto ships 45 production connectors across six families. Each one is a real, tested integration — not a placeholder.

Databases

Operational and analytical databases, including change-data-capture sources.

PostgreSQL
MySQL
Airtable
Notion
HubSpot
MongoDB
SQL Server
Oracle Database
SAP HANA
PostgreSQL CDC
MySQL CDC
MongoDB CDC

Data warehouses

Query and refresh from the warehouse your team already governs.

Google BigQuery
Snowflake
Amazon Redshift

Files and storage

Upload structured files or read them from cloud object storage.

CSV File
JSON File
Excel File
Parquet File
Cloud Storage (S3)

Spreadsheets

Use governed sheets and workbooks as recurring report sources.

Google Sheets
Microsoft Excel

SaaS applications

Pull business objects from implemented application connectors.

Salesforce
Stripe
Shopify
Jira
Zendesk
QuickBooks

APIs and services

Read from HTTP services, accept pushed rows, and connect supported service APIs.

Push API
REST API
Google Analytics 4
Facebook/Meta Ads
Google Ads
LinkedIn Ads
Slack
Segment
Mixpanel
Intercom
Klaviyo
Twilio
Mailchimp
Asana

Streams

Subscribe to event streams and supported change feeds.

WebSocket Stream
Kafka Stream
Kafka CDC

Coming soon

Redis, DynamoDB, Databricks, GraphQL, and Microsoft Dynamics 365 are listed in the app but not yet available — they appear as clearly marked coming soon placeholders and cannot be used to create a data source. We will announce each one here when it ships.

Hand off work from analytics and BI tools

Keep analysis in the tool your team already uses. Each Rahoto integration states which report-ready outcomes work now, which need setup, and which the provider API cannot support.

These are handoff integrations, not replacements for the source tool. Rahoto evaluates them against three outcomes:

Editable data for Rahoto tables, charts, calculations, and variants.
A permissioned run reference that preserves the source link and run lineage.
A stored document kept in Rahoto-controlled artifact storage as a reference.

Mode

Connect and test your Mode workspace, choose a report, and run it from Rahoto. You can save the result rows as a governed Rahoto dataset for editable tables and charts, or import the completed run's PDF into Rahoto-controlled artifact storage. Rahoto preserves the source report and run lineage. This connection does not create a live Mode visual because Mode does not expose a supported snapshot-link API for it.

Hex

Connect and test Hex, choose a published project, run it, and save its validated, permissioned run reference in Rahoto with project and run lineage. Reports can use that governed reference without copying credentials or short-lived access links into the document. Hex's Project Runs API does not expose arbitrary result tables or native image and document exports through this connection, so Rahoto does not present those outcomes as available.

Funnel

Keep Funnel responsible for collecting and scheduling the export. Rahoto guides you to a supported destination (Push API, Amazon S3, BigQuery, Snowflake, Redshift, or Google Sheets) and you connect that destination to Rahoto as a data source. Funnel moves structured data; it is not presented as a visual or finished-report import.

Power BI, Tableau, and Looker

Connect Power BI with a Microsoft Entra service principal, Tableau with a personal access token, or Looker with API client credentials. Power BI can import a report as a stored PDF reference. Tableau can import editable view data or a stored view PDF. Looker can import a Look as governed editable data or render a dashboard into a stored PDF reference. Rahoto keeps provider credentials out of report content and stores imported documents in Rahoto-controlled artifact storage.

Sigma and ThoughtSpot

Connect Sigma with OAuth API client credentials to choose a workbook and import its completed PDF export into Rahoto-controlled storage. Connect ThoughtSpot with a scoped REST API access token to import an Answer as governed editable data or a Liveboard as a stored PDF reference. Rahoto preserves the selected source and run lineage; Sigma workbook-element data is not presented as editable until its element-level discovery flow is available.

Supermetrics

Keep Supermetrics responsible for collecting marketing data and running its scheduled transfer. Rahoto guides you to connect the same Amazon S3, BigQuery, Snowflake, Redshift, or Google Sheets destination with separate read-only credentials. Rahoto refreshes after the Supermetrics transfer window, while Supermetrics remains responsible for source authentication, field selection, and transfer timing.

Need another tool or handoff?

Tell us the tool and the reporting outcome you need — for example, editable results, a permissioned visual or run reference, or a stored document. We will recommend an existing safe route when one fits. If it does not, the request helps us prioritise a native integration; it does not imply a delivery date.

Datasets and live bindings

When you connect a source, Rahoto discovers its schema and creates a dataset— the reusable handle you bind report elements to. From there:

Add a data source and enter its credentials.
Let Rahoto discover the available tables and fields.
Bind a table, chart, or saved value to a field — or to an expression or aggregate over several fields.

Once an element is bound, its numbers come from the dataset every time the report runs. SeeDesign reports for how binding works inside the editor, andPublish & schedule for how a run turns into a delivered document.

Keep reports fresh

Datasets can refresh on a schedule, so a bound report reflects current data without a manual re-export. You set the cadence that fits the source — and the same schedule can feed a report that publishes and delivers itself. Scheduling and delivery live inPublish & schedule.

When your source changes shape

Source schemas move — a column gets renamed, a field is dropped, a type changes. Rahoto watches for this. When a dataset's schema drifts from what your report expects, it raises aschema-drift notice rather than silently breaking a binding.

To repair it, the mapping wizard walks you through re-binding affected placeholders to the new fields in three steps — pick the source, map each field, then review and save. Nothing publishes on a broken binding until you have confirmed the mapping.

Upload a file directly

No live connection required. You can upload a CSV orExcel (XLSX) file, as well as JSON and Parquet, and bind to it exactly like any other dataset. It is the quickest way to build your first report or work from a one-off extract.

Working with very large tables

Rahoto is built to design against real, enterprise-scale data — but a report is a designed document, not an unbounded data grid. A couple of limits apply so the editor stays responsive, and both are shown clearly in-app rather than failing silently:

A table renders up to 50,000 rows in the editor; past that you will see a "showing the first 50,000 of N" banner.
Single-shot full-content export is capped at 10,000 rows; larger tables export through the page-split path instead.

For very large tables, the reliable approach is to narrow at the source — filter, aggregate, or select only the columns you need with a SQL WHERE clause or a dataflow step before it reaches the report. A focused dataset is faster to design against and produces a cleaner document.