Forky AI for Garmin.
Forky AI talks to Garmin Connect via their official OAuth API and pulls your activity calories, training load, and VO₂ max trend. A 90-minute Z2 run pushes your daily target up by 600-900 kcal automatically; a recovery week scales it back so you don't accidentally eat into the deload. Ships with Forky v1.2 once the Whoop integration (v1.1) is stable. The OAuth screen lives under Settings → Connected Apps.
- 01
- Activity caloriesThe kcal Garmin measured from your last activity. More accurate than a generic estimate because Garmin combines heart-rate, motion, and GPS pace — the gold standard for cardio kcal_out.
- 02
- Training loadGarmin's 7-day acute load metric. High load shifts Forky toward more carbs and protein; low load (deload weeks) shrinks the calorie target so the deficit holds without extra discipline.
- 03
- VO₂ max trendDirection matters more than the absolute number. A rising VO₂ during a deficit confirms you're not under-fuelling; a falling VO₂ tells Forky to lift the floor.
- 04
- Workouts listSport type, duration, intensity. Forky tags meals against the workout that preceded or follows them so post-run nutrition gets the right macro split, not just the right total.
Open Forky, Settings → Connected Apps, tap Garmin, log in to Garmin Connect in a webview, return to Forky. The morning sync at six a.m. UTC pulls the previous day's activities, plus the current week's training load. The Track tab's daily target moves before you even open the day's plan.
v1.2 doesn't pull Garmin's Body Battery or Stress score — they're proprietary aggregates and the API access is restricted to enterprise accounts. We also don't push Forky meals to Garmin Connect because their write endpoints are read-only at present. If Garmin opens that, we will.
- 01“26 km long run yesterday (1,850 kcal active). Today's target: +1,200 kcal vs your maintenance, biased toward carbs in your first two meals.”
- 02“Training load up 38% week-over-week. Lifting protein floor +20g and reducing the deficit to -150 kcal — you're building, not cutting.”
- 03“Three workouts cancelled this week (cross-training week?). Scaled your target down to 2,180 kcal — saves you 1,100 kcal of accidental overeating.”
- 04“VO₂ max dropped 1.2 points over four weeks during your cut. Closing the deficit by 220 kcal for the next two weeks — fitness is the canary.”
Any Garmin device whose activity data syncs to Garmin Connect — Forerunner, Fenix, Epix, Enduro, Venu, Instinct, vívoactive, even the older 235/735. The integration reads from Garmin Connect, not from the watch directly, so the watch model is invisible to Forky.
No. v1.0 ships with manual macro logging, fridge and meal scanning, and recipe import. Garmin direct OAuth arrives in v1.2 — same release window as Oura, after the Whoop integration in v1.1.
No. The integration uses the free Garmin Connect API. You only need a Garmin account and at least one Garmin device whose activities sync to it.
Not directly in v1.2 — running power is interesting but doesn't change the calorie target meaningfully versus heart-rate-based kcal. We may surface it as context in Forky if traction justifies the engineering work.
Yes. Forky lets you connect multiple sources. The arbitration rule is: for the same metric, the strap whose data is more granular wins. Garmin owns activity calories, Whoop owns recovery and strain. The Forky pulls from both.
Install Forky AI and pair your Garmin from Settings → Connected Apps.