Features Integrations AI & API Pricing Blog Docs
Overview WHOOP Oura Withings Apple Health Glucose Hevy Lab Tests Training Data Weekly Recap Connect any AI MCP Server Claude ChatGPT Codex Grok (xAI) Developer tools Other assistants Automations Prompt library AI access & privacy REST API

Health automations with VitalTrends

Use VitalTrends as the data layer for automated health workflows: a readiness brief every morning, a weekly training review, a weight trend nudge, or a digest for your coach.

This page covers the three ways to automate, setup notes for each platform, seven workflow recipes and downloadable templates.

Last checked: 21 November 2026. Third-party platforms change often. Where a section says "Not yet tested by VitalTrends", the steps come from that vendor's documentation, not from a run we completed.

Three ways to automate

ApproachGood forHow it reads VitalTrendsExamples
Scheduled AI assistantsA written brief or review with no setup beyond a promptHosted MCP server, https://mcp.vitaltrends.net/mcp, through the assistant's connectorGrok, ChatGPT, Claude
No-code platformsSending results to Telegram, Slack, email, Notion, a calendar or smart homeMCP client nodes (MCP server) or HTTP steps (REST API)n8n, Zapier, Make, Home Assistant
Plain REST callsExact numbers, no AI in the loop, full controlREST API, https://vitaltrends.net/api/v1, with Authorization: Bearer <API key>Apple Shortcuts, cron scripts, GitHub Actions

MCP tool names and REST endpoints map one to one. See the MCP tool reference and the REST API reference.

Before you start: safety

Not medical advice. These workflows summarize your own data. They do not diagnose or treat anything. Talk to a qualified professional about health decisions.

Scheduled AI assistants

Some AI assistants can run a saved prompt on a schedule. Once the VitalTrends connector is added, a scheduled prompt can read your data and send you the answer. Whether a scheduled run can use a custom connector, and on which plans, differs by app and changes often, so follow the client guide:

Any recipe prompt below works as a scheduled prompt. Start with the morning brief prompt and run it once by hand before you schedule it.

n8n

Not yet tested by VitalTrends Based on n8n's documentation and node source code (n8n 2.48), checked 21 November 2026.

Option A: import the REST template

Download n8n-morning-readiness-brief.json. It runs Schedule Trigger → HTTP Request (WHOOP daily) → HTTP Request (Oura readiness) → Code (green/yellow/red) → Telegram. It uses no AI and sends only the three-line message to Telegram.

1
Create the VitalTrends credential

In n8n, create a Header Auth credential named VitalTrends API key. Set Name to Authorization and Value to Bearer YOUR_VITALTRENDS_API_KEY.

2
Create the Telegram credential

Create a Telegram credential with your bot token from Telegram's BotFather.

3
Import the workflow

Open a new workflow and import the file (the workflow menu's Import from File option, or paste the JSON onto the canvas).

4
Select credentials

Select your Header Auth credential on both HTTP Request nodes. Select your Telegram credential on Send to Telegram and replace YOUR_TELEGRAM_CHAT_ID.

5
Set the timezone

In Workflow settings, set the timezone to your VitalTrends profile timezone so "today" matches your local day.

6
Test, then activate

Run the workflow once by hand and check the message. Then activate (publish) it. The label depends on your n8n version.

To send to Slack or email instead, replace the Telegram node with n8n's Slack or Send Email node and map {{ $json.message }} into the message text.

Option B: AI Agent with the MCP Client Tool

  1. Add an AI Agent node with a chat model, then attach an MCP Client Tool to it.
  2. Set Endpoint to https://mcp.vitaltrends.net/mcp and Server Transport to HTTP Streamable. If your n8n version only shows an SSE Endpoint field, use https://mcp.vitaltrends.net/sse.
  3. Set Authentication to Bearer Auth and create a Bearer credential with your VitalTrends API key. This is the simplest option.
  4. Set Tools to Include to Selected and pick only the read tools the workflow needs, for example get_whoop_daily and get_oura_daily_readiness.
  5. Put a recipe prompt in the agent's prompt and connect a Schedule Trigger before it and a Telegram, Slack or email node after it.

n8n also offers MCP OAuth2 authentication, with Use Dynamic Client Registration on by default. VitalTrends supports dynamic registration for public clients without a client secret. We have not tested whether n8n's registration matches that; if OAuth fails, use Bearer Auth.

Zapier

Not yet tested by VitalTrends Based on Zapier's help center, checked 21 November 2026.

MCP Client by Zapier (beta)

  1. On Zapier's Apps page, select + Add connection, search for MCP Client and select Add connection.
  2. Set Server URL to https://mcp.vitaltrends.net/mcp and Transport to Streamable HTTP.
  3. Choose one of:
    • OAuth: Yes. Select Yes, Continue to MCP Client, then paste your API key on the Connect VitalTrends page. The bearer token field is ignored. This gives a read-only token.
    • OAuth: No. Enter your VitalTrends API key as the Bearer Token.
  4. In a Zap, use the Run Read-Only Tool search with a tool such as get_whoop_daily, then pass a short summary to Slack, Gmail or another app.

A Zapier Community thread reports bearer-token-only connections failing at the "Yes, Continue" step for some servers. If that happens, try OAuth: Yes.

Webhooks by Zapier (REST)

Webhooks by Zapier is available on Zapier's Professional, Team and Enterprise plans.

  1. Trigger: Schedule by Zapier, every day at your chosen time.
  2. Action: Webhooks by Zapier → GET. URL https://vitaltrends.net/api/v1/whoop/daily, with per_page set to 5 in the parameter fields (Zapier recommends parameters there rather than in the URL). Add a header Authorization with the value Bearer YOUR_VITALTRENDS_API_KEY.
  3. Add a Code by Zapier step to pick the row whose cycle_start_date is today and build the message. The JavaScript in the n8n template's Code node is a good starting point.
  4. Send only the message to Slack, Gmail or SMS.

Make

Not yet tested by VitalTrends Based on Make's MCP Client app documentation, checked 21 November 2026.

  1. In a scenario, add MCP Client → Call a tool. Make's MCP Client app is in open beta.
  2. Create a connection: choose + New MCP Server, set URL to https://mcp.vitaltrends.net/mcp and paste your VitalTrends API key into API Key / Access token. Make's documentation does not say which header it sends the token in; VitalTrends expects Authorization: Bearer <key>.
  3. Set Tool Name to a read tool such as get_whoop_daily and Arguments such as {"per_page": 5}.
  4. Add a router or text step to build the message, then send it with Slack, Telegram, Gmail or another module.

Make also supports OAuth for MCP servers and lists https://www.make.com/oauth/cb/mcp as its redirect URI. VitalTrends registers public clients dynamically; we have not confirmed that Make uses dynamic registration. If the MCP Client connection fails, Make's HTTP app (Make a request) can call the REST API with an Authorization: Bearer YOUR_VITALTRENDS_API_KEY header.

Home Assistant

Not yet tested by VitalTrends Based on Home Assistant's documentation, checked 21 November 2026.

MCP client integration. Home Assistant's Model Context Protocol integration supports Streamable HTTP and SSE servers and exposes their tools to conversation agents. For servers that need sign-in, it asks for an OAuth client ID and client secret through Application Credentials. VitalTrends does not issue client secrets (it only supports dynamically registered public clients), and Home Assistant's documentation does not describe a bearer-header option, so we do not recommend this route for now.

Recommended: a RESTful sensor. Home Assistant can read the REST API directly. This example creates a recovery sensor and dims the lights to a warm tone on a red recovery morning.

secrets.yaml:

vitaltrends_api_authorization: "Bearer YOUR_VITALTRENDS_API_KEY"

configuration.yaml:

sensor:
  - platform: rest
    name: VitalTrends WHOOP recovery
    unique_id: vitaltrends_whoop_recovery
    resource: https://vitaltrends.net/api/v1/whoop/daily?per_page=5
    headers:
      Authorization: !secret vitaltrends_api_authorization
      Accept: application/json
    scan_interval: 1800
    value_template: >
      {% set today = now().strftime('%Y-%m-%d') %}
      {% set rows = value_json.data
         | selectattr('cycle_start_date', 'eq', today)
         | selectattr('recovery_score', 'ne', none)
         | list %}
      {{ rows[0].recovery_score if rows else 'unknown' }}

Automation:

automation:
  - alias: Warm, dim lights on a red recovery morning
    triggers:
      - trigger: time
        at: "07:30:00"
    conditions:
      - condition: numeric_state
        entity_id: sensor.vitaltrends_whoop_recovery
        below: 34
    actions:
      - action: light.turn_on
        target:
          entity_id: light.living_room
        data:
          color_temp_kelvin: 2700
          brightness_pct: 40

scan_interval: 1800 polls every 30 minutes. Home Assistant's default of 30 seconds is far more often than this data changes. Replace light.living_room with your own light.

Apple Shortcuts: "How recovered am I?"

Not yet tested by VitalTrends Based on Apple's Shortcuts User Guide, checked 21 November 2026.

Shortcuts has no MCP support, so it calls the REST API with Get Contents of URL. Name the shortcut "How recovered am I" and you can run it by asking Siri, or add it to your Home Screen as a widget.

1
Create the shortcut

Open Shortcuts, tap + and name the shortcut How recovered am I.

2
Get today's date

Add Format Date. Set the date to Current Date, the format to Custom and the custom format to yyyy-MM-dd.

3
Add the URL

Add URL with https://vitaltrends.net/api/v1/whoop/daily?per_page=5.

4
Call the API

Add Get Contents of URL. Tap Show More, keep the method as GET, and under Headers add a header with key Authorization and value Bearer YOUR_VITALTRENDS_API_KEY.

5
Read the rows

Add Get Dictionary Value to get the value for data in Contents of URL.

6
Find today's row

Add Repeat with Each item in that Dictionary Value. Inside the repeat, add Get Dictionary Value for cycle_start_date in Repeat Item. Then add If that value is the Formatted Date from step 2, and inside the If, add Set Variable named Today to Repeat Item.

7
Say the answer

After the repeat, add If Today has any value. Inside it, add Get Dictionary Value for recovery_score in Today, then Speak Text (or Show Result): "Your WHOOP recovery today is [Dictionary Value] percent." In Otherwise, add Speak Text: "No recovery for today has synced yet."

8
Test it

Run it once from the editor. Shortcuts may ask permission to connect to vitaltrends.net. Allow it.

For Oura, use https://vitaltrends.net/api/v1/oura/daily-readiness?start=[Formatted Date]&end=[Formatted Date] instead, then read score from the first item in data.

The shortcut contains your API key. Don't share it or upload it to the Shortcuts Gallery. If you think the key leaked, regenerate it in Settings → Developer and update every automation that uses it.

Scripts, cron and GitHub Actions

The Python templates below need Python 3.9 or newer and requests (pip install requests). They read the key from the VITALTRENDS_API_KEY environment variable, only send GET requests, never print the key, and refuse to send it to any host other than the VitalTrends API.

FileWhat it does
morning-brief.pyToday's WHOOP recovery, with Oura readiness as a fallback, as a three-line green/yellow/red brief. Posts to a Slack incoming webhook when SLACK_WEBHOOK_URL is set. Handles days with no data yet.
weekly-training-review.pyMarkdown review of the last 7 days: volume by muscle group, sessions and exercises, heaviest set per exercise. --prs also checks exercise history for new heaviest loads. -o review.md writes a file.
withings-weight-trend.pyDaily average of Withings weigh-ins, 7-day moving average, change over the last two weeks, and a nudge when the trend reverses. Posts the nudge to Slack when SLACK_WEBHOOK_URL is set. --unit lb shows pounds.
n8n-morning-readiness-brief.jsonImportable n8n workflow for the morning brief (see n8n).

Set VITALTRENDS_TIMEZONE (for example Europe/Lisbon) to your VitalTrends profile timezone if the machine runs in a different one. Use --dry-run on the brief and weight scripts to print without posting.

cron. Keep the key in a file only you can read (chmod 600 ~/.vitaltrends.env) containing export VITALTRENDS_API_KEY=..., then:

30 7 * * * . "$HOME/.vitaltrends.env" && /usr/bin/python3 "$HOME/vitaltrends/morning-brief.py"

GitHub Actions. Use a private repository, because job logs contain the brief. Store VITALTRENDS_API_KEY and SLACK_WEBHOOK_URL as repository secrets. GitHub runs schedules in UTC and can start them late when it is busy.

name: Morning brief
on:
  schedule:
    - cron: "30 6 * * *"
  workflow_dispatch:
permissions:
  contents: read
jobs:
  brief:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-python@v5
        with:
          python-version: "3.12"
      - run: pip install requests
      - run: python morning-brief.py
        env:
          VITALTRENDS_API_KEY: ${{ secrets.VITALTRENDS_API_KEY }}
          VITALTRENDS_TIMEZONE: Europe/Lisbon
          SLACK_WEBHOOK_URL: ${{ secrets.SLACK_WEBHOOK_URL }}

Workflow recipes

Each recipe lists the trigger, the exact data it reads, the steps, a prompt for AI-based setups, and a sample output. All sample numbers are invented. All recipes are read-only.

1. Morning readiness brief

Prompt: Use VitalTrends to read my WHOOP daily data for today (the row whose cycle_start_date is today). If there is none, use today's Oura readiness. Give me one status, green, yellow or red, with a one-sentence reason based on recovery, sleep duration, HRV and resting heart rate compared with my last 14 days. Three lines maximum. Don't give medical advice.

Sample output:

Readiness 2026-11-21: YELLOW (WHOOP recovery 72% but short sleep)
Sleep 5h 42m, HRV 61 ms, resting HR 50 bpm
Suggestion: train if you like, but keep the hardest work moderate. Not medical advice.

2. Calendar guard

Prompt: Use VitalTrends to check today's WHOOP recovery and last night's sleep duration. If recovery is under 34% or sleep was under 6 hours, look at my calendar for today's hard workout blocks and suggest, but don't make, one change for each: an easier session or a different time. If neither condition is true, reply "No change needed". Not medical advice.

Sample output:

Calendar guard, Fri 21 Nov: recovery 29%, sleep 5h 55m.
"Track intervals" 18:00-19:00 looks hard for today.
Proposal: swap for a 40-minute easy ride, or move intervals to Sunday. Nothing was changed.

3. Weekly training review

Prompt: Use VitalTrends to review my training for the last 7 days. Show lifted volume by muscle group with percentages, list each session, flag exercises where I lifted a heavier load than any earlier session, and compare my average WHOOP recovery (or Oura readiness) with the 7 days before. Note any muscle group with no volume this week. Format as a short Markdown note. Not medical advice.

Sample output:

# Training review: 2026-11-15 to 2026-11-21
- Sessions: 4, sets: 62, lifted volume: 18,420 kg
- Back 39%, Quadriceps 33%, Chest 18%, Shoulders 10%. No hamstrings volume this week.
- New heaviest load: Lat pulldown 8 x 65 kg (previous 62.5 kg)
- Average recovery 61% vs 66% the week before.

4. Withings weight trend

Prompt: Use VitalTrends to read my Withings weight for the last 5 weeks. Average readings per day, compute the 7-day moving average and tell me whether the trend over the last week has reversed compared with the week before. Only mention body fat if it moved by more than 1 percentage point. Two sentences. Not medical advice.

Sample output:

Weight trend to 2026-11-21: 7-day average 79.4 kg (latest weigh-in 79.5 kg)
Change vs last week: +0.3 kg; week before: -0.3 kg
Nudge: your 7-day average has turned up after trending down. Worth a look at the last week's routine. Not medical advice.

5. Glucose evening review

Prompt: Use VitalTrends to summarize my glucose for the last 24 hours: average, time in range 70-180 and 70-140, highest reading and when it happened, and each period above 180 mg/dL with start time and duration. Keep it to four lines. Describe the data only; don't give medical or dosing advice.

Sample output:

Glucose, last 24 h: average 108 mg/dL, 70-180: 97%, 70-140: 84%.
Highest 176 mg/dL at 13:40. No readings above 180 mg/dL.
Variability (CV) 17%.

If you manage diabetes, follow your care team's guidance. This review is not a substitute for it.

6. Workout auto-log summary

Prompt: Use VitalTrends to list my Training Log sessions and unified workouts from today. For each new session, write a three-line journal entry: what I did, the heaviest set or main effort, and one observation compared with the same exercise last time. Don't change any data.

Sample output:

Fri 21 Nov, Pull day (Hevy), 52 min, 2,100 kg
Lat pulldown top set 8 x 65 kg, seated row 10 x 55 kg.
Lat pulldown is 2.5 kg heavier than your previous best.

7. Coach weekly digest (opt-in, read-only)

Prompt: Use VitalTrends to write a weekly digest for my coach covering the last 7 days: average recovery or readiness, average sleep duration, training sessions and volume by muscle group, and one line on anything unusual. Use weekly averages only, no daily raw values and no other health data. Under 120 words. Not medical advice.

Sample output:

Week of 15-21 Nov
Recovery averaged 61% (previous week 66%). Sleep averaged 6h 48m.
4 strength sessions, 18,420 kg total: back 39%, quads 33%, chest 18%, shoulders 10%.
Unusual: two short-sleep nights (Wed, Fri). Next week is a planned deload.

What you can't automate yet

Lab results, weekly recaps, Control Center, provider connections, billing, account settings, CSV export jobs and share links are not available through the API or MCP server. A "retest this lab marker in 90 days" reminder, for example, has to come from your own notes for now.

FAQ

Can an automation change my data?
Not with these templates. They only send GET requests. Writes need an API key with Allow workout write access, and through MCP OAuth also a connection where you ticked "Allow changes to my Training Log".

Which API key do automations use?
Your account's one API key from Settings → Developer. Every automation and AI connection uses the same key. Regenerating it stops all of them until you update them.

Do the templates send my health data to third parties?
Only the short message you choose to send, to the destination you configure, such as Telegram or Slack. That service then handles it under its privacy policy. If you add an AI step, the data that step reads goes to that AI provider.

Can I automate lab results?
Not yet. Lab results are only available in the VitalTrends website.

How often should an automation poll?
Every 30 minutes at most. The limit is 120 requests per minute per API key, and it is shared by every tool that uses your key.

Is this medical advice?
No. These workflows summarize your own data. Talk to a qualified professional about health decisions.