Skip to content
Book a demoStart free
Connectors

Oura connector

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

Oura connector pricing, tier and credits on kaivo.io

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

Sync your Oura activity, sleep, and readiness data into BigQuery with Kaivo to analyse health and wellbeing trends alongside the rest of your data.

CategoryOther
AuthenticationAPI key
SetupSelf-service
  1. Sign up for Kaivo and create a workspace.
  2. Connect your Oura 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 Oura personal access token.

|

When you set up the connector, you provide:

Field Description
Start Date
Any data before this date will not be fetched.

|

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

daily_activity (33 columns)
Column Type Description
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
class_5_min STRING
score FLOAT64
active_calories FLOAT64
average_met_minutes FLOAT64
contributors__meet_daily_targets FLOAT64
contributors__move_every_hour FLOAT64
contributors__recovery_time FLOAT64
contributors__stay_active FLOAT64
contributors__training_frequency FLOAT64
contributors__training_volume FLOAT64
equivalent_walking_distance FLOAT64
high_activity_met_minutes FLOAT64
high_activity_time FLOAT64
inactivity_alerts FLOAT64
low_activity_met_minutes FLOAT64
low_activity_time FLOAT64
medium_activity_met_minutes FLOAT64
medium_activity_time FLOAT64
met__interval FLOAT64
met__timestamp TIMESTAMP
meters_to_target FLOAT64
non_wear_time FLOAT64
resting_time FLOAT64
sedentary_met_minutes FLOAT64
sedentary_time FLOAT64
steps FLOAT64
target_calories FLOAT64
target_meters FLOAT64
total_calories FLOAT64
day DATE
timestamp TIMESTAMP
_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 FLOAT64
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.
daily_readiness (15 columns)
Column Type Description
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
contributors__activity_balance FLOAT64
contributors__body_temperature FLOAT64
contributors__hrv_balance FLOAT64
contributors__previous_day_activity JSON
contributors__previous_night FLOAT64
contributors__recovery_index FLOAT64
contributors__resting_heart_rate FLOAT64
contributors__sleep_balance FLOAT64
day DATE
score FLOAT64
temperature_deviation FLOAT64
temperature_trend_deviation FLOAT64
timestamp TIMESTAMP
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.
daily_sleep (12 columns)
Column Type Description
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
contributors__deep_sleep FLOAT64
contributors__efficiency FLOAT64
contributors__latency FLOAT64
contributors__rem_sleep FLOAT64
contributors__restfulness FLOAT64
contributors__timing FLOAT64
contributors__total_sleep FLOAT64
day DATE
score FLOAT64
timestamp TIMESTAMP
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.
heart_rate (5 columns)
Column Type Description
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
bpm FLOAT64
source STRING
timestamp TIMESTAMP
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.
sessions (11 columns)
Column Type Description
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
day DATE
start_datetime TIMESTAMP
end_datetime TIMESTAMP
type STRING
heart_rate JSON
heart_rate_variability JSON
mood JSON
motion_count__interval FLOAT64
motion_count__timestamp TIMESTAMP
_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 FLOAT64
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.
sleep_periods (29 columns)
Column Type Description
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
average_breath FLOAT64
average_heart_rate FLOAT64
average_hrv FLOAT64
awake_time FLOAT64
bedtime_end TIMESTAMP
bedtime_start TIMESTAMP
day DATE
deep_sleep_duration FLOAT64
efficiency FLOAT64
heart_rate__interval FLOAT64
heart_rate__timestamp TIMESTAMP
hrv__interval FLOAT64
hrv__timestamp TIMESTAMP
latency FLOAT64
light_sleep_duration FLOAT64
low_battery_alert BOOL
lowest_heart_rate FLOAT64
movement_30_sec STRING
period FLOAT64
readiness_score_delta FLOAT64
rem_sleep_duration FLOAT64
restless_periods FLOAT64
sleep_phase_5_min STRING
sleep_score_delta FLOAT64
time_in_bed FLOAT64
total_sleep_duration JSON
type STRING
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.

Subtable: sleep_periods__heart_rate__items

Section titled “Subtable: sleep_periods__heart_rate__items”
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 FLOAT64
_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 FLOAT64
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.
tags (5 columns)
Column Type Description
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
day DATE
text STRING
timestamp TIMESTAMP
_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.
workouts (11 columns)
Column Type Description
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
activity STRING
calories FLOAT64
day DATE
distance FLOAT64
end_datetime TIMESTAMP
intensity STRING
label JSON
source STRING
start_datetime TIMESTAMP
_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 Oura 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 Oura?

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

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

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

Use daily_sleep and sleep_periods to track sleep quality and duration over time.

Analyse daily_activity and daily_readiness to see how activity affects recovery.

Report on workouts and heart_rate to understand training load and intensity.

Keep a synced history to spot long-term trends across sleep, activity, and readiness.

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