Forky AI for Strava.
Forky AI connects to Strava through their OAuth API and pulls every activity you upload — running, cycling, swimming, gravel, gym. The kcal Strava estimates feed Forky's daily target so the day after a 70 km gravel ride doesn't leave you under-fed at 1,800 kcal. Releases with Forky v1.2, after the Whoop integration in v1.1. The OAuth screen lives under Settings → Connected Apps.
- 01
- Activity calorieskcal per activity as Strava computes them from your power meter, heart-rate strap, or estimate model. Forky weights heart-rate activities higher than estimate-only activities for accuracy.
- 02
- Distance and durationUsed by Forky to time post-activity meals — a 40-minute interval session triggers a different protein-timing nudge than a 4-hour endurance ride.
- 03
- Sport typeRun, ride, swim, ski, hike, gym. Forky biases the meal plan toward carbs after long aerobic work and toward protein after lifting, based on what Strava saw.
- 04
- Activity datesSo Forky can build a weekly load picture and adjust the cumulative target — not just react meal-by-meal, but pace your fuelling across a training block.
Open Forky, Settings → Connected Apps, tap Strava, log in to Strava in a webview, return to Forky. The sync runs every six hours so a workout uploaded in the afternoon shows up in the evening's meal target. The Track tab gains an activity strip under the daily ring, showing your last three activities and their kcal contribution to today's target.
v1.2 doesn't push Forky meals to Strava — Strava's API is read-only for nutrition data. We also don't pull segment leaderboards, kudos, or comments — irrelevant for AI macro trackering. We do pull private activities you've granted scope to; everything stays under your privacy settings.
- 01“85 km ride at 0.78 IF yesterday (3,200 kcal). Today's target: 3,400 kcal with carbs up 24% for the first two meals — refuel the glycogen before the deficit starts.”
- 02“Three rest days in a row (the calendar shows you tapered for a race). Target dropped to 2,090 kcal — you don't need to chase last week's intake.”
- 03“Two heart-rate-based runs and one estimate-only ride this week. The HR runs count full; the estimate ride got a 15% conservative haircut.”
- 04“Threshold session at 6:34 p.m. Suggested 20g protein and 40g fast carbs in the next 60 minutes — your meal plan auto-shifted to a recovery-friendly dinner.”
The integration uses the free Strava OAuth API. You don't need Strava Premium for it to work, though Premium unlocks more granular metrics (like Fitness & Freshness) that Forky may use in future versions.
No. v1.0 ships with manual macro logging, fridge and meal scanning, and recipe import. Strava direct OAuth arrives in v1.2 alongside Oura and Garmin, after the Whoop integration in v1.1.
Strava's kcal numbers are noisy without a power meter — they can be off by ±20% for estimate-only activities. Forky applies a sport-specific haircut (estimate-only activities get -15%) and caps the daily kcal bump from a single activity at +1,800 kcal so a misreported ride doesn't tell you to eat 7,000 kcal.
Not in v1.2. We pull activities, not goals — Strava's goals don't map cleanly onto nutrition targets. If we add a goals integration later, it'll be opt-in on the Forky side.
Yes. When the same activity is logged in both Strava and Garmin Connect (common), Forky dedupes on timestamp + duration so you don't get a double-count. Whoop's strain runs alongside as a recovery signal, not an activity signal.
Install Forky AI and pair your Strava from Settings → Connected Apps.