Skip to content
Book a demoStart free
Connectors

Breezy HR connector

Set up the Breezy HR connector in Kaivo: authentication, configuration, the 3 BigQuery tables it syncs, and answers to common questions.

Breezy HR connector pricing, tier and credits on kaivo.io

Kaivo is a fully managed data platform that syncs your Breezy HR 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 Breezy HR recruiting data into BigQuery with Kaivo to track funnel, candidate scoring, and sourcing across your open positions.

CategoryHR
AuthenticationAPI key
SetupSelf-service

Getting started with the Breezy HR connector

Section titled “Getting started with the Breezy HR connector”
  1. Sign up for Kaivo and create a workspace.
  2. Connect your Breezy HR 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 Breezy HR API key. Generate one in your Breezy HR account under Settings → API Keys.

|

When you set up the connector, you provide:

Field Description
Company ID
Your Breezy HR company ID. Found in the URL when logged in, e.g. app.breezy.hr/[company_id]/dashboard.

|

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

candidates (33 columns)
Column Type Description
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
_id STRING
assigned_to___id STRING
assigned_to__email_address STRING
assigned_to__hex_color STRING
assigned_to__initial STRING
assigned_to__name STRING
assigned_to__username STRING
bias_status STRING
creation_date STRING
email_address STRING
headline STRING
initial STRING
meta_id STRING
name STRING
origin STRING
overall_score__average_score FLOAT64
overall_score__score FLOAT64
overall_score__scored_count FLOAT64
phone_number STRING
pos_id STRING
position_id STRING
profile_photo_url STRING
resume___id STRING
resume__error BOOL
resume__file_name STRING
resume__url STRING
source__type STRING
source__id STRING
source__name STRING
stage STRING
updated_date STRING
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.
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: candidates__overall_score__neutral

Section titled “Subtable: candidates__overall_score__neutral”
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.
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: candidates__overall_score__very_good

Section titled “Subtable: candidates__overall_score__very_good”
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: candidates__overall_score__very_poor

Section titled “Subtable: candidates__overall_score__very_poor”
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.
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.
pipelines (4 columns)
Column Type Description
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
_id STRING
name STRING
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.
positions (13 columns)
Column Type Description
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
type STRING
country_id STRING
country_name STRING
creation_date STRING
department STRING
name STRING
org_type STRING
pipeline_id STRING
position_id STRING
state STRING
updated_date STRING
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.
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.
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.

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

Section titled “How long does the initial sync take for Breezy HR?”

It depends on how much history is in your Breezy HR 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 Breezy HR’s schema changes?

Section titled “What happens when Breezy HR’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 Breezy HR, 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 Breezy HR 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 Breezy HR connector in Kaivo and all of its synced data is deleted with it.

Track candidates through pipelines and positions to see conversion at each stage.

Use the candidates overall_score to compare how candidates rate across roles.

Use the candidates origin to see which channels bring the strongest applicants.

Group candidates by assigned_to to balance workload across the team.

Use Breezy HR data in your AI and BI tools

Section titled “Use Breezy HR data in your AI and BI tools”

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