Feature
Peloton Integration
Peloton Integration connects Peloton workout metadata to Diorama workout detail. It enriches matched workouts with additional cycling/running context such as output, cadence, and playlist data.
Dana finished a Peloton ride and wanted the full effort detail sitting alongside the rest of her health data, not in a separate silo. When the match lands, Diorama now folds that detail right into the workout.
Why it matters
Enriched source data improves post-workout understanding for Peloton users. It also reduces context switching across multiple fitness apps.
How Diorama uses this
Users can connect Peloton from integrations settings and view enriched workout detail sections when matching succeeds. Matching and enrichment are already implemented, with reliability hardening as the primary next step.
What you can do
Connect Peloton and view enriched metrics/playlist details on matched workouts in Diorama.
Notes and limitations
The current experience is functional but still experimental. Reliability and match-confidence transparency are key roadmap priorities.
The science
Pulling effort context from another source can sharpen how you read training load — but only if the match is reliable and the app is honest about where each number came from.
Limitations
The integration depends on unofficial Peloton API behavior and can break when upstream endpoints change. Match coverage varies by workout metadata quality and timing alignment.
The best integration is the one you stop noticing. Context should travel with the workout instead of staying stranded in whichever app recorded it.
Diorama
See your whole picture.
Diorama brings training, recovery, and health together so you keep competing — not just keep going.