DatriseAI-first ETL

Recharge ThoughtSpot

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

How Datrise loads Recharge into ThoughtSpot

Datrise syncs Recharge's subscriptions, charges, customers, plans, and churn events 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

Recharge: Subscription commerce for Shopify and recurring billing.

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

How Recharge entities map to ThoughtSpot

Recharge entityThoughtSpot objectNotes
subscriptionsrecharge_subscriptionsid PK · custom fields → flattened columns for searchable fields
chargesrecharge_chargesid PK · linked to recharge_subscriptions
customersrecharge_customersid PK · linked to recharge_subscriptions
plansrecharge_plansid PK · linked to recharge_subscriptions

FAQ

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

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

Related pipelines

Early access

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