DatriseAI-first ETL

Everhour to Metabase Integration

AI-first ETL from Everhour into Metabase. Governed entities, incremental sync, typed landing tables.

How Datrise loads Everhour into Metabase

Datrise syncs Everhour's time entries, projects, tasks, users, clients, and budgets into Metabase as clean SQL tables Metabase auto-discovers. Flexible or custom fields land in flattened columns for the question builder, and timestamps such as created, updated, and status changes are typed as temporal columns for trends.

Sync is incremental: Datrise uses incremental refresh of the connected tables, so re-runs update only what changed. Date-partitioned facts for large questions. Metabase auto-scans schemas, so Datrise uses readable table and column names so the no-code UI stays self-explanatory.

Ideal for self-serve questions and dashboards for whole teams.

Endpoints

Everhour: Time tracking and budgets for project teams.

Metabase: Open-source analytics with questions, dashboards, and embedded insights.

How Everhour entities map to Metabase

Everhour entityMetabase objectNotes
time entrieseverhour_time_entriesid PK · custom fields → flattened columns for the question builder
projectseverhour_projectsid PK · linked to everhour_time_entries
taskseverhour_tasksid PK · linked to everhour_time_entries
userseverhour_usersid PK · linked to everhour_time_entries

FAQ

How does Datrise handle Everhour's custom fields in Metabase?

Flexible values are stored as flattened columns for the question builder, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Metabase types.

How does the Everhour to Metabase sync stay up to date?

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

Related pipelines

Early access

Connect Everhour to Metabase 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.