DatriseAI-first ETL

Holded to ThoughtSpot Integration

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

How Datrise loads Holded into ThoughtSpot

Datrise syncs Holded's contacts, leads, invoices, estimates, products, and projects 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

Holded: Spanish business suite joining CRM, invoicing, and accounting.

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

How Holded entities map to ThoughtSpot

Holded entityThoughtSpot objectNotes
contactsholded_contactsid PK · custom fields → flattened columns for searchable fields
leadsholded_leadsid PK · linked to holded_contacts
invoicesholded_invoicesid PK · linked to holded_contacts
estimatesholded_estimatesid PK · linked to holded_contacts

FAQ

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

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

Related pipelines

Early access

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