DatriseAI-first ETL

Codat to ThoughtSpot Integration

AI-first ETL from Codat into ThoughtSpot. Governed entities, incremental sync, typed landing tables.

How Datrise loads Codat into ThoughtSpot

Datrise syncs Codat's companies, accounts, invoices, bills, journal entries, and payments into ThoughtSpot as warehouse tables ThoughtSpot indexes for search. Flexible or custom fields land in flattened columns for searchable fields, and timestamps such as created, updated, and status changes are typed as date/time columns.

Sync is incremental: Datrise uses incremental refresh of the indexed tables, so re-runs update only what changed. Date-partitioned facts for live-query performance. ThoughtSpot search relies on clear names and relationships, so Datrise lands well-named, joinable tables.

Ideal for natural-language search analytics over a warehouse.

Endpoints

Codat: Unified API for accounting and banking data.

ThoughtSpot: Search-driven analytics with AI-assisted insights on warehouse data.

How Codat entities map to ThoughtSpot

Codat entityThoughtSpot objectNotes
companiescodat_companiesid PK · custom fields → flattened columns for searchable fields
accountscodat_accountsid PK · linked to codat_companies
invoicescodat_invoicesid PK · linked to codat_companies
billscodat_billsid PK · linked to codat_companies

FAQ

How does Datrise handle Codat's custom fields in ThoughtSpot?

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

How does the Codat to ThoughtSpot sync stay up to date?

It runs incrementally — Datrise uses incremental refresh of the indexed tables.

Related pipelines

Early access

Connect Codat to ThoughtSpot 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.