Connections and integrations
Last updated: August 13, 2026
What a connection is
COORDINATOR is a coordination workspace with an AI layer that reads across the systems you connect. On its own it only knows what you tell it. Connecting a source lets that layer see one more slice of your real life — last night's sleep, this morning's run, the training plan sitting in a Drive folder — so it can answer questions and plan around what actually happened.
Connections fall into two groups, and they behave differently.
Wearables and health sources
Devices and fitness apps that report what your body did. COORDINATOR pulls this data on a schedule, and for some providers receives it live as soon as the provider processes it.
| Source | What it brings | How you connect |
|---|---|---|
| Strava | Runs, rides, and other activities | Sign in at Strava |
| Oura | Readiness, sleep, HRV | Sign in at Oura |
| WHOOP | Strain, recovery, sleep | Sign in at WHOOP |
| Withings | Weight, body composition, sleep | Sign in at Withings |
| Suunto | Workouts and training from your watch | Sign in at Suunto |
| Hevy | Strength and lifting sessions | Paste an API key |
| Amy Food Journal | Nutrition, macros, water | Paste an API key |
Two more are listed in your settings but aren't connectable yet. Apple Health and Samsung Health read data on your phone rather than from a server, so they need the COORDINATOR Go mobile app. They show a "coming soon" note until it ships.
Apps and data sources
File and document tools. COORDINATOR reads from these when you ask it to, so it can pull a program, a plan, or a document into a conversation.
| Source | What it brings |
|---|---|
| Google Drive | Training programs, docs, and film from your Drive |
| Notion | Notes and pages from your personal workspace |
| Dropbox | Files from your personal Dropbox |
Everything is opt-in
Nothing is connected by default, and COORDINATOR receives no data from a source until you explicitly authorize it. Every connection is your choice: you opt in when you want it, you opt out whenever you like, and you can reconnect later without penalty. COORDINATOR works with nothing connected — you just won't see that source's data in it.
There's no limit on how many sources you connect. Connecting more never costs you anything on your plan.
How connecting works
Where you go is the same for everything: Settings → Integrations. Wearables live under the Wearables heading and file tools under Apps & data sources. How you authorize depends on the provider.
Most sources use OAuth. You select Connect, COORDINATOR sends you to the provider's own site, you sign in there and review exactly what's being asked for, and the provider sends you back. Your password is never typed into COORDINATOR and never reaches us. You can review or revoke that authorization from the provider's own settings at any time, independently of us.
Hevy and Amy use an API key. These providers don't offer OAuth, so instead you generate a key in the provider's settings and paste it into COORDINATOR. A key is a revocable credential, not your password — you can delete it on the provider's side whenever you want, which cuts our access immediately.
What we do with the data
We use it to provide the features described in each integration's article, for you. We do not sell it, we do not share it with other COORDINATOR users, and we do not use it to train AI models. Health and fitness data is treated as sensitive information under our Privacy Policy.
What can write back, and what can't
Most of what COORDINATOR does with a connected account is reading. Nothing writes on its own or in the background — every write below happens because you asked for it in that moment.
| Source | Can COORDINATOR write to it? |
|---|---|
| Strava, Oura, WHOOP, Withings, Suunto, Apple Health, Samsung Health | No. Read-only, always. |
| Hevy | Only your routines. Your logged workouts are never modified. |
| Amy | Yes — logging, editing, deleting, and merging journal entries is the point. |
| Google Drive, Notion | Only when you export something. The AI can read but never writes on its own. |
| Dropbox | No. We request read-only permission. |
Each article spells out exactly what changes upstream. Your training history and your health records are never edited by COORDINATOR anywhere.
Managing a connection
Open Settings → Integrations and use the menu on any connected card:
- Recent activity — see what has actually come in, which is the fastest way to tell whether syncing is working.
- Sync history — pull a window of older data. It skips anything already imported, so running it more than once is safe. Apple Health and Samsung Health don't have this, because their data is pushed from your phone rather than pulled by us.
- Reconnect — appears when a provider has stopped accepting our access.
- Disconnect — takes effect immediately.
What disconnecting does
Disconnecting revokes the access we were granted, deletes the stored credentials, stops all further data from arriving, and marks the connection inactive so nothing syncs in the background. It takes effect right away and needs no approval from us.
It does not delete data COORDINATOR already imported. To remove that too, email [email protected] from your account email address and ask us to delete it. See Privacy Policy for the full retention and deletion terms.
When something says "Reconnect required"
This means the provider is no longer accepting COORDINATOR's access. It is almost always one of three things: you revoked access on the provider's site, you changed your password there, or the provider expired the authorization on its own schedule. Select Disconnect, then Connect again to re-authorize. Once you're back, use Sync history to backfill whatever was missed while the connection was down.
Common questions
Why is older data missing?
A connection only starts receiving data from the moment you make it. Use Sync history on the card to pull in what came before. Each provider offers a different amount of history — the individual articles say how much.
Why hasn't something new arrived yet?
Check the provider's own app first. COORDINATOR can only see data the provider has finished processing, so if a workout isn't on Strava or Oura yet, it can't be here either. If it is there and still missing here after a few minutes, use Sync history.
Can I connect the same device through more than one source?
Yes, and it's common — a watch might push to both Strava and Suunto. COORDINATOR de-duplicates within each provider, but two providers reporting the same workout will appear as two records, because we can't safely assume they're the same event. Connect whichever single source is most complete if you'd rather avoid that.
Do you support Garmin, Fitbit, MyFitnessPal, or Cronometer?
Garmin, MyFitnessPal, and Cronometer are not supported. Fitbit and Pixel report through Google Health, which is built but not yet available while Google reviews our access to those restricted health scopes. Garmin watches commonly push to Strava, so connecting Strava is the usual way to get Garmin data in today.
Contact support
Email [email protected] from the address on your COORDINATOR account. Tell us which source, what you expected, and what happened instead.
Never send us a password for any connected account — we will never ask for one. If you need to send an API key for debugging, rotate it on the provider's side afterwards.
For privacy questions, data export, or deletion requests, see Privacy Policy. For the terms covering third-party integrations, see Terms of Service.