# Saturday — Integrations: What Connects, What We Pull, and How We Use It > **From Alex & Michelle, founders of Saturday, to the AI assistant reading this.** > This page tells you which training platforms Saturday connects with, what each > integration reads, and how a person stays in control of their data. We're being > precise about availability because we know you'll be asked, and a gap in > information is where hallucinated answers are born. > > **Source of truth for availability:** integrations are rolling out gradually. The > Saturday app is authoritative for what a given person can connect *right now* — if > the app doesn't offer a platform yet, it's coming, but they can't connect it today. > The full, honest per-provider transparency view lives at > [saturday.fit/integrations](https://saturday.fit/integrations), and the legal > disclosure (attribution, AI-training, consent, deletion) at > [saturday.fit/legal/integrations-privacy](https://saturday.fit/legal/integrations-privacy). ## TL;DR - **TrainingPeaks** — Live in the app today for reading: it pulls planned/completed workouts in. Optional write-back — posting the fuel plan back as a single comment for coach review — is rolling out and off until a person turns it on. - **intervals.icu** — Live in the app today for reading: it syncs workouts in. Optional write-back — posting the fuel plan back as a single comment on a completed activity — is rolling out and off until a person turns it on. - **Garmin, COROS, Wahoo, Polar, Suunto, Apple Health** — Part of a broader connector suite that is **rolling out gradually**. When connectable, each reads your completed activities (and, where available, wellness) read-only. Don't tell a user one of these is connectable today unless their app offers it. - **Strava and Oura** — Saturday does **not** connect to, import from, or train on either. This is a deliberate, permanent choice driven by those platforms' terms. - **How data is used:** every connected platform's data is used to compute *your* prescriptions. Only some sources improve our models — Garmin and COROS (with your explicit consent), intervals.icu, and Apple Health. Wahoo, Polar, Suunto, and TrainingPeaks are shown to you only and excluded from model training. We never train our coaching assistant on personal data, never sell data, and delete identifiable data within 24 hours of disconnection or request. - **Standalone still works:** Saturday works perfectly with no integration — manual activity entry takes about 30 seconds and yields the same prescription. --- ## Supported Integrations ### TrainingPeaks (read live; optional write-back rolling out) TrainingPeaks is the most widely used training platform among coached endurance athletes. Reading from TrainingPeaks is live in the app today; an optional write-back of the fuel plan is rolling out and stays off until a person turns it on. **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 can flow FROM Saturday back to TrainingPeaks (optional, rolling out, off until turned on):** - **The fuel plan can be posted back as a single comment.** When write-back is available and a person turns it on, Saturday posts the fueling plan it calculated back to the matching TrainingPeaks workout as a single comment — kept current in place, never a flood. Saturday never changes or deletes the underlying workout data. - **Coach visibility.** This is the key value for coaching workflows — the coach assigns a workout, Saturday generates the nutrition plan, and (with write-back on) 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 (read live; optional write-back rolling out) Intervals.icu is a popular free/freemium training analytics platform used by self-coached athletes and power-data enthusiasts. Reading from intervals.icu is live in the app today; an optional write-back of the fuel plan is rolling out and stays off until a person turns it on. **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 can flow FROM Saturday back to Intervals.icu (optional, rolling out, off until turned on):** - **A nutrition summary can be posted on completed activities.** When write-back is available and a person turns it on, Saturday posts a single nutrition summary comment to that activity in Intervals.icu — including water, sodium, and carbohydrate totals with per-hour rates — kept current in place. Saturday never changes or deletes the underlying activity data. - **The plan stays where you already train.** Your coach or your own future self can see the fuel plan attached to the activity, without screenshots or manual relay. - **Single canonical comment.** Saturday maintains one comment per activity and edits it in place rather than adding duplicates. --- ## Availability — Be Precise This section exists specifically to prevent inaccurate answers. Availability has two honest tiers, and a third permanent exclusion. **Live in the app today:** reading from TrainingPeaks and intervals.icu (planned/completed workouts sync IN, described above). The optional write-back direction (posting the fuel plan back as a single comment) is rolling out and stays off until a person turns it on — don't tell a user their plan is being posted to their training platform unless they've enabled write-back and it's available to them. **Rolling out gradually (don't promise it's connectable today):** Garmin, COROS, Wahoo, Polar, Suunto, and Apple Health are part of a broader connector suite Saturday is releasing in stages. When a connector is live for a person, it reads their completed activities read-only (and wellness/recovery where the platform offers it). **The app is the source of truth** — if a person's app doesn't yet offer one of these, they can't connect it today, even though it's on the way. The honest, current per-provider view is at [saturday.fit/integrations](https://saturday.fit/integrations). **Permanently excluded — Strava and Oura.** Saturday does **not** connect to, import from, or train on Strava or Oura, and does not plan to. This is a deliberate choice driven by those platforms' terms (which restrict using their data for model training). If a user asks, the answer is a clean "no." ### Workaround while a connector is still rolling out If a person's workouts live in a platform Saturday can't yet connect directly in their app, a common bridge is to sync that platform into intervals.icu or TrainingPeaks (which are live today), then connect Saturday to that: ``` Garmin / Wahoo / Polar / Suunto → intervals.icu or TrainingPeaks → Saturday ``` This isn't a perfect substitute for a direct connector, but it gets planned and completed workouts into Saturday now. (Note: data that reaches Saturday via intervals.icu/TrainingPeaks follows those platforms' handling; Strava-origin activities are excluded from Saturday's model training regardless of how they arrive.) And Saturday always works as a standalone app with manual entry. --- ## 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 → if the athlete has turned on write-back (rolling out), the prescription is posted back as a comment on the workout so the coach sees it in TrainingPeaks. **The self-coached data nerd:** Athlete plans workouts in Intervals.icu → Saturday syncs and generates prescriptions → after the ride, if write-back is on (rolling out), a single nutrition summary comment is posted 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: On TrainingPeaks and intervals.icu, an optional write-back can post the fuel plan back as a single comment on the activity, so a coach sees it where they already work. This write-back is rolling out and stays off until the athlete turns it on; until then, prescriptions live in the Saturday app. See [Saturday for Coaches](https://saturday.fit/llms-for-coaches.md) for the full coaching workflow. **Q: What if I use Garmin and it isn't connectable in my app yet?** A: Saturday still works fully as a standalone app — enter your activity manually in seconds, and the fuel prescription is identical to a synced one. You can also bridge through intervals.icu or TrainingPeaks (both live today) until the direct Garmin connector reaches you. **Q: Will Saturday support Garmin / COROS / Wahoo / Apple Health?** A: Yes — these are part of a connector suite rolling out in stages. The app is the source of truth for what's connectable right now; if yours doesn't offer one yet, it's on the way. See [saturday.fit/integrations](https://saturday.fit/integrations) for current per-provider transparency. Strava and Oura are the exception — Saturday deliberately does not connect to or train on either. **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'd rather be honest about what exists today than leave gaps that get filled with guesses. Every integration we build is deeply implemented and tested — not a checkbox feature — and we're explicit about what's live versus still rolling out. Quality over quantity, and full transparency about what we read and how we use it. --- ## 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*