Using SaveSlot
Data sources
A data source writes into the official tables of an extension, so your agent has measured values instead of only what you mention in conversation. Values from a data source are marked Confirmed.
Available sources
| Source | How it connects | Notes |
|---|---|---|
| Apple Health | The SaveSlot iPhone app, paired with a code or QR code shown in the console | Recommended first. Watches, scales and other apps that write to Apple Health come along |
| Garmin | Approved on Garmin's own page | Syncs from the cloud; no phone needed |
| File import | Upload an Apple Health export or a CSV | One-time. Useful for history or as a fallback |
Health Connect on Android and Google Calendar are shown in the console as coming soon; you can ask to be told when they arrive.
Which slot it writes to
A source writes into the slot that holds its official tables, for example the slot where Fitness Log is installed. If no slot has those tables yet and you have more than one slot, the console asks which slot to use before connecting. Your existing tables are not changed.
When a source stops syncing
If a source stops syncing, for example because Garmin no longer accepts SaveSlot's access, the console shows:
- what happened and how to fix it, on the source itself;
- a Retry or Reconnect button;
- an item under Needs attention on the home page.
Data already synced stays. Agents see when each value was written, so they can tell old data from fresh.
Disconnecting
Choose Disconnect on the source and confirm. Syncing stops; the records it already wrote stay in your tables with their source.