Secoda to ThoughtSpot Integration

How Datrise loads Secoda into ThoughtSpot

Datrise syncs Secoda's tables, columns, dictionaries, lineage edges, owners, and documentation entries 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

Secoda: Data catalog, lineage, and documentation.

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

How Secoda entities map to ThoughtSpot

Secoda entity	ThoughtSpot object	Notes
tables	`secoda_tables`	id PK · custom fields → flattened columns for searchable fields
columns	`secoda_columns`	id PK · linked to secoda_tables
dictionaries	`secoda_dictionaries`	id PK · linked to secoda_tables
lineage edges	`secoda_lineage_edges`	id PK · linked to secoda_tables

FAQ

How does Datrise handle Secoda'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 Secoda to ThoughtSpot sync stay up to date?

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

Related pipelines

Early access

Connect Secoda 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.