DatriseAI-first ETL

Clockify to Looker Integration

AI-first ETL from Clockify into Looker. Governed entities, incremental sync, typed landing tables.

How Datrise loads Clockify into Looker

Datrise syncs Clockify's time entries, projects, tasks, users, clients, and tags into Looker as governed warehouse tables with LookML-ready naming. Flexible or custom fields land in flattened columns (nested fields expanded for modeling), and timestamps such as created, updated, and status changes are typed as date/time dimension columns.

Sync is incremental: Datrise uses incremental refresh of the underlying warehouse tables Looker explores, so re-runs update only what changed. Date-partitioned fact tables for PDT performance. Looker models live in LookML on top of SQL, so Datrise lands clean, stable column names rather than churn that would break your views.

Ideal for governed, version-controlled BI on a warehouse.

Endpoints

Clockify: Time tracking across projects and teams.

Looker: Google Cloud BI with LookML semantic models and governed dashboards.

How Clockify entities map to Looker

Clockify entityLooker objectNotes
time entriesclockify_time_entriesid PK · custom fields → flattened columns (nested fields expanded for modeling)
projectsclockify_projectsid PK · linked to clockify_time_entries
tasksclockify_tasksid PK · linked to clockify_time_entries
usersclockify_usersid PK · linked to clockify_time_entries

FAQ

How does Datrise handle Clockify's custom fields in Looker?

Flexible values are stored as flattened columns (nested fields expanded for modeling), so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Looker types.

How does the Clockify to Looker sync stay up to date?

It runs incrementally — Datrise uses incremental refresh of the underlying warehouse tables Looker explores.

Related pipelines

Early access

Connect Clockify to Looker 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.