DatriseAI-first ETL

My Hours to ThoughtSpot Integration

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

How Datrise loads My Hours into ThoughtSpot

Datrise syncs My Hours's time logs, projects, tasks, clients, team members, and billable rates 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

My Hours: Time tracking and billable hours for projects.

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

How My Hours entities map to ThoughtSpot

My Hours entityThoughtSpot objectNotes
time logsmy_hours_time_logsid PK · custom fields → flattened columns for searchable fields
projectsmy_hours_projectsid PK · linked to my_hours_time_logs
tasksmy_hours_tasksid PK · linked to my_hours_time_logs
clientsmy_hours_clientsid PK · linked to my_hours_time_logs

FAQ

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

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

Related pipelines

Early access

Connect My Hours 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.