My Hours to Redash Integration
AI-first ETL from My Hours into Redash. Governed entities, incremental sync, typed landing tables.
How Datrise loads My Hours into Redash
Datrise syncs My Hours's time logs, projects, tasks, clients, team members, and billable rates into Redash as SQL tables Redash queries and visualizes. Flexible or custom fields land in flattened columns for query results, and timestamps such as created, updated, and status changes are typed as temporal columns.
Sync is incremental: Datrise uses incremental refresh of the connected tables, so re-runs update only what changed. Date-partitioned facts for scheduled queries. Redash caches query results on a schedule, so Datrise keeps tables incrementally fresh so cached dashboards reflect reality.
Ideal for lightweight, query-driven dashboards.
Endpoints
My Hours: Time tracking and billable hours for projects.
Redash: Open-source SQL client for queries, visualizations, and dashboards.
How My Hours entities map to Redash
| My Hours entity | Redash object | Notes |
|---|---|---|
| time logs | my_hours_time_logs | id PK · custom fields → flattened columns for query results |
| projects | my_hours_projects | id PK · linked to my_hours_time_logs |
| tasks | my_hours_tasks | id PK · linked to my_hours_time_logs |
| clients | my_hours_clients | id PK · linked to my_hours_time_logs |
FAQ
How does Datrise handle My Hours's custom fields in Redash?
Flexible values are stored as flattened columns for query results, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Redash types.
How does the My Hours to Redash sync stay up to date?
It runs incrementally — Datrise uses incremental refresh of the connected tables.
Related pipelines
More destinations for My Hours
Early access
Connect My Hours to Redash 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.