DatriseAI-first ETL

New York Times ThoughtSpot

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

How Datrise loads New York Times into ThoughtSpot

Datrise syncs New York Times's records, events, and configuration objects 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

New York Times: SaaS or API data source for analytics and warehouse sync.

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

How New York Times entities map to ThoughtSpot

New York Times entityThoughtSpot objectNotes
recordsnew_york_times_recordsid PK · custom fields → flattened columns for searchable fields
eventsnew_york_times_eventsdate/time columns events
configuration objectsnew_york_times_configuration_objectsid PK · linked to new_york_times_records

FAQ

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

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

Related pipelines

Early access

Connect New York Times 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.