Skip to content
Book a demoStart free
Connectors

Captain Data connector

Set up the Captain Data connector in Kaivo: authentication, configuration, the 5 BigQuery tables it syncs, and answers to common questions.

Captain Data connector pricing, tier and credits on kaivo.io

Kaivo is a fully managed data platform that syncs your Captain Data 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 data from Captain Data instead of moving it.

Sync your Captain Data workflow runs into BigQuery with Kaivo to monitor your data automation jobs, catch failures, and track reliability.

CategoryTech
AuthenticationAPI key
SetupSelf-service

Getting started with the Captain Data connector

Section titled “Getting started with the Captain Data connector”
  1. Sign up for Kaivo and create a workspace.
  2. Connect your Captain Data 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 Captain Data project API key.

|

When you set up the connector, you provide:

Field Description
Project UID
Your Captain Data project UUID.

|

Tables and columns synced from Captain Data

Section titled “Tables and columns synced from Captain Data”

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

job_results (5 columns)
Column Type Description
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
extracted_at STRING
job_result_id STRING
job_uid STRING
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.
jobs (17 columns)
Column Type Description
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
error_message STRING
finish_time STRING
main_job_name STRING
main_job_uid STRING
name STRING
number_inputs INT64
row_count INT64
scheduled_time STRING
start_time STRING
status STRING
step_uid STRING
total_row_count INT64
uid STRING
workflow_name STRING
workflow_uid 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.
successful_jobs (17 columns)
Column Type Description
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
error_message STRING
finish_time STRING
main_job_name STRING
main_job_uid STRING
name STRING
number_inputs INT64
row_count INT64
scheduled_time STRING
start_time STRING
status STRING
step_uid STRING
total_row_count INT64
uid STRING
workflow_name STRING
workflow_uid 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.
workflows (7 columns)
Column Type Description
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
created_at STRING
name STRING
project_id INT64
template_uid STRING
uid 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.
name STRING
step_uid STRING
uid STRING
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.
workspace (11 columns)
Column Type Description
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
current_month_end STRING
current_month_start STRING
email STRING
name STRING
plan_name STRING
project_uid STRING
tasks_left INT64
tasks_max INT64
tasks_used INT64
_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 Captain Data 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 Captain Data?

Section titled “How long does the initial sync take for Captain Data?”

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

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

Use jobs and successful_jobs to track run volume and success rates over time.

Bring job_results into BigQuery to analyse the data your workflows collect.

Join workflows with jobs to find which automations fail most often.

Use Captain Data data in your AI and BI tools

Section titled “Use Captain Data data in your AI and BI tools”

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

  • Adform: Sync Adform to BigQuery.
  • Amplitude: Sync Amplitude to BigQuery.
  • Auth0: Sync Auth0 to BigQuery.
  • Convex: Sync Convex to BigQuery.
  • GitHub: Sync GitHub to BigQuery.
  • GitLab: Sync GitLab to BigQuery.