Skip to content
Book a demoStart free
Connectors

Employment Hero connector

Set up the Employment Hero connector in Kaivo: authentication, configuration, the 10 BigQuery tables it syncs, and answers to common questions.

Employment Hero connector pricing, tier and credits on kaivo.io

Kaivo is a fully managed data platform that syncs your Employment Hero 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.

Sync your Employment Hero HR data into BigQuery with Kaivo to report on headcount, leave, and pay without exporting spreadsheets.

CategoryHR
AuthenticationAPI key
SetupSelf-service

Getting started with the Employment Hero connector

Section titled “Getting started with the Employment Hero connector”
  1. Sign up for Kaivo and create a workspace.
  2. Connect your Employment Hero account.
  3. Choose which tables to sync.
  4. Wait for the initial sync to finish.
  5. Query your data in BigQuery or your favourite AI or BI tool.

Authenticate with your API Key.

Field Description
API Key
Your Employment Hero OAuth 2.0 access token, sent as a Bearer token. Create an app in the Employment Hero Developer Portal (top-right profile menu → Developer Portal) for a Client ID and Secret, then complete the OAuth flow to obtain an access token.

|

When you set up the connector, you provide:

Field Description
Organization ID
List of organization IDs to sync data for. Leave empty to sync all organizations.

| | Employees ID |

List of employee IDs to sync data for. Leave empty to sync all employees.

|

Tables and columns synced from Employment Hero

Section titled “Tables and columns synced from Employment Hero”

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

certifications (5 columns)
Column Type Description
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
type STRING
id STRING
name STRING
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.
custom_fields (9 columns)
Column Type Description
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
type STRING
description STRING
hint STRING
id STRING
in_onboarding BOOL
name STRING
required BOOL
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.

Subtable: custom_fields__custom_field_permissions

Section titled “Subtable: custom_fields__custom_field_permissions”
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 STRING
permission STRING
role STRING
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.
employee_certifications (7 columns)
Column Type Description
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
type STRING
certification_id STRING
id STRING
name STRING
status STRING
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.
employee_custom_fields (6 columns)
Column Type Description
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
type STRING
description STRING
id STRING
name STRING
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.
employees (30 columns)
Column Type Description
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
account_email STRING
address STRING
avatar_url STRING
code STRING
company_email STRING
company_landline STRING
company_mobile STRING
country STRING
date_of_birth STRING
employing_entity STRING
first_name STRING
gender STRING
home_phone STRING
id STRING
job_title STRING
known_as STRING
last_name STRING
location STRING
marital_status STRING
middle_name STRING
nationality STRING
personal_email STRING
personal_mobile_number STRING
primary_manager__id STRING
primary_manager__name STRING
role STRING
start_date STRING
title STRING
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.

Subtable: employees__secondary_cost_centres

Section titled “Subtable: employees__secondary_cost_centres”
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.
leave_requests (11 columns)
Column Type Description
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
comment STRING
employee_id STRING
end_date STRING
id STRING
leave_balance_amount FLOAT64
leave_category_name STRING
start_date STRING
status STRING
total_hours FLOAT64
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.
organisations (7 columns)
Column Type Description
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
country STRING
id STRING
logo_url STRING
name STRING
phone STRING
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.
pay_details (4 columns)
Column Type Description
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
effective_from STRING
id STRING
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.
policies (6 columns)
Column Type Description
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
created_at STRING
id STRING
induction BOOL
name STRING
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.
teams (5 columns)
Column Type Description
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
id STRING
name STRING
status STRING
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.

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

How long does the initial sync take for Employment Hero?

Section titled “How long does the initial sync take for Employment Hero?”

It depends on how much history is in your Employment Hero 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.

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 Employment Hero’s schema changes?

Section titled “What happens when Employment Hero’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 Employment Hero, 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.

How do I handle GDPR or data deletion requests?

Section titled “How do I handle GDPR or data deletion requests?”

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 Employment Hero 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 Employment Hero connector in Kaivo and all of its synced data is deleted with it.

Use employees and organisations to track headcount and changes over time.

Join leave_requests with teams to see leave trends and coverage.

Use pay_details and employee_certifications to report on pay and compliance.

Use Employment Hero data in your AI and BI tools

Section titled “Use Employment Hero data in your AI and BI tools”

Once Employment Hero 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 Employment Hero data.

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

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

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

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

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

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

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

See our pricing page for Employment Hero connector pricing and plan details.