How to Connect Amazfit Watch to ChatGPT and Claude.ai

Amazfit works with STAS when your Zepp account sends completed activities to Intervals.icu. First confirm that one recent workout appears in Intervals.icu with distance, duration, GPS, heart rate, and useful lap or interval detail. Then sign in to STAS with the same Intervals.icu account and ask ChatGPT or Claude.ai to update your data.

• Your Amazfit watch must already sync correctly to the Zepp app.
• Use the same Zepp account that your watch uses on your phone. Account mismatch is the most common sync problem.
• You need an Intervals.icu account and access to Settings → Connections.
• For ChatGPT or Claude.ai, use the same Intervals.icu account when signing in to STAS.
• If you also use Strava, keep it as a social log or extra analysis source, not as the preferred STAS data path.

1. 1Open Zepp on your phone and sync the watch first. If the workout is not visible in Zepp, Intervals.icu and STAS cannot see it.
2. 2Open Intervals.icu → Settings → Connections and find the Amazfit box. Start authorization and sign in with the same Zepp account used by the watch.
3. 3Enable completed activity download. Intervals.icu receives activities through webhooks and also polls recent activities when you visit the app.
4. 4Enable wellness data if you want STAS to use steps, sleep, resting heart rate, and similar context when Zepp provides it.
5. 5If you need older activities, use Download Old Data in Intervals.icu. The first automatic poll is mainly for recent activity and missed webhooks.
6. 6Open Intervals.icu → Activities and check one recent Amazfit workout. Only after it looks useful there, sign in to STAS with that Intervals.icu account.
7. 7In ChatGPT, open STAS GPT. In Claude.ai, add STAS as a custom connector and use the same Intervals.icu authorization.

Verify a real workout, not just the connection screen. STAS can only coach from fields that reached Intervals.icu.

• Correct date, sport type, duration, distance, and GPS track.
• Heart rate, pace, cadence, power, and other metrics you care about.
• Lap or interval structure if you want interval analysis.
• Wellness fields such as sleep, resting HR, HRV, or readiness only if they actually appear for your setup.
• A second new workout syncing automatically after the initial setup.
• If a planned workout is important, test one easy session before trusting a key workout.

After Intervals.icu shows a real Amazfit workout, ChatGPT and Claude.ai use the same STAS context. The connection path is different in each AI app.

Amazfit workout push is useful, but model- and workout-type-specific. Treat it as something to test on your exact watch before relying on key sessions.

1. 1In Intervals.icu, enable planned workout upload for Amazfit if the option is available on your account.
2. 2Intervals.icu can upload the next week of planned workouts and refresh them several times per day.
3. 3Supported behavior is strongest on newer models such as T-Rex 3 Pro and Balance 2; support can differ by watch and firmware.
4. 4Open Zepp on your phone to sync the plan from Zepp to the watch.
5. 5For structured sessions, start simple: run or ride, clear steps, no unusual targets. Check how the workout appears on the watch before a key day.

• Do not assume every Amazfit model exports the same detail. Verify your exact watch and sport type in Intervals.icu.
• Wellness, HRV, readiness, power, cadence, and lap detail depend on Zepp support, firmware, permissions, and Intervals.icu support at the time.
• If intervals appear as one total block, try Intervals.icu re-analysis options such as using laps when the source file has lap data.
• Workout push may be limited to specific models and workout types. Strength or unusual sport types may not transfer.
• Amazfit can sync to Strava through Zepp, but for STAS the direct Zepp → Intervals.icu path is preferred.
• STAS does not invent missing fields. If Intervals.icu does not show the detail, ChatGPT or Claude.ai should not make strong conclusions from it.

Strava’s official MCP connector is useful if you want Claude to answer questions from live Strava data. It is read-only and focused on Strava history, trends, and training load. STAS is different: it is a training workflow around Intervals.icu, your profile, goals, rules, calendar, workout reports, and plan write-back after approval.

• Use the Strava connector when your question is mainly about Strava history inside Claude.
• Use STAS when you want ChatGPT or Claude.ai to coach from Intervals.icu data, your saved context, and your plan.
• For STAS quality, connect Amazfit directly to Intervals.icu when possible. Strava-routed activities may hide workout details that STAS needs, such as distance, time, pace, heart rate, power, laps, and intervals.
• Strava can remain connected for social sharing. It should not be the preferred bridge between Amazfit and STAS when a direct Zepp → Intervals.icu path works.

Connect STAS after Intervals.icu already shows a useful Amazfit workout. Then use STAS in ChatGPT or Claude.ai and ask: “Update my data”, “Review my latest Amazfit workout”, or “Compare this week with my plan”. If the workout is missing or incomplete in Intervals.icu, fix that layer first.

This page is based on Intervals.icu’s Amazfit/Zepp support announcement and discussion, Amazfit’s public Zepp sync instructions, Strava’s official MCP documentation, and STAS internal product rules about direct source sync.