Recruitee connector

Set up the Recruitee connector in Kaivo: authentication, configuration, the 3 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 Recruitee 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 Recruitee connector

Sync your Recruitee recruiting data into BigQuery with Kaivo to track candidates and pipeline across your open roles.

Category	HR
Authentication	API key
Setup	Self-service

Getting started with the Recruitee connector

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

Authenticate with your API Key.

Field	Description
API Key	Recruitee API Key. See here.

Configuring the Recruitee connector

When you set up the connector, you provide:

Field	Description
Company ID	Recruitee Company ID. You can also find this ID on the Recruitee API tokens page.

Tables and columns synced from Recruitee

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

candidates (29 columns)

Column	Type	Description
`_kaivo_id`	`STRING`	Primary key that uniquely identifies the row. Auto-generated by Kaivo.
`admin_id`	`INT64`
`adminapp_url`	`STRING`
`created_at`	`STRING`
`example`	`BOOL`
`followed`	`BOOL`
`has_avatar`	`BOOL`
`id`	`INT64`
`initials`	`STRING`
`last_message_at`	`STRING`
`my_last_rating`	`STRING`
`my_pending_result_request`	`BOOL`
`my_upcoming_event`	`BOOL`
`name`	`STRING`
`notes_count`	`INT64`
`pending_result_request`	`BOOL`
`photo_thumb_url`	`STRING`
`positive_ratings`	`INT64`
`rating`	`INT64`
`ratings__yes`	`INT64`
`ratings_count`	`INT64`
`referrer`	`STRING`
`source`	`STRING`
`tasks_count`	`INT64`
`unread_notifications`	`BOOL`
`upcoming_event`	`BOOL`
`updated_at`	`STRING`
`viewed`	`BOOL`
`_kaivo_extracted_at`	`TIMESTAMP`	Timestamp that shows when the row was extracted. Auto-generated by Kaivo.

Subtable: candidates__emails

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__phones

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__placements

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.
`candidate_id`	`INT64`
`created_at`	`STRING`
`hired_at`	`STRING`
`id`	`INT64`
`job_starts_at`	`STRING`
`language`	`STRING`
`offer_id`	`INT64`
`overdue_at`	`STRING`
`overdue_diff`	`STRING`
`position`	`INT64`
`positive_ratings`	`INT64`
`stage_id`	`INT64`
`updated_at`	`STRING`
`_kaivo_extracted_at`	`TIMESTAMP`	Timestamp that shows when the row was extracted. Auto-generated by Kaivo.

departments (7 columns)

Column	Type	Description
`_kaivo_id`	`STRING`	Primary key that uniquely identifies the row. Auto-generated by Kaivo.
`grouped_translations__en__name`	`STRING`
`id`	`INT64`
`name`	`STRING`
`offers_count`	`INT64`
`status`	`STRING`
`_kaivo_extracted_at`	`TIMESTAMP`	Timestamp that shows when the row was extracted. Auto-generated by Kaivo.

offers (41 columns)

Column	Type	Description
`_kaivo_id`	`STRING`	Primary key that uniquely identifies the row. Auto-generated by Kaivo.
`adminapp_url`	`STRING`
`candidates_count`	`INT64`
`careers_url`	`STRING`
`city`	`STRING`
`closed_at`	`STRING`
`country_code`	`STRING`
`created_at`	`STRING`
`department`	`STRING`
`department_id`	`INT64`
`disqualified_candidates_count`	`INT64`
`eeo_settings`	`STRING`
`employment_type`	`STRING`
`enabled_for_referrals`	`BOOL`
`example`	`BOOL`
`followed`	`BOOL`
`guid`	`STRING`
`has_active_campaign`	`BOOL`
`hired_candidates_count`	`INT64`
`hiring_manager_id`	`INT64`
`id`	`INT64`
`job_scheduler`	`STRING`
`kind`	`STRING`
`location`	`STRING`
`mailbox_email`	`STRING`
`number_of_openings`	`INT64`
`pipeline`	`BOOL`
`position`	`INT64`
`postal_code`	`STRING`
`published_at`	`STRING`
`qualified_candidates_count`	`INT64`
`recruiter_id`	`INT64`
`slug`	`STRING`
`state_code`	`STRING`
`state_name`	`STRING`
`status`	`STRING`
`street`	`STRING`
`title`	`STRING`
`updated_at`	`STRING`
`url`	`STRING`
`_kaivo_extracted_at`	`TIMESTAMP`	Timestamp that shows when the row was extracted. Auto-generated by Kaivo.

Subtable: offers__enabled_languages

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

Subtable: offers__followers

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

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.

How the Recruitee sync works

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

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

Common use cases for Recruitee data

Funnel reporting

Use candidates and offers to track conversion through your hiring process.

Department view

Join offers with departments to compare hiring across teams.

Pipeline analysis

Use candidates to find roles with too few or too many applicants.

Use Recruitee data in your AI and BI tools

Once Recruitee 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 Recruitee 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 Recruitee 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