OURA n8n INTEGRATION: AUTOMATE OURA WITH N8N

The Get Sleep Periods action retrieves detailed summaries of your sleep sessions recorded by your Oura Ring. This is arguably the most valuable action for anyone serious about optimizing their rest and recovery, giving you programmatic access to the comprehensive sleep data that makes Oura famous.

Configuration parameters:

• Credential to connect with: A required dropdown where you select your authenticated Oura account. This establishes the secure connection to pull your personal sleep data.
• Resource: A required dropdown set to "Summary" for this action, indicating you're accessing aggregated sleep metrics rather than raw sensor data.
• Operation: A required dropdown where "Get Sleep Periods" is selected, specifying that you want to retrieve sleep session records.
• Return All: An optional toggle switch. When enabled, it fetches every available sleep record, ignoring any limit. Useful for historical analysis or data migration.
• Limit: An optional numeric field that caps the number of records returned. Set to "5" by default, ideal for fetching recent nights without overwhelming your workflow.
• Filters: An optional section where you can add criteria like date ranges to narrow down results. Click "Add Filter" to specify conditions such as retrieving only last week's sleep data.

Practical use cases:

• Automatically log each night's sleep score and duration to a Google Sheet for monthly trend analysis
• Trigger a Slack message to your team channel when you've had less than 6 hours of sleep (signaling you might be slower to respond)
• Feed sleep data into a custom dashboard that correlates rest quality with productivity metrics
• Create weekly sleep reports sent via email every Monday morning

This action is perfect when you want to build sleep-aware automations or maintain a detailed sleep journal without manual data entry.

The Get Readiness Summary action pulls your Oura readiness scores, which indicate how prepared your body is for physical and mental challenges based on factors like sleep quality, recovery, and activity balance. This data is gold for anyone optimizing their daily performance.

Configuration parameters:

• Credential to connect with: A required dropdown for selecting your Oura account credentials. The screenshot shows "Oura account" selected for authentication.
• Resource: A required dropdown set to "Summary" to access your aggregated readiness metrics.
• Operation: A required dropdown where "Get Readiness Summary" is selected, telling n8n to fetch readiness data specifically.
• Return All: An optional toggle that, when enabled, retrieves all readiness records regardless of the limit setting. Currently disabled in the default configuration.
• Limit: An optional number input (set to "5" by default) that restricts how many readiness records are returned—useful for checking recent trends without processing excessive data.
• Filters: An optional section for adding date ranges or other criteria to refine which readiness summaries are retrieved.

Practical use cases:

• Send yourself a morning notification with your readiness score to help plan your day's intensity
• Automatically block "deep work" time in your calendar when readiness is high, or schedule lighter tasks when it's low
• Feed readiness data into a fitness app or training log to adjust workout intensity
• Create alerts when readiness drops below a personal threshold for several consecutive days, prompting a recovery check

Use this action when you want your workflows to be body-aware—adapting schedules, notifications, and activities based on your actual physiological readiness.

The Get Activity Summary action retrieves your daily activity metrics from Oura, including steps, calories burned, and activity scores. This gives you programmatic access to understand your movement patterns and energy expenditure throughout the day.

Configuration parameters:

• Credential to connect with: A required dropdown for selecting your authenticated Oura account, shown as "Oura account" in the configuration.
• Resource: A required dropdown configured to "Summary" to access daily activity aggregates.
• Operation: A required dropdown set to "Get Activity Summary," specifying retrieval of activity-related data.
• Return All: An optional toggle switch to fetch all available activity records when enabled, bypassing any limit restrictions.
• Limit: An optional text field (default "5") specifying the maximum number of activity summaries to return—ideal for recent-day analysis.
• Filters: An optional section for adding filtering criteria. Click "Add Filter" to define conditions like specific date ranges for your activity data.

Practical use cases:

• Automatically log daily step counts and activity scores to a fitness tracking spreadsheet
• Trigger a mid-day reminder if you haven't hit a certain activity threshold by noon
• Sync activity data to a habit tracking app to maintain accountability on movement goals
• Create weekly activity reports comparing your metrics against personal targets

This action shines when building movement-aware automations—whether you're tracking fitness goals, monitoring sedentary patterns, or integrating activity data into broader health dashboards. For similar fitness integrations, check out our Strava n8n integration guide.

The Get Profile action retrieves your Oura user profile information, including basic account details. While simpler than the other actions, it's essential for personalizing workflows and verifying account connections.

Configuration parameters:

• Credential to connect with: A required dropdown to select your Oura account credentials for authentication. "Oura account" is shown selected.
• Resource: A required dropdown set to "Profile," indicating you're accessing user profile data rather than health metrics.
• Operation: A required dropdown with "Get" selected, specifying that the action will retrieve (not modify) profile information.

Practical use cases:

• Verify that your Oura connection is active at the start of a workflow before processing health data
• Pull profile information to personalize automated health reports or dashboards
• Use profile data in multi-user scenarios to route data correctly in team wellness applications
• Include user details in exported health summaries for identification purposes

This action is useful as a connection test, for personalization purposes, or when building applications that serve multiple Oura users and need to identify whose data is being processed.