Use this article to understand what the Intervals.icu integration does, connect it to Hexis, understand what data comes across, and resolve common sync issues.
What the Intervals.icu integration does
Hexis has an official integration with Intervals.icu. This pulls your planned and completed workout data - including duration, intensity, and type - directly into Hexis, where it informs your personalized Carb Coding™ and Live Energy plans.
Note: the integration is currently one-way - Hexis pulls data from Intervals.icu, but doesn't send your nutrition data back.
Connecting Intervals.icu to Hexis
To connect Intervals.icu, follow the general integration steps in Wearable Integrations and select Intervals.icu from the list. Once connected, you can confirm its status at any time by going to More > Settings > Integrations.
What data comes across
Hexis directly maps specific fields from Intervals.icu: start time, duration, and intensity, along with power or pace where relevant to your sport. For a workout to sync correctly, it needs these details filled in on Intervals.icu - Hexis can't import a workout if they're missing.
Tip: it's worth entering a start time in Intervals.icu for every workout — even an approximate one — since this is essential for Hexis to map your session correctly.
Note: if your Intervals.icu data originates from Strava - for example, if you log activities in Strava and Intervals.icu pulls them in from there - some data may not come across to Hexis. This is a Strava third-party API restriction, not a limitation of Hexis or Intervals.icu. See Wearable Integrations for the full explanation and what to do instead.
Editing a workout after it's synced
Planned workouts: the Intervals.icu calendar is always the source of truth. Any change you make there is reflected in Hexis right away.
Completed workouts: once a completed workout has landed in Hexis, make any edits - for example, correcting the intensity - directly in Hexis rather than in Intervals.icu. Edits made in Intervals.icu after a workout has already synced as completed won't carry across.
Troubleshooting workout sync
Force a refresh: pull down on the Home screen or your Fuel Plan to force Hexis to sync the latest data.
Check for overlapping workouts: having two workouts scheduled with identical timestamps in Intervals.icu can block the sync.
Check the connection: confirm Intervals.icu shows as connected under More > Settings > Integrations. If it shows as connected but isn't syncing, try disconnecting and reconnecting.
If the issue continues after trying these steps, contact support.
Why am I getting an alert saying information is missing on my workout?
This means the workout imported, but Hexis is missing details it needs to calculate your energy needs - usually start time, duration, or intensity. Open the workout in Hexis or Intervals.icu, fill in the missing fields, and sync again.
FAQs
Does Hexis integrate directly with Intervals.icu?
Yes. Hexis has an official integration with Intervals.icu that pulls planned and completed workout data - including duration, intensity, and type - directly into Hexis, informing your personalized Carb Coding™ and Fuel plans.
Can Hexis send my nutrition data back to Intervals.icu?
No. The integration is currently one-way: Hexis pulls workout data from Intervals.icu, but doesn't send your nutrition data back.
Why is my intensity data missing in Hexis after a sync?
This is most often because the data originally came from Strava rather than being entered directly in Intervals.icu - see the note on this above. If that's not the cause, add the missing intensity manually within the Hexis app.