TempoLife › Features › Integrations
Integrations
An honest status for every device and app people ask about: Health Connect is live on Android, Google Fit is live on the web, Fitbit was retired, and Strava, Garmin, Polar, Oura, Withings and Samsung Health have no direct integration at all.
This page lists what is built, not what is planned. Where an integration does not exist it says so and gives the route that does work. Nothing here is a roadmap commitment.
Status of every integration
| Integration | Kind | Status | What that means |
|---|---|---|---|
| Google Health Connect | Android health platform | Live | Automatic, two-way permission prompt, works on the Android app today. |
| Fitbit | Watch and band | Retired | Existed, then was removed. The server refuses new connections. |
| Samsung Health | Phone and watch app | Not built | Not built. Nothing in TempoLife ever contacts this vendor. |
| Garmin | Watch and bike computer | Not built | Not built. Nothing in TempoLife ever contacts this vendor. |
| Strava | Activity tracking app | Not built | Not built. Nothing in TempoLife ever contacts this vendor. |
| Polar | Watch and chest strap | Not built | Not built. Nothing in TempoLife ever contacts this vendor. |
| Oura | Smart ring | Not built | Not built. Nothing in TempoLife ever contacts this vendor. |
| Withings | Smart scale and watch | Not built | Not built. Nothing in TempoLife ever contacts this vendor. |
| Apple Health | iOS health platform | Not shipped | Code exists in the repository but no released app can run it. |
The one automatic path: Health Connect
On Android, TempoLife reads Google Health Connect — the system store that health apps write into. That is the whole automatic ingestion story, and it is why the app calls the button "Connect Google Health". Steps, sleep with its stages, naps and body weight come across on the standard permission grant. Heart rate, resting heart rate, HRV and workout sessions are behind a separate per-account module that is off by default, so if you want your heart data you have to switch it on as well.
Because Health Connect is a hub rather than a vendor link, anything that writes to it reaches TempoLife: a Galaxy Watch through Samsung Health, a Garmin through Garmin Connect, a ring through the Oura app. TempoLife recognises the writing app by its Android package name and shows that as the source, so you can always see which device a number came from. Eighteen source apps are named in the app today, including Samsung Health, Garmin Connect, Polar Flow, Withings, Oura, Strava, WHOOP, Suunto, COROS, Zepp and Health Sync.
One caveat that catches people: the background worker refreshes today's step total only. Sleep, weight, heart rate and history are read by the foreground app. Open TempoLife once a day and everything catches up; leave it closed for a week and you will find gaps.
Google Fit on the web
Separately from the Android path, the website can connect a Google account and read the Google Fitness REST API for steps, sleep, weight and heart rate — and it pushes weight back to Google Fit, which makes it the only two-way link in TempoLife. It is a real, shipped code path, gated on the server holding a Google OAuth client id and secret. Where those are not configured, the connect flow tells you it is not set up rather than failing silently. Confusingly, the same "Google Health" label sits over both this and the Android Health Connect card, so check which surface you are on before concluding one is broken.
If your device is not on the list
The question to ask is never "does TempoLife support my watch" — it is "does my watch's Android app write to Health Connect". If it does, TempoLife will read it and attribute it. If it does not, no amount of configuration on this end changes that, and the fallback is manual entry. Third-party bridge apps that republish vendor data into Health Connect also work by the same mechanism; TempoLife recognises one of them by name in its source labels, but it has no relationship with any such product and cannot support it.
Frequently asked questions
Which integrations actually work?
One automatic path on Android: Google Health Connect, which carries steps, sleep, weight and — if you switch the heart module on — heart rate, resting heart rate, HRV and workouts. On the web there is a Google Fit connection, which works where the server holds Google OAuth credentials.
Does TempoLife connect to Strava, Garmin, Polar, Oura or Withings?
No. There is no OAuth client, no API call and no scheduled pull for any of them anywhere in TempoLife. On Android their data can still arrive if their own app writes it into Health Connect, which TempoLife reads.
What happened to the Fitbit sync?
It was replaced by Health Connect in v2.49.0. The connect endpoint now answers HTTP 410 and the supporting code was deleted. Fitbit data can still arrive through Health Connect on Android.
Can I import a CSV export from my old app?
No. There is a weight-only CSV parser on the server, but no screen, button or file picker reaches it. Until that ships, history has to be typed in.
Is there an iPhone app?
Not in the App Store. On iOS, TempoLife is the website added to the home screen, and a web page cannot read Apple Health.
Source: TempoLife application source — assets/js/health-connect.js, api/health_connect.php, api/sync.php, api/fitbit.php, apple/ios/App/App/TempoLifeHealthPlugin.swift · checked 2026-09-02
Every integration page
Google Health Connect
The only automatic sync TempoLife has. Everything else on Android arrives through it.
Fitbit
The direct Fitbit connection was removed in v2.49.0. New connections are refused by the server.
Samsung Health
No direct Samsung integration exists. On Android, Samsung Health data reaches TempoLife through Health Connect.
Garmin
No Garmin Connect API integration. On Android, Garmin data can reach TempoLife through Health Connect.
Strava
No Strava API integration. TempoLife has no Strava client id and never calls Strava.
Polar
No Polar Flow or Polar AccessLink integration. On Android, Polar data can arrive through Health Connect.
Oura
No Oura API integration. On Android, Oura data can arrive through Health Connect.
Withings
No Withings Health Mate API integration. On Android, weigh-ins can arrive through Health Connect.
Apple Health
There is no TempoLife iOS app in the App Store, so there is no Apple Health sync for anyone today.
Developer API · Webhooks and automations · Sign in with TempoLife
Start with the path that works
Install the Android app, connect Google Health once, and steps, sleep and weight fill themselves in from whichever device you already wear.