Forky AI for Whoop.
Forky AI connects to Whoop via direct OAuth — no Apple Health, no extra app. Every morning Forky reads your previous-cycle strain score, recovery score, and burned calories, then adjusts your daily calorie and macro targets so a 17.4-strain leg day doesn't leave you 600 kcal short by dinner. Released with Forky v1.1 in the App Store; the OAuth screen lives under Settings → Connected Apps.
- 01
- Calories burnedThe full-cycle kcal Whoop measures from your heart-rate, not a Watch estimate. This is the kcal_out side of the energy balance equation Forky uses to suggest deficit or surplus.
- 02
- Strain scoreWhoop's 0-21 cardiovascular load. Strain ≥ 17 with a hard workout signals Forky to raise your calorie target +200-300 kcal that day and bias toward protein.
- 03
- Recovery scoreThe 0-100% morning readiness metric. Low recovery flips Forky into a different mode — easier-to-digest meals, more carbs around training, more sleep nudges.
- 04
- WorkoutsType, duration, kcal. Forky tags your meals with the workout that preceded them so you can audit whether your fuelling matched the session, not just the day total.
Open Forky, go to Settings → Connected Apps, tap Whoop, log in to your Whoop account in a webview, return to Forky. Every morning at six a.m. UTC, a background job pulls your previous day's cycle: strain, recovery, kcal, workouts. The numbers feed directly into the daily target your Track tab shows — no manual import, no spreadsheet, no Apple Health detour.
v1.1 doesn't change your meal plan based on tomorrow's predicted strain — Whoop doesn't expose that data via OAuth, only same-day and history. We also don't write Forky's meals back to Whoop's Journal because that endpoint isn't public yet. If Whoop opens it, we will.
- 01“Strain 18.4 yesterday, recovery 47%. I'm raising your target +280 kcal and your protein floor by 18g — go easy at dinner but don't underfuel.”
- 02“Three sub-50 recovery scores in a row. Bumping carbs +12% for the next 48 hours and dropping the workout load on tomorrow's meal plan.”
- 03“You logged a 1,400 kcal lunch the day Whoop says you only burned 1,950 active. That's a steep midday surplus — want to lighten dinner or hold the line?”
- 04“Strain 6 today (rest day), eat 1,820 kcal not 2,100. Saved you the regret tomorrow morning.”
No. Forky talks to Whoop directly through their OAuth API. The flow works inside the iOS app and doesn't depend on the Apple Developer HealthKit entitlement — it's the reason this integration ships in v1.1 instead of waiting for v1.2.
No. v1.0 ships with manual macro logging, fridge and meal scanning, and recipe import. Whoop direct OAuth and the daily strain-aware target adjustments arrive in v1.1, a few weeks after v1.0 stabilises.
No. Strain, recovery, and burned calories are stored in your Forky account on a self-hosted backend in France, operated by Elie DTDR (Lausanne, Switzerland), used to compute your daily target, and never resold or sent to advertisers. You can disconnect Whoop in Settings at any time, which wipes the OAuth token and stops the daily sync.
Whoop's Journal lets you tick boxes after the fact. Forky tracks calorie intake from photos and recipes in real time, then uses your Whoop data to size the target the photos are scored against — different layer of the stack. Both tools play nicely; nothing prevents you from running both.
Yes — you need an active Whoop membership for their API to return your data. Forky charges its own subscription for the AI macro tracker. The two are independent.
Install Forky AI and pair your Whoop from Settings → Connected Apps.