Apple Health data pipeline · January 2026
HealthAgent
My nutrition and activity lived in different apps. I brought their Apple Health exports together so I could see the trends in one place.
Solo engineer. Ingestion through to the dashboard, auth and cloud deploy included.
Two apps, no shared view
Nutrition came from MacroFactor and activity data came from Apple Watch. Apple Health was the common source, but it did not provide the comparative view I wanted.
Keep the raw exports
Daily exports are retained before normalisation, per-user ingest tokens protect writes, and derived data remains scoped to the authenticated account.
Runs locally or on GCP
A Fastify and Prisma API writes canonical Postgres tables. Cloud Run, GCS, Secret Manager, and Cloud Scheduler support daily processing, while local storage and sample data keep development practical.
The dashboard
The repository includes a real Status view showing trends, projections, and processed ingest files. Optional model-backed insights are deliberately separate from the working ingestion and metrics path.
What this is not
This is a data pipeline, not a medical tool. Nothing in it is clinically validated, and the generated suggestions are not health advice.
Outcome
A working end-to-end ingestion and trend pipeline; generated insight backends remain optional and are not medical advice.