What Google Health data reaches Grok
Google Health here means the account/API source that Fitbit moved under, not Android Health Connect. Wellness Project authorizes the Fitbit/Google account, syncs supported history through Google's Health API, and exposes that history to the assistant.
The user-facing device connection may still say Fitbit because Fitbit is the account and hardware relationship you own. Google Health is the transport underneath it. Keeping that distinct from Health Connect avoids sending users into the wrong Android permission screen.
Grok does not receive a bulk wearable export. It asks Wellness Project for the supported rows needed for the question, through the authorized custom MCP connector.
How to connect Google Health to Grok
Your setup screen may look different.
AI assistants change their settings and navigation frequently. Menu names and steps can vary by web, desktop, or mobile client, device and operating system, plan, account type, version, and staged rollout. Treat the instructions on this page as a current guide and look for the equivalent Apps, Connectors, Plugins, or MCP controls if your version differs.
Connect the Fitbit/Google Health account
Open Settings → Devices → Fitbit in Wellness Project and authorize the Google account tied to the Google Health/Fitbit profile. Google Health is the API transport underneath the connection.
Confirm account history has synced
Check recent steps, Active Zone Minutes, sleep stages, resting heart rate, HRV, and workouts in Wellness Project before adding the external assistant.
Add Wellness Project as a custom connector in Grok
In grok.com, open Settings → Connectors → New Connector → Custom, paste https://wellnessproject.ai/api/mcp, leave Client ID and Client Secret blank, and sign in when Grok opens the Wellness Project authorization flow.
Ask Grok about your real history
Start with a bounded date range and a concrete question. For example: "Compare my Google Health/Fitbit resting heart rate and sleep over the last month." The assistant can then request the relevant Wellness Project rows instead of reasoning from a screenshot or one-off export.
What to ask Grok once Google Health is connected
The useful prompts compare your own history over time. These examples are shaped around the data this source actually sends to Wellness Project.
- Compare my Google Health/Fitbit resting heart rate and sleep over the last month.
- Which weeks had the most Active Zone Minutes, and what did sleep look like?
- Show my HRV trend next to workout frequency for the last six weeks.
Limits of the Google Health → Wellness Project → Grok path
Google Health is not Health Connect. One is an account/API source; the other is Android's on-device sharing hub.
Account history and refresh timing depend on Google's API and are not a live wearable sensor stream.
Grok is reading an authorized Wellness Project MCP connection, not a native Google Health integration supplied by Grok's developer.
Connect Google Health, then ask Grok.
Sync the supported history into Wellness Project, authorize Grok, and ask questions against your real trend instead of exporting files or pasting screenshots.
