DatriseAI-first ETL

Public API Tableau

AI-first ETL from Public API into Tableau. Governed entities, incremental sync, typed landing tables.

How Datrise loads Public API into Tableau

Datrise syncs Public API's records, events, and configuration objects into Tableau as warehouse tables or a refreshed .hyper extract. Flexible or custom fields land in flattened columns for Tableau fields, and timestamps such as created, updated, and status changes are typed as date/datetime fields.

Sync is incremental: Datrise uses incremental refresh of the tables behind a live connection or extract, so re-runs update only what changed. Date-partitioned facts to keep extract refresh quick. Tableau .hyper extracts snapshot data, so Datrise keeps the source tables incremental and lets you choose live vs extract.

Ideal for visual analytics and dashboards in Tableau.

Endpoints

Public API: SaaS or API data source for analytics and warehouse sync.

Tableau: Salesforce analytics platform for interactive dashboards and visual exploration.

How Public API entities map to Tableau

Public API entityTableau objectNotes
recordspublic_api_recordsid PK · custom fields → flattened columns for Tableau fields
eventspublic_api_eventsdate/datetime fields events
configuration objectspublic_api_configuration_objectsid PK · linked to public_api_records

FAQ

How does Datrise handle Public API's custom fields in Tableau?

Flexible values are stored as flattened columns for Tableau fields, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Tableau types.

How does the Public API to Tableau sync stay up to date?

It runs incrementally — Datrise uses incremental refresh of the tables behind a live connection or extract.

Related pipelines

Early access

Connect Public API to Tableau the easy way

Skip brittle scripts and manual exports. Join the waitlist to get a guided setup, AI-assisted mapping, and reliable incremental sync for this integration.