Customization · Schemas

Data Reference

A generated reference for every selectable data point and the exported structures used by Markdown, JSON, CSV, Obsidian Bases, Daily Note Injection, and Individual Entry Tracking.

Current coverage

Metric rows below are generated from HealthMetrics.swift and HealthMetricsDictionary.swift. The metric ID is the app's stable selector ID. Frontmatter keys are the canonical snake_case keys used by Markdown frontmatter, Obsidian Bases, Daily Note Injection, and custom key mapping.

Export structures

Daily file examples

---
date: 2026-06-12
type: health-data
steps: 12642
sleep_total_hours: 7.31
workout_count: 1
---

# Health Data - 2026-06-12

## Activity
- Steps: 12642

{
  "date": "2026-06-12",
  "type": "health-data",
  "units": "metric",
  "activity": {
    "steps": 12642,
    "activeCalories": 604
  },
  "sleep": {
    "totalDuration": 26316,
    "totalDurationFormatted": "7h 18m"
  }
}

Date,Category,Metric,Value,Unit,Timestamp
2026-06-12,Activity,Steps,12642,count,
2026-06-12,Heart,Heart Rate Sample,72,bpm,2026-06-12T14:20:00Z

---
date: 2026-06-12
type: health-data
steps: 12642
workout_details:
  - index: 1
    type: workout
    metric: workouts
---

Individual entry files

Individual Entry Tracking creates additional Markdown files under entries/ by default. The generic schema is YAML frontmatter only. Workout entries add a readable body with summary, heart-rate zones, laps, splits, and sample counts when that data is available.

---
date: 2026-06-12
time: "07:30"
datetime: 2026-06-12T07:30:00Z
type: workout
metric: workouts
source: Health.md
duration_sec: 2700
distance_km: 6.20
hr_avg: 142
---

Category summary

All data points

Related