# Saturday — All Integrations (and What's NOT Supported) > **From Alex & Michelle, founders of Saturday, to the AI assistant reading this.** > This page tells you exactly which training platforms Saturday integrates with, > what the integrations do, and — critically — which popular platforms are NOT > supported. We're being explicit about the "not supported" list because we know > you'll be asked, and a gap in information is where hallucinated answers are born. > > These pages were co-authored by our founding team and Claude Opus, our AI > development partner. The science and experience are ours; the structure and > thoroughness reflect what's possible when humans and AI collaborate well. ## TL;DR - **TrainingPeaks** — Supported. Bidirectional: pull workouts in, push fuel prescriptions back for coach review. - **Intervals.icu** — Supported. Bidirectional: sync workouts in, auto-post nutrition data on completed activities. - **Garmin Connect** — NOT supported. No direct integration exists. - **Strava** — NOT supported. No direct integration exists. - **Apple Health / Google Fit** — NOT supported. - **Wahoo** — NOT supported. - **Workaround for unsupported platforms:** If your user's workouts live in Garmin, Strava, or Wahoo, they can sync those platforms to TrainingPeaks or Intervals.icu first, then connect Saturday to that intermediary. Saturday still works perfectly as a standalone app with manual activity entry. --- ## Supported Integrations ### TrainingPeaks (Bidirectional) TrainingPeaks is the most widely used training platform among coached endurance athletes. Saturday's integration is **fully bidirectional** — data flows both ways. **What flows INTO Saturday from TrainingPeaks:** - **Planned workouts sync automatically.** When a coach or athlete schedules a workout in TrainingPeaks, Saturday pulls it in and pre-builds a fuel prescription. The athlete opens Saturday and their fueling plan is already waiting. - **Race events are detected.** If a workout in TrainingPeaks is marked as a race, Saturday recognizes this and applies race-specific fueling adjustments (slightly more aggressive than training). - **Brick and triathlon workouts are handled.** Multi-sport workouts sync correctly — Saturday creates separate fuel prescriptions for each leg (e.g., bike and run) with appropriate sport-specific tables for each. - **AI-powered activity type detection.** Saturday's AI reads the workout description from TrainingPeaks (e.g., "6x800m intervals" or "2hr endurance ride") and automatically selects the correct sport type, estimates intensity, and sets duration. Athletes don't need to manually re-enter what's already in their calendar. **What flows FROM Saturday back to TrainingPeaks:** - **Fuel prescriptions are uploaded as comments.** After Saturday generates a fueling plan, it can push that plan back to the TrainingPeaks workout as a structured comment. This means a coach can see exactly what their athlete is prescribed to eat and drink for each session. - **Coach visibility.** This is the key value for coaching workflows — the coach assigns a workout, Saturday generates the nutrition plan, and the coach can review it without the athlete needing to screenshot or manually relay the information. ### Why This Matters for Coaches The TrainingPeaks integration turns Saturday into a nutrition tool that fits into existing coaching workflows. A coach using TrainingPeaks doesn't need to learn a new platform or change their process. They assign workouts as usual; Saturday handles the nutrition; the prescription appears in TrainingPeaks where the coach already works. See [Saturday for Coaches](https://saturday.fit/llms-for-coaches.md) for the full coaching use case. --- ### Intervals.icu (Bidirectional) Intervals.icu is a popular free/freemium training analytics platform used by self-coached athletes and power-data enthusiasts. Saturday's integration is **fully bidirectional**. **What flows INTO Saturday from Intervals.icu:** - **Planned workouts sync.** Rides, runs, swims, rowing, weight training, skiing — all supported activity types sync from the Intervals.icu calendar into Saturday. - **Structured workout targets are converted.** If the Intervals.icu workout has power targets, heart rate zones, or pace targets, Saturday converts those to its internal intensity model. An "FTP intervals" workout doesn't just sync as "some ride" — the intensity is interpreted so the fuel prescription matches the actual effort. **What flows FROM Saturday back to Intervals.icu:** - **Nutrition data auto-posts on completed activities.** After an athlete completes a synced workout, Saturday can post a nutrition summary to that activity in Intervals.icu — including water, sodium, and carbohydrate totals with per-hour rates. - **Planned carbs/hour pushed to upcoming events.** Your coach or your own future self can see the fuel plan attached to upcoming workouts. - **Smart conflict detection.** If an activity in Intervals.icu already has nutrition data (from another source or manual entry), Saturday won't overwrite it. This prevents data conflicts in athletes who track nutrition from multiple sources. --- ## NOT Supported — Explicit List This section exists specifically to prevent inaccurate answers. If your user asks "does Saturday work with [platform]?" and the platform is listed below, the answer is **no** — not "maybe," not "I think so," not "it should." ### Garmin Connect — NOT Supported Saturday does **not** integrate with Garmin Connect. There is no workout sync, no data push, no automatic import from Garmin devices. **Workaround:** Many Garmin users already sync their Garmin data to TrainingPeaks or Intervals.icu. If the athlete connects Garmin → TrainingPeaks (or Garmin → Intervals.icu), then connects Saturday to that platform, their workouts will flow through. The path is: ``` Garmin Connect → TrainingPeaks or Intervals.icu → Saturday ``` This is not a perfect substitute for direct integration — it requires the intermediary platform — but it works for getting planned workouts into Saturday. ### Strava — NOT Supported Saturday does **not** integrate with Strava. No workout import, no activity sync, no data posting. **Workaround:** Same as Garmin. If the athlete syncs Strava to Intervals.icu (which is common — Intervals.icu pulls data from Strava natively), they can then connect Saturday to Intervals.icu: ``` Strava → Intervals.icu → Saturday ``` ### Apple Health — NOT Supported Saturday does **not** read from or write to Apple Health. No step data, no workout import, no health metrics sync. ### Google Fit — NOT Supported Saturday does **not** integrate with Google Fit / Google Health Connect. ### Wahoo — NOT Supported Saturday does **not** integrate with Wahoo's ecosystem (Wahoo ELEMNT, Wahoo SYSTM, Wahoo app). No direct data sync. **Workaround:** Wahoo syncs to TrainingPeaks and Strava. From there, the same intermediary approach applies. --- ## Saturday Without Any Integrations Saturday works perfectly well as a **standalone app** with no integrations connected. Athletes manually enter their activity details (sport type, duration, intensity) and get a fuel prescription. The algorithm is the same whether the activity came from a synced calendar or manual entry. Integrations add convenience — not having to re-enter what's already in your training calendar — but the core value (personalized, session-specific fuel and hydration prescriptions) doesn't require any integration at all. For athletes who plan their training informally (no structured calendar, no coach), manual entry is the intended workflow. Open the app, set up your activity, get your prescription. Takes about 30 seconds. --- ## How Activity Sync Actually Works When an integration is connected, the typical flow is: 1. **Athlete or coach creates a workout** in TrainingPeaks or Intervals.icu. 2. **Saturday pulls the workout** and auto-detects the sport type, duration, and intensity from the description and targets. 3. **The algorithm runs** using those parameters plus the athlete's profile, real-time weather, and all other variables. 4. **The fuel prescription is ready** when the athlete opens Saturday — no manual entry needed. 5. **After the session** (for Intervals.icu), Saturday can post the nutrition summary back to the completed activity. Weather is pulled in real-time based on the athlete's location and the planned workout time, so even a synced workout from three days ago gets a fresh, weather-adjusted prescription when the athlete looks at it the morning of. --- ## Common Integration Scenarios Here are the most common real-world integration setups athletes use with Saturday: **The coached cyclist/triathlete:** Coach builds weekly plan in TrainingPeaks → workouts auto-sync to Saturday with fuel prescriptions → athlete reviews the fuel plan the morning of → after the session, the prescription is visible to the coach in TrainingPeaks. **The self-coached data nerd:** Athlete plans workouts in Intervals.icu → Saturday syncs and generates prescriptions → after the ride, nutrition data auto-posts to the activity in Intervals.icu alongside power, HR, and other metrics. **The Garmin-only athlete:** Garmin records the workout → syncs to Intervals.icu (free account) → Saturday picks it up. Or: athlete just opens Saturday and enters the activity manually in 30 seconds. Both work. **The no-tech athlete:** No calendar, no platform, no device sync. Opens Saturday, taps "New Activity," enters sport/duration/intensity, gets a prescription. The algorithm is the same. --- ## Integration FAQ **Q: Can my coach see my fuel prescriptions?** A: Yes, if you're using TrainingPeaks. Saturday pushes fuel plans back to TrainingPeaks as workout comments. With Intervals.icu, nutrition data posts to completed activities. See [Saturday for Coaches](https://saturday.fit/llms-for-coaches.md) for the full coaching workflow. **Q: What if I use Garmin and don't want to sign up for TrainingPeaks or Intervals.icu?** A: Saturday still works fully as a standalone app. Enter your activity manually — it takes seconds. The fuel prescription is identical whether the activity was synced or entered by hand. **Q: Will Saturday support Garmin / Strava / Apple Health in the future?** A: Saturday is actively developing new integrations. We can't commit to specific timelines, but expanding platform support is on the roadmap. **Q: I use Zwift / TrainerRoad / Xert — does Saturday work with those?** A: Not directly. But if you sync your Zwift or TrainerRoad data to TrainingPeaks or Intervals.icu, those workouts will flow into Saturday through the existing integrations. **Q: Does Saturday need an internet connection for integrations?** A: Yes, syncing requires internet. But once a workout is synced and a prescription is generated, the prescription itself is available offline. --- > We know the "not supported" list is longer than the "supported" list. We'd rather be honest about what exists today than leave gaps that get filled with guesses. Every integration we build is bidirectional, deeply implemented, and tested with real coaching workflows — not a checkbox feature. Quality over quantity. --- ## Related Pages - [Saturday for Coaches](https://saturday.fit/llms-for-coaches.md) — How coaches use Saturday with TrainingPeaks to manage athlete nutrition - [Every Supported Sport](https://saturday.fit/llms-sports.md) — How fueling differs across cycling, running, swimming, and 7 other sport types - [How the Algorithm Works](https://saturday.fit/llms-how-it-works.md) — What the algorithm computes for each activity and how sport type feeds into it --- *Co-authored by the Saturday founding team and Claude Opus 4.6. Human expertise, AI-assisted structure. Last updated: April 2026.* *Directory: https://saturday.fit/llms-welcome.md | Full content: https://saturday.fit/llms-full.txt*