HoorayHR connector

Set up the HoorayHR connector in Kaivo: authentication, configuration, the 4 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 HoorayHR 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 HR data instead of moving it.

What is the HoorayHR connector

Sync your HoorayHR data into BigQuery with Kaivo to report on leave and people data without exporting spreadsheets.

Category	HR
Authentication	Username and password
Setup	Self-service

Getting started with the HoorayHR connector

Sign up for Kaivo and create a workspace.
Connect your HoorayHR 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 HoorayHR

Connect with your HoorayHR login. You provide:

Field	Description
HoorayHR Password	The password for your HoorayHR account at app.hoorayhr.io.

Configuring the HoorayHR connector

When you set up the connector, you provide:

Field	Description
HoorayHR Email	The email address you use to sign in to HoorayHR at app.hoorayhr.io.

Tables and columns synced from HoorayHR

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

leave-types (23 columns)

Column	Type	Description
`_kaivo_id`	`STRING`	Primary key that uniquely identifies the row. Auto-generated by Kaivo.
`id`	`FLOAT64`
`icon`	`STRING`
`name`	`STRING`
`color`	`STRING`
`budget`	`FLOAT64`
`default`	`FLOAT64`
`is_legacy`	`FLOAT64`
`created_at`	`STRING`
`updated_at`	`STRING`
`updated_by`	`FLOAT64`
`leave_in_days`	`FLOAT64`
`unpaid_leave`	`FLOAT64`
`period_offset`	`FLOAT64`
`auto_approve_limit`	`FLOAT64`
`subtract_holidays`	`FLOAT64`
`calculation_method`	`STRING`
`budget_release_timing`	`STRING`
`invisible_in_calendar`	`FLOAT64`
`budget_release_recurrence`	`STRING`
`leave_type_system_category`	`STRING`
`accumulate_budget_when_absent`	`FLOAT64`
`_kaivo_extracted_at`	`TIMESTAMP`	Timestamp that shows when the row was extracted. Auto-generated by Kaivo.

Subtable: leave-types__leave_type_rules

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`
`name`	`STRING`
`order`	`FLOAT64`
`budget`	`FLOAT64`
`created_at`	`STRING`
`updated_at`	`STRING`
`leave_type_id`	`FLOAT64`
`transfer_term`	`FLOAT64`
`transfer_period`	`STRING`
`expiration_moment`	`STRING`
`rule_system_category`	`STRING`
`_kaivo_extracted_at`	`TIMESTAMP`	Timestamp that shows when the row was extracted. Auto-generated by Kaivo.

sick-leaves (21 columns)

Column	Type	Description
`_kaivo_id`	`STRING`	Primary key that uniquely identifies the row. Auto-generated by Kaivo.
`id`	`FLOAT64`
`notes`	`STRING`
`status`	`FLOAT64`
`user_id`	`FLOAT64`
`timezone`	`STRING`
`created_at`	`STRING`
`updated_at`	`STRING`
`percentage`	`FLOAT64`
`actual_start`	`STRING`
`actual_total`	`FLOAT64`
`actual_return`	`STRING`
`expected_total`	`FLOAT64`
`reported_start`	`STRING`
`actual_start_end`	`STRING`
`expected_return`	`STRING`
`reported_return`	`STRING`
`user_id_reported`	`FLOAT64`
`actual_return_end`	`STRING`
`user_id_confirmed`	`FLOAT64`
`_kaivo_extracted_at`	`TIMESTAMP`	Timestamp that shows when the row was extracted. Auto-generated by Kaivo.

time-off (25 columns)

Column	Type	Description
`_kaivo_id`	`STRING`	Primary key that uniquely identifies the row. Auto-generated by Kaivo.
`id`	`FLOAT64`
`end`	`STRING`
`notes`	`STRING`
`pause`	`FLOAT64`
`reply`	`STRING`
`start`	`STRING`
`status`	`FLOAT64`
`user_id`	`FLOAT64`
`timezone`	`STRING`
`created_at`	`STRING`
`holiday_id`	`FLOAT64`
`is_private`	`FLOAT64`
`leave_unit`	`STRING`
`updated_at`	`STRING`
`budget_total`	`FLOAT64`
`leave_type_id`	`FLOAT64`
`time_off_type`	`STRING`
`user_id_approved`	`FLOAT64`
`base_time_off_type`	`STRING`
`is_not_calculated`	`FLOAT64`
`leave_type_rule_id`	`FLOAT64`
`budget_adjustment`	`FLOAT64`
`budget_calculated`	`FLOAT64`
`_kaivo_extracted_at`	`TIMESTAMP`	Timestamp that shows when the row was extracted. Auto-generated by Kaivo.

Subtable: time-off__labels

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.
`type`	`STRING`
`id`	`FLOAT64`
`name__de`	`STRING`
`name__en`	`STRING`
`name__nl`	`STRING`
`created_at`	`STRING`
`updated_at`	`STRING`
`archived_at`	`STRING`
`_kaivo_extracted_at`	`TIMESTAMP`	Timestamp that shows when the row was extracted. Auto-generated by Kaivo.

users (56 columns)

Column	Type	Description
`_kaivo_id`	`STRING`	Primary key that uniquely identifies the row. Auto-generated by Kaivo.
`id`	`FLOAT64`
`city`	`STRING`
`email`	`STRING`
`phone`	`STRING`
`teams`	`STRING`
`avatar`	`STRING`
`gender`	`STRING`
`locale`	`STRING`
`status`	`FLOAT64`
`country`	`STRING`
`is_admin`	`FLOAT64`
`zipcode`	`STRING`
`initials`	`STRING`
`job_title`	`STRING`
`last_name`	`STRING`
`nick_name`	`STRING`
`timezone`	`STRING`
`biography`	`STRING`
`birthdate`	`STRING`
`company_id`	`FLOAT64`
`created_at`	`STRING`
`first_name`	`STRING`
`insertion`	`STRING`
`invited_at`	`STRING`
`updated_at`	`STRING`
`birth_place`	`STRING`
`civil_status`	`STRING`
`nationality`	`STRING`
`on_boarded_at`	`STRING`
`birth_country`	`STRING`
`email_private`	`STRING`
`address_number`	`STRING`
`address_street`	`STRING`
`emergency_name`	`STRING`
`holiday_policy__id`	`FLOAT64`
`holiday_policy__name`	`STRING`
`last_name_usage`	`STRING`
`company_end_date`	`STRING`
`employee_number`	`STRING`
`address_addition`	`STRING`
`holiday_policy_id`	`FLOAT64`
`invited_by_user_id`	`FLOAT64`
`travel_allowance`	`FLOAT64`
`company_end_reason`	`STRING`
`company_start_date`	`STRING`
`invite_accepted_at`	`STRING`
`invite_reminded_at`	`STRING`
`bank_account_number`	`STRING`
`emergency_relation`	`STRING`
`emergency_work_phone`	`STRING`
`citizen_service_number`	`STRING`
`emergency_personal_phone`	`STRING`
`two_factor_authentication`	`FLOAT64`
`bank_account_number_on_behalf_of`	`STRING`
`_kaivo_extracted_at`	`TIMESTAMP`	Timestamp that shows when the row was extracted. Auto-generated by Kaivo.

Subtable: users__abilities

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: users__cost_centers

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: users__integrations

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.
`type`	`STRING`
`enabled`	`STRING`
`_kaivo_extracted_at`	`TIMESTAMP`	Timestamp that shows when the row was extracted. Auto-generated by Kaivo.

How the HoorayHR sync works

After the first load, Kaivo keeps your BigQuery warehouse up to date for you. Where HoorayHR 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 HoorayHR?

It depends on how much history is in your HoorayHR 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 HoorayHR'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 HoorayHR, 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 HoorayHR 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 HoorayHR connector in Kaivo and all of its synced data is deleted with it.

Common use cases for HoorayHR data

Leave analysis

Use time-off and leave-types to see leave trends and coverage.

Sick leave tracking

Use sick-leaves to monitor absence across the team.

People view

Join users with leave data to build people reports.

Use HoorayHR data in your AI and BI tools

Once HoorayHR 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 HoorayHR 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 HoorayHR connector pricing and plan details.

Greenhouse: Sync Greenhouse to BigQuery.
Kellokortti: Sync Kellokortti to BigQuery.
Nepton: Sync Nepton to BigQuery.
Teamtailor: Sync Teamtailor to BigQuery.
7shifts: Sync 7shifts to BigQuery.
Ashby: Sync Ashby to BigQuery.

Was this helpful?

Still need help? Share an idea