My Hours connector

Set up the My Hours connector in Kaivo: authentication, configuration, the 5 BigQuery tables it syncs, and answers to common questions.

Written By Lauri Raivio

Last updated 16 days ago

Kaivo is a fully managed data platform that syncs your My Hours data into a Google BigQuery warehouse and keeps it up to date automatically. There is no pipeline to build and no infrastructure to run, so you can spend your time analysing your project management data instead of moving it.

What is the My Hours connector

Sync your My Hours time tracking data into BigQuery with Kaivo to analyse hours, billable time, and project profitability.

Category	Project Management
Authentication	Username and password
Setup	Self-service

Getting started with the My Hours connector

Sign up for Kaivo and create a workspace.
Connect your My Hours account.
Choose which tables to sync.
Wait for the initial sync to finish.
Query your data in BigQuery or your favourite AI or BI tool.

Authenticating My Hours

Connect with your My Hours login. You provide:

Field	Description
Password	The password for your My Hours account.

Configuring the My Hours connector

When you set up the connector, you provide:

Field	Description
Email	Your My Hours account email address.
Start Date	Any data before this date will not be fetched.

Tables and columns synced from My Hours

Kaivo syncs 5 tables from My Hours into a dedicated dataset in your BigQuery warehouse. Click any table to see its columns and types.

clients (9 columns)

Column	Type	Description
`_kaivo_id`	`STRING`	Primary key that uniquely identifies the row. Auto-generated by Kaivo.
`id`	`FLOAT64`
`custom_id`	`STRING`
`contact_name`	`STRING`
`contact_email`	`STRING`
`name`	`STRING`
`archived`	`BOOL`
`date_archived`	`STRING`
`_kaivo_extracted_at`	`TIMESTAMP`	Timestamp that shows when the row was extracted. Auto-generated by Kaivo.

projects (27 columns)

Column	Type	Description
`_kaivo_id`	`STRING`	Primary key that uniquely identifies the row. Auto-generated by Kaivo.
`id`	`FLOAT64`
`name`	`STRING`
`archived`	`BOOL`
`date_archived`	`STRING`
`date_created`	`STRING`
`client_name`	`STRING`
`client_id`	`INT64`
`custom_id`	`STRING`
`budget_alert_percent`	`FLOAT64`
`budget_type`	`FLOAT64`
`labor_cost`	`FLOAT64`
`total_time_logged`	`FLOAT64`
`budget_value`	`FLOAT64`
`total_amount`	`FLOAT64`
`total_expense`	`FLOAT64`
`total_cost`	`FLOAT64`
`billable_time_logged`	`FLOAT64`
`total_billable_amount`	`FLOAT64`
`billable`	`BOOL`
`round_type`	`FLOAT64`
`round_interval`	`FLOAT64`
`budget_spent_percentage`	`FLOAT64`
`budget_target`	`FLOAT64`
`budget_period_type`	`FLOAT64`
`budget_spent`	`FLOAT64`
`_kaivo_extracted_at`	`TIMESTAMP`	Timestamp that shows when the row was extracted. Auto-generated by Kaivo.

tags (7 columns)

Column	Type	Description
`_kaivo_id`	`STRING`	Primary key that uniquely identifies the row. Auto-generated by Kaivo.
`id`	`FLOAT64`
`name`	`STRING`
`hex_color`	`STRING`
`archived`	`BOOL`
`date_archived`	`STRING`
`_kaivo_extracted_at`	`TIMESTAMP`	Timestamp that shows when the row was extracted. Auto-generated by Kaivo.

time_logs (52 columns)

Column	Type	Description
`_kaivo_id`	`STRING`	Primary key that uniquely identifies the row. Auto-generated by Kaivo.
`log_id`	`FLOAT64`
`user_id`	`FLOAT64`
`date`	`STRING`
`user_name`	`STRING`
`client_id`	`FLOAT64`
`client_name`	`STRING`
`project_id`	`FLOAT64`
`project_name`	`STRING`
`project_invoice_method`	`FLOAT64`
`task_id`	`FLOAT64`
`task_name`	`STRING`
`tags`	`STRING`
`rate`	`FLOAT64`
`billable`	`BOOL`
`in_locked_period`	`BOOL`
`billable_amount`	`FLOAT64`
`amount`	`FLOAT64`
`labor_cost`	`FLOAT64`
`labor_rate`	`FLOAT64`
`labor_duration`	`FLOAT64`
`log_duration`	`FLOAT64`
`expense`	`FLOAT64`
`cost`	`FLOAT64`
`note`	`STRING`
`status`	`FLOAT64`
`invoice_id`	`FLOAT64`
`invoiced`	`BOOL`
`billable_hours`	`FLOAT64`
`labor_hours`	`FLOAT64`
`custom_field1`	`FLOAT64`
`custom_field2`	`FLOAT64`
`custom_field3`	`FLOAT64`
`month_of_year`	`STRING`
`week_no`	`FLOAT64`
`week_of_year`	`STRING`
`roundtype`	`FLOAT64`
`balance`	`FLOAT64`
`billable_expense`	`FLOAT64`
`billable_hours_log_billable`	`FLOAT64`
`client_custom_id`	`STRING`
`end_time`	`STRING`
`invoiced_amount`	`FLOAT64`
`log_duration_billable`	`FLOAT64`
`start_time`	`TIMESTAMP`
`start_end_time`	`STRING`
`teams_names`	`STRING`
`task_list_name`	`STRING`
`task_due_date`	`STRING`
`task_start_date`	`STRING`
`uninvoiced_amount`	`FLOAT64`
`_kaivo_extracted_at`	`TIMESTAMP`	Timestamp that shows when the row was extracted. Auto-generated by Kaivo.

Subtable: time_logs__times

Column	Type	Description
`_kaivo_parent_id`	`STRING`	Foreign key referencing _kaivo_id in the parent table. Auto-generated by Kaivo.
`_kaivo_id`	`STRING`	Primary key that uniquely identifies the row. Auto-generated by Kaivo.
`id`	`FLOAT64`
`duration`	`FLOAT64`
`start_time`	`STRING`
`end_time`	`STRING`
`running`	`BOOL`
`deleted`	`BOOL`
`_kaivo_extracted_at`	`TIMESTAMP`	Timestamp that shows when the row was extracted. Auto-generated by Kaivo.

Subtable: time_logs__attachments

Column	Type	Description
`_kaivo_parent_id`	`STRING`	Foreign key referencing _kaivo_id in the parent table. Auto-generated by Kaivo.
`_kaivo_id`	`STRING`	Primary key that uniquely identifies the row. Auto-generated by Kaivo.
`value`	`JSON`
`_kaivo_extracted_at`	`TIMESTAMP`	Timestamp that shows when the row was extracted. Auto-generated by Kaivo.

Subtable: time_logs__teams

Column	Type	Description
`_kaivo_parent_id`	`STRING`	Foreign key referencing _kaivo_id in the parent table. Auto-generated by Kaivo.
`_kaivo_id`	`STRING`	Primary key that uniquely identifies the row. Auto-generated by Kaivo.
`value`	`STRING`
`_kaivo_extracted_at`	`TIMESTAMP`	Timestamp that shows when the row was extracted. Auto-generated by Kaivo.

Subtable: time_logs__tags_data

Column	Type	Description
`_kaivo_parent_id`	`STRING`	Foreign key referencing _kaivo_id in the parent table. Auto-generated by Kaivo.
`_kaivo_id`	`STRING`	Primary key that uniquely identifies the row. Auto-generated by Kaivo.
`value`	`JSON`
`_kaivo_extracted_at`	`TIMESTAMP`	Timestamp that shows when the row was extracted. Auto-generated by Kaivo.

users (15 columns)

Column	Type	Description
`_kaivo_id`	`STRING`	Primary key that uniquely identifies the row. Auto-generated by Kaivo.
`id`	`FLOAT64`
`name`	`STRING`
`archived`	`BOOL`
`date_archived`	`STRING`
`active`	`BOOL`
`account_owner`	`BOOL`
`email`	`STRING`
`rate`	`FLOAT64`
`billable_rate`	`FLOAT64`
`admin`	`BOOL`
`is_project_manager`	`BOOL`
`role_type`	`INT64`
`custom_id`	`STRING`
`_kaivo_extracted_at`	`TIMESTAMP`	Timestamp that shows when the row was extracted. Auto-generated by Kaivo.

How the My Hours sync works

After the first load, Kaivo keeps your BigQuery warehouse up to date for you. Where My Hours supports it, each sync pulls only new and changed records so it stays fast; otherwise it refreshes the whole table. Every record keeps its original ID, so you won't get duplicate rows.

Frequently asked questions

How long does the initial sync take for My Hours?

It depends on how much history is in your My Hours account. Most initial syncs finish within minutes, while large accounts can take a few hours. After that, syncs only fetch new and changed records, so they're much faster.

Can I sync only some tables or columns?

Yes. You pick which tables to sync when you set up the connection and can change the selection later. Tables you don't select are never copied to your warehouse.

What happens when My Hours's schema changes?

New fields are never added automatically. You choose which fields to sync, so data you haven't selected (sensitive personal data, for example) never lands in your warehouse. When a new field appears, it becomes available for you to add. What happens to removed or renamed fields depends on a table's sync mode: full-refresh tables always match what's currently in My Hours, so dropped fields disappear, while incremental tables keep their existing columns and history, so an old field stays and newly added fields fill in over time.

Your data lives in your own Kaivo-managed BigQuery warehouse, so the most direct option is to delete or anonymise specific records right in BigQuery. If you delete data in My Hours instead, full-refresh tables drop it on the next sync, while incremental tables keep it, so you would remove the row in BigQuery or ask us to run a full refresh. To remove everything, delete the My Hours connector in Kaivo and all of its synced data is deleted with it.

Common use cases for My Hours data

Billable hours

Use time_logs to track billable versus non-billable hours by project and client.

Project profitability

Join time_logs with projects and clients to compare logged time against budgets.

Team utilisation

Group hours by user to see how time is spent across the team.

Tag breakdown

Use tags to understand where effort goes within each project.

Use My Hours data in your AI and BI tools

Once My Hours data lands in your Kaivo-managed BigQuery warehouse, you can explore it with AI tools or any BI tool that connects to BigQuery. Here's how the most common destinations work with My Hours data.

Claude

Use Kaivo's MCP server to give Claude secure, workspace-scoped access to your data. Setup guide →

Power BI

Microsoft's BI tool with a native BigQuery connector. Supports direct query and scheduled refresh. Setup guide →

Data Studio

Free Google BI tool with native BigQuery support. One-click connection to your Kaivo warehouse; great for SMB teams on Google Workspace. Setup guide →

Tableau

The premium analytics standard, with native BigQuery integration. Setup guide →

Google Sheets

Use Connected Sheets to query BigQuery directly from a spreadsheet, with no SQL. Setup guide →

Excel

Connect via Power Query's BigQuery connector. Setup guide →

Metabase

Open-source BI tool with strong BigQuery support. Setup guide →

See our pricing page for My Hours connector pricing and plan details.

ClickUp: Sync ClickUp to BigQuery.
GitHub: Sync GitHub to BigQuery.
GitLab: Sync GitLab to BigQuery.
Harvest: Sync Harvest to BigQuery.
Jira: Sync Jira to BigQuery.
Kellokortti: Sync Kellokortti to BigQuery.

Was this helpful?

Still need help? Share an idea