Linking Oura as a source

Let AI connect your sources for you

Skip the manual setup — run this in your project and the wizard auto-detects your databases and APIs and connects them to PostHog.

Learn more
PostHog Wizard hedgehog

The Oura connector syncs your Oura Ring health data into PostHog, so you can analyze your health and activity metrics alongside your product data.

Prerequisites

You need an Oura account with access to the data you want to sync. A PostHog project admin must connect the Oura account before other project members can select it.

Adding a data source

  1. In PostHog, go to the Sources tab of the data pipeline section.
  2. Click + New source and click Link next to this source.
  3. Enter your credentials (see Configuration below) and click Next.
  4. Select the tables you want to sync, choose a sync method and frequency, then click Import.

Once the syncs are complete, you can start querying this data in PostHog.

When you reach the credentials step, use the Oura account field:

  1. Click Choose Oura connection, then Connect to Oura. If your project already has an Oura connection, you can select it instead.
  2. Sign in to Oura and authorize PostHog to access your data.
  3. After you return to PostHog, confirm the Oura connection is selected, then click Next to choose your tables.

PostHog requests the email, personal, daily, heartrate, workout, tag, session, spo2, and heart_health scopes. The email and personal scopes identify your connected account. The remaining scopes provide access to your health and activity data. Grant access to the data types you want to sync.

PostHog refreshes expired access tokens automatically.

Reconnecting an existing source

Oura retired personal access tokens in December 2025. If you previously connected with a personal access token, reconnect using OAuth:

  1. In the Sources tab, open your existing Oura source and select Configuration.
  2. Under Oura account, use Choose Oura connection (or Change if a connection is already selected) to connect your Oura account. Sign in to Oura and authorize access.
  3. Return to your existing source's Configuration tab, select the authorized Oura connection under Oura account, and click Save.

Existing sources do not switch to OAuth automatically. If your source reports Reconnect your Oura account, follow these steps to update its connection.

Sync modes

Each table can be synced in one of several modes, depending on what the source supports:

  • Webhook (when available) – the source pushes changes to PostHog in real time. Fastest freshness, lowest ongoing cost, and the only mode that reliably captures updates and deletes.
  • Incremental – only new or updated rows are synced on each run, using a cursor field (such as an updated_at timestamp). Cheaper than a full refresh, but deletes aren't captured.
  • Append only – new rows are appended using a cursor field; existing rows are never updated. Ideal for immutable, append-only tables like event logs.
  • Full refresh – the whole table is reloaded on every sync. Use it when a table has no reliable cursor or when you need deletions reflected.

See sync methods for a full explanation of how each mode works and how to choose between them.

Configuration

OptionTypeRequired
Personal access tokenpasswordYes

Supported tables

The tables available from this source are discovered from your account when you connect it, so the exact list depends on your data. Once connected, you can pick which tables to sync from the sources tab.

Troubleshooting

  • Authentication error or missing connection: Reconnect your Oura account if access has been revoked or the connection was deleted.
  • Permission error: Reconnect your Oura account and grant access to the data type you want to sync. Also check that your Oura membership is active.
  • Oura app not configured: Contact PostHog support.

If your sync is failing or data looks wrong, see the Data warehouse troubleshooting guide. If that doesn't help, contact support – we're happy to help.

Still have questions?

Was this page useful?