Kaizendex DocsOpen the app

Connecting Fitbit or Google Health

Connect your Fitbit once and Kaizendex keeps your sleep, heart rate, and workouts synced automatically — no manual syncing required.

If you wear a Fitbit, you can connect it to Kaizendex and let your health data fill in on its own. Once you're connected, your sleep, heart rate, and workouts sync automatically — you don't need to open the app or tap anything for new data to show up.

Connecting your Fitbit

  1. Go to Settings → Integrations.
  2. Tap Connect next to Fitbit · Google Health.
  3. Sign in with the Google account linked to your Fitbit and approve access on Google's consent screen.
  4. You're redirected back to Kaizendex, connected. Your history starts syncing in the background — check back in a minute or two for your first nights and days to appear.

Syncing is automatic

Once connected, Kaizendex stays in sync on its own: your Fitbit notifies Kaizendex whenever new data is ready, and Kaizendex also checks in periodically to catch anything it missed. You'll see "Auto-sync on" on the Integrations card, along with when it last ran.

Want your latest night or workout right now instead of waiting? Tap Sync now on the same card for an immediate refresh.

If your connection ever expires, the card shows Reconnect needed — tap it and sign in again the same way you did the first time.

What you get

Sleep — one entry per night, with total sleep, time in each sleep stage (deep, REM, light, awake), a Sleep stages chart of the night as it actually happened, time in bed, your bedtime and wake time, a sleep score out of 100, and your sleep efficiency. Because Bedtime and Wake time are Date/time fields, every night also shows up as a block on your Calendar automatically — no setup needed. Want the night's length spelled out as its own field? Add a Formula like dateBetween(prop("Wake time"), prop("Bedtime"), "minutes").

Heart rate — a day-by-day chart of your heart rate, plus your resting heart rate, heart-rate variability (HRV), and minutes spent in each heart-rate zone (fat burn, cardio, peak). Open any day's entry and the chart sits right in its Properties list, under the Heart Rate row — no separate section to scroll to.

Workouts — anything your Fitbit logged as an activity, with duration, average and max heart rate, calories, distance, and how much time you spent in each intensity zone. Runs and walks are special: they get their own Running 🏃 and Walking 🚶 collections (created on your first run or walk — or, if you already made a collection with that name, Kaizendex adopts it instead of creating a duplicate). Everything else — gym sessions, cycling, sports — lands in a catch-all Google Health Activities collection.

Each stream lands in its own collection — Sleep, Heart Rate, Running, Walking, and Google Health Activities — created automatically the first time it syncs. They're normal collections: chart them on your dashboard, add them to a view, open any entry like you would one you logged yourself.

Your sleep score, explained

Your sleep score is Kaizendex's own read on a night's sleep, out of 100, made of three parts:

  • Duration (50 points) — how close your total sleep came to an 8-hour goal.
  • Quality (25 points) — how much of the night was deep and REM sleep, the stages that do the most repair work, with a small deduction for time spent awake.
  • Restoration (25 points) — how much of the night your heart rate dropped below your daytime resting rate, which is a sign your body actually got to rest. If Fitbit hasn't sent heart-rate data for that night yet, Kaizendex estimates this part from your sleep efficiency instead.

A night under 3 hours isn't scored at all, so a nap won't drag down your weekly average.

The Sleep stages chart

Open any night and you'll see Sleep stages — a row of coloured bars showing when you were awake and when you were in REM, light and deep sleep, from the moment you fell asleep to the moment you woke up. Each lane is labelled with its total ("Deep · 1h 47m"), and the times under the chart mark the start, middle and end of the night.

It's an ordinary chart on an ordinary field, so it follows your theme's colours, and the lanes — their order, names and colours — are yours to change. Nights recorded without stage tracking simply show fewer lanes.

Both Sleep score and Sleep efficiency are built as Formula fields — the recipe is right there on the field, not hidden. Kaizendex fills in a sensible default, but you can open either one in the Collection builder and change the math: nudge the sleep goal off 8 hours, reweight duration vs. quality, or tweak how the score reads your heart rate. Your version replaces the default from then on. The score always recalculates itself the instant the fields it reads (total sleep, sleep stages, heart rate) change — nothing to re-run.

Choose where each data stream goes

On the Integrations card, under Data streams, you'll see one row per stream — Sleep, Heart rate, Running, Walking, Other activities — each with a collection picker and an on/off switch. Turning Running or Walking off doesn't drop those workouts; they just go to your Other-activities collection instead.

  • Collection picker — pick which collection that stream writes into. Kaizendex fills in a sensible default the first time a stream starts syncing, but you can point it anywhere: say you renamed "Sleep" to "Sleep 😴", or want workouts to land in a collection you already built — pick it here and future syncs go there. Renaming a collection never breaks its sync; the connection is remembered by the collection itself, not its name.
  • On/off switch — turn a single stream off without disconnecting the whole integration. Off means that stream stops writing; everything it already wrote stays put.

If a stream's collection gets deleted, that stream pauses automatically — you'll see a short notice right on its row, and the confirm dialog for deleting a mapped collection tells you this will happen before you commit to it. Two ways to fix it:

  • Restore the collection from Trash — the stream resumes right where it left off, with no gap and no duplicates.
  • Pick a different collection (or a new one) in the row's picker — the stream resumes, but starting from now. It doesn't automatically backfill the history it missed while paused; use Import past data (below) if you want that history too.

Nothing is ever silently recreated on your behalf.

Which fields you can edit

Every value your wearable fills in is normally read-only, but not all of it is locked the same way:

  • A handful of fields — like a night's Bedtime and Wake time — are what Kaizendex calls protected: they're what the sync actually keys off of to match up your data night to night, so their value stays locked and they can't be deleted or have their type changed while the connection is active. You can still rename, hide, or reorder them freely; if you truly want them gone, disconnect the stream first (its row's on/off switch, or Disconnect for the whole integration).
  • Everything else your wearable fills in — calories, average heart rate, sleep stages, and so on — is fully editable: type over a value and it sticks, your edit wins over what the wearable reports on the next sync. Delete one of these fields and Kaizendex remembers your choice — it's never silently added back.

A small ⟳ icon next to a synced field's name is your cue that it's filled in automatically; hover or tap it for a reminder of where it comes from.

Bringing back history: Import past data

If a stream paused and you re-mapped it to a new collection, or you deleted an entry you later wanted back, syncing normally won't reach into the past to restore it — that's on purpose, so nothing you deleted comes back without you asking for it. When you do want it back, use Import past data on the stream's row in Settings → Integrations: pick a window (30 days, 90 days, or everything) and Kaizendex re-fetches that range, including any individually deleted entries inside it.

On the Running or Walking row, Import past data does one extra thing: any run or walk that previously landed in your Other-activities collection is moved into its proper collection, and the leftover duplicate is cleaned up (soft-deleted — recoverable from Trash like anything else).

Disconnecting never deletes your data

Tapping Disconnect removes Kaizendex's saved access to your Fitbit account and pauses its streams. It does not touch anything already synced — every night of sleep, every workout, every collection stays exactly where it is. There's no "also delete the data" prompt, because there's no such option: the only way synced data leaves Kaizendex is you deleting it yourself, the same way you'd delete anything you logged by hand.

Reconnecting later

Fitbit connections occasionally need refreshing — you'll see this as Reconnect needed on the Integrations card if it happens. Tap Reconnect and sign in again; nothing you've already synced is lost, and syncing picks back up where it left off.

Next