Amy Food Journal integration

Last updated: August 13, 2026

What the integration does

COORDINATOR is a coordination workspace with an AI layer that reads across the systems you connect. Amy is the only source that reports what you actually ate — everything else tells us what your body did, not what you put into it.

Once connected, COORDINATOR can:

• Show your nutrition, macros, and water intake alongside the rest of your workspace.
• Answer questions about what you've eaten ("what did I have yesterday?", "how's my protein been this week?").
• Log food for you, straight from chat — say "I had two eggs and toast, log it" and it goes into your Amy journal.
• Trigger routines you set up yourself. Nutrition arrives as a daily record, so routines watching Amy fire on the day's totals.

This integration writes, not just reads

Amy is the exception to how every other COORDINATOR integration works. The rest are strictly read-only; Amy is read and write, because logging food is the point. COORDINATOR can, when you ask it to:

• Add food entries to your journal.
• Edit an entry you already logged.
• Delete an entry.
• Merge entries that describe the same thing.

It does these only when you ask. COORDINATOR does not log food on its own, does not adjust entries in the background, and does not set or enforce calorie targets. It records what you say you ate and reports Amy's numbers back — it does not estimate nutrition itself or evaluate your eating.

What data we receive

Your Amy journal contents: food entries with their nutrition analysis, daily totals for calories and macros, water intake, and your weight history if you record it in Amy. We do not receive your Amy password.

Amy data is used to provide the features above, 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. It is handled as sensitive health information under our Privacy Policy.

Connecting Amy is opt-in

Nothing is connected by default, and COORDINATOR receives no Amy data — and can write nothing to your journal — until you explicitly connect it. You opt in when you want it, you can opt out at any time, and you can reconnect later without penalty.

How to connect

Amy uses an API key rather than a sign-in redirect. A key is a revocable credential; it is not your password, and you can destroy it in Amy at any moment.

1. Sign in to COORDINATOR.
2. Go to Settings → Integrations.
3. Find Amy Food Journal under Wearables and select Connect.
4. COORDINATOR shows a single field asking for your Amy API Key, with a link to Amy's documentation.
5. Generate a key in Amy's settings and copy it.
6. Paste the key into COORDINATOR and submit.

Copy the key before you navigate away. Amy shows a key in full exactly once, when you create it. If you lose it you can't retrieve it — you have to mint a new one.

We check the key against Amy immediately. If it's valid the card shows as connected; if not, nothing is saved. A rejected key is usually one that was partially copied — re-copy the whole string with no leading or trailing spaces.

To bring in entries logged before you connected, use Sync history on the Amy card. It pulls a window of past days and skips anything already imported, so running it more than once is safe.

How to disconnect

You can disconnect at any time, for any reason, without contacting us.

1. Go to Settings → Integrations.
2. On the Amy Food Journal card, open the menu and select Disconnect, then confirm.

Disconnecting deletes our stored copy of your API key immediately, stops all further reading, and stops COORDINATOR being able to write to your journal.

Important: disconnecting does not revoke the key

There's nothing for us to revoke on Amy's side — the key is issued by Amy and controlled by you. Disconnecting removes our copy, which is what stops our access. If you want the key itself dead, revoke it in Amy's settings. We recommend doing both.

Food already logged to your Amy journal stays in Amy. It's your journal, and disconnecting doesn't touch it.

To delete the Amy data COORDINATOR imported on our side, email [email protected] from your account email address and ask us to delete it. See Privacy Policy for the full retention and deletion terms.

Rotating your key

Revoke the old key in Amy, generate a new one, then disconnect and reconnect in COORDINATOR with the new key. Amy identifies your account for us, so a rotated key updates your existing connection rather than creating a second one.

Common issues

Today's totals look out of date

A food journal changes all day — you edit an entry, delete a duplicate, log a late snack. COORDINATOR re-reads the day and replaces its copy of your totals rather than keeping the first version it saw, so a number moving during the day is correct behaviour. If the app and COORDINATOR still disagree after a few minutes, use Sync history.

Something I logged in chat isn't in Amy

Check whether COORDINATOR confirmed it. When a log succeeds it tells you what went in and reports your updated totals for the day. If it didn't confirm, it didn't log. Ask again — but check the journal first, so you don't end up with the entry twice.

An entry logged twice

Ask COORDINATOR to delete one of them, or remove it in the Amy app. Both work; Amy is the source of truth either way.

The food name in my journal is shorter than what I said

That's deliberate. The journal line keeps the food and the amount so it stays readable; details like brand, restaurant, and portion estimates are sent to Amy separately to improve its nutrition analysis without cluttering the entry.

Nutrition numbers look wrong

The analysis is Amy's, not ours — COORDINATOR reports what Amy returns and never estimates calories or macros itself. If a number looks off, correct the entry in Amy; the corrected version reaches us on the next sync.

Older entries are missing

COORDINATOR only starts receiving data from the moment you connect. Use Sync history to backfill.

The card says the connection has a problem

The stored key is being rejected, which means it was revoked or regenerated in Amy. Generate a fresh key and reconnect.

Contact support

Email [email protected]. Write from the email address on your COORDINATOR account so we can find it, and include:

• What you expected to happen, and what happened instead.
• The date of the entry involved, and whether it appears in the Amy app.
• Whether you were logging from chat or reading data.

Never send us your API key or your Amy password. We will never ask for either. If you've already sent a key to anyone, revoke it in Amy right away.

For privacy questions, data export, or deletion requests, see Privacy Policy. For the terms covering third-party integrations, see Terms of Service.