Coassemble connector
Set up the Coassemble connector in Kaivo: authentication, configuration, the 3 BigQuery tables it syncs, and answers to common questions.
Coassemble connector pricing, tier and credits on kaivo.ioKaivo is a fully managed data platform that syncs your Coassemble 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 Coassemble connector
Section titled “What is the Coassemble connector”Sync your Coassemble training data into BigQuery with Kaivo to track course engagement, learner progress, and completion rates.
| Category | HR |
|---|---|
| Authentication | API key |
| Setup | Self-service |
Getting started with the Coassemble connector
Section titled “Getting started with the Coassemble connector”- Sign up for Kaivo and create a workspace.
- Connect your Coassemble 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 Coassemble
Section titled “Authenticating Coassemble”Authenticate with your User Token.
| Field | Description |
|---|---|
| User Token | |
| Your Coassemble API key, found under Settings → Add-ons → API in your workspace. |
|
Configuring the Coassemble connector
Section titled “Configuring the Coassemble connector”When you set up the connector, you provide:
| Field | Description |
|---|---|
| User ID | |
| Your Coassemble User ID, shown alongside the API key under Settings → Add-ons → API. |
|
Tables and columns synced from Coassemble
Section titled “Tables and columns synced from Coassemble”Kaivo syncs 3 tables from Coassemble into a dedicated dataset in your BigQuery warehouse. Click any table to see its columns and types.
courses (32 columns)
| Column | Type | Description |
|---|---|---|
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
description |
STRING |
|
active |
BOOL |
|
finish |
JSON |
|
id |
FLOAT64 |
|
identified |
BOOL |
|
image |
STRING |
|
is_sharable |
BOOL |
|
key |
STRING |
|
paid |
BOOL |
|
private |
BOOL |
|
start__button_label |
STRING |
|
start__button_style |
STRING |
|
start__display_button |
BOOL |
|
start__display_description |
BOOL |
|
start__display_duration |
BOOL |
|
start__display_pattern |
BOOL |
|
start__drag_index |
FLOAT64 |
|
start__finish |
BOOL |
|
start__layout |
STRING |
|
start__legacy |
BOOL |
|
start__link_type |
STRING |
|
start__mode |
STRING |
|
start__overlay |
FLOAT64 |
|
start__start |
BOOL |
|
start__text_alignment |
STRING |
|
start__text_colour |
STRING |
|
start__title_size |
STRING |
|
theme |
JSON |
|
thumbnail |
STRING |
|
title |
STRING |
|
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
Subtable: courses__emails
Section titled “Subtable: courses__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 |
JSON |
|
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
Subtable: courses__screens
Section titled “Subtable: courses__screens”| 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__completable |
FLOAT64 |
|
type__icon |
STRING |
|
type__id |
FLOAT64 |
|
type__name |
STRING |
|
type__premium |
BOOL |
|
type__title |
STRING |
|
description |
STRING |
|
asset |
STRING |
|
id |
FLOAT64 |
|
object__display_button |
BOOL |
|
object__display_description |
BOOL |
|
object__display_duration |
BOOL |
|
object__display_title |
BOOL |
|
object__drag_index |
FLOAT64 |
|
object__layout |
STRING |
|
object__legacy |
BOOL |
|
object__mode |
STRING |
|
object__text_alignment |
STRING |
|
passing_grade |
FLOAT64 |
|
scored |
BOOL |
|
sequence |
FLOAT64 |
|
title |
STRING |
|
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
Subtable: courses__screens__questions
Section titled “Subtable: courses__screens__questions”| 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. |
screen_types (2 columns)
| Column | Type | Description |
|---|---|---|
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
trackings (2 columns)
| Column | Type | Description |
|---|---|---|
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
How the Coassemble sync works
Section titled “How the Coassemble sync works”After the first load, Kaivo keeps your BigQuery warehouse up to date for you. Where Coassemble 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
Section titled “Frequently asked questions”How long does the initial sync take for Coassemble?
Section titled “How long does the initial sync take for Coassemble?”It depends on how much history is in your Coassemble 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?
Section titled “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 Coassemble’s schema changes?
Section titled “What happens when Coassemble’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 Coassemble, 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 Coassemble 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 Coassemble connector in Kaivo and all of its synced data is deleted with it.
Common use cases for Coassemble data
Section titled “Common use cases for Coassemble data”Course engagement
Section titled “Course engagement”Use courses and trackings to see which courses learners complete.
Progress reporting
Section titled “Progress reporting”Bring trackings into BigQuery to report on completion across your team.
Content view
Section titled “Content view”Use screen_types to understand how your courses are built.
Use Coassemble data in your AI and BI tools
Section titled “Use Coassemble data in your AI and BI tools”Once Coassemble 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 Coassemble data.
Claude
Section titled “Claude”Use Kaivo’s MCP server to give Claude secure, workspace-scoped access to your data. Setup guide →
Power BI
Section titled “Power BI”Microsoft’s BI tool with a native BigQuery connector. Supports direct query and scheduled refresh. Setup guide →
Data Studio
Section titled “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
Section titled “Tableau”The premium analytics standard, with native BigQuery integration. Setup guide →
Google Sheets
Section titled “Google Sheets”Use Connected Sheets to query BigQuery directly from a spreadsheet, with no SQL. Setup guide →
Connect via Power Query’s BigQuery connector. Setup guide →
Metabase
Section titled “Metabase”Open-source BI tool with strong BigQuery support. Setup guide →
See our pricing page for Coassemble connector pricing and plan details.
Related connectors
Section titled “Related connectors”- 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.