How to Set Up Custom Streams in Intervals.icu for Your Sensors

By Toby Pattullo
Australian Deaflympic marathon and ultra runner, and the solo developer behind IcuSync.
Your watch or bike computer often records more than power, heart rate and cadence. A Stryd (opens in a new tab) pod adds form power and air power. A Connect IQ (opens in a new tab) data field can add wind, gear ratio or battery level. Muscle oxygen, core temperature and breathing sensors all write their own data into the activity file.
Intervals.icu stores that file, but it only shows the fields it recognises.
Custom streams let you tell Intervals.icu which extra fields to pull out, so they appear on your activity charts and your AI assistant can analyse them through IcuSync.
This guide covers what custom streams are, how to set one up, how to apply it to past activities, and what to ask Claude, ChatGPT or Grok once your data is in.
What is a custom stream?
A stream is a second-by-second line of data across an activity, like your power or heart rate trace. Intervals.icu creates the standard ones automatically.
A custom stream is one you add yourself. It reads a named field from your activity file, usually a developer field written by a sensor or a Connect IQ app, and turns it into its own line of data. Once set up, it works for every new activity that contains that field.
You might need one if:
- A sensor shows numbers on your watch, but they are missing in Intervals.icu
- You use a Connect IQ data field and want its values on your activity chart
- You want Stryd metrics like form power, air power or leg spring stiffness
Check first: you may not need one
Intervals.icu already reads many extra sensors without any setup. These usually appear on their own when your device records them:
| Data | Typical source |
|---|---|
| Running dynamics (ground contact time, vertical oscillation, vertical ratio, step length) | Garmin HRM-Pro, Running Dynamics Pod, newer watches |
| Running power, leg spring stiffness, impact loading rate | Stryd (opens in a new tab) pod (form power and air power still need a custom stream, see below) |
| Core body temperature | CORE (opens in a new tab) sensor |
| Muscle oxygen (SmO2) | Moxy (opens in a new tab) and similar sensors |
| Breathing rate and volume | Tymewear (opens in a new tab) smart sensor |
| Blood glucose | Supported glucose monitors |
| DFA alpha 1 | Calculated by Intervals.icu from heart rate variability |
Quick check: open a recent activity and look through the chart options. If you can already see the metric, you are done. Field names vary between devices and apps, so if it is missing, a custom stream is the fix.
Before you start
Sync straight from your device. Activities must come from Garmin, Coros, Suunto, Polar, Wahoo or a file upload. Activities that arrive through Strava do not carry the original file, so the extra fields are lost.
You also need:
- A recent activity that recorded the sensor. The setup reads field names from the activity you have open.
- A rough idea of the field name. If you are unsure, open the activity's FIT file in a free viewer such as fitfileviewer.com (opens in a new tab) and look at the record messages for the field name.
How to add a custom stream
Step 1: Open an activity that has the data
Open an activity recorded with the sensor or Connect IQ field connected.
Step 2: Open Custom Streams
Open any activity and click Customize (top right, next to Notes). Choose Timeline, click Custom Streams at the bottom, then Add Stream.
Save yourself some work: use the search on the Custom Streams screen first. Other athletes may have already shared a stream for the same sensor, so you don't need to work out the field name.
Step 3: Fill in the stream
- Name: a short, clear name. This is what appears on your charts and what IcuSync uses to identify the data.
- Record field: choose the field from the dropdown. The list comes from the activity you have open.
- Units: for example
W,ms,%or°C. Streams with the same units share an axis on your charts.
Names are case sensitive. The record field must match the name in your file exactly, so pick it from the dropdown rather than typing it.
Save the stream.
Step 4: Reprocess the activity
On the activity, click Actions, then Reprocess File. Your new stream should now appear on the chart.
Why reprocess? Streams are created when an activity file is processed. Reprocessing tells Intervals.icu to read the original file again and pull out your new field.
Applying a custom stream to past activities
From now on, every new activity that contains the field gets the stream automatically. For older activities:
- Go to the Activities list view (the table, not the calendar)
- Filter to the sport you need
- Tick the activities you want to update
- Click Edit at the top and choose Reprocess File
- Tick Keep existing intervals, then click OK
Don't skip "Keep existing intervals". Without it, Intervals.icu detects your intervals again from scratch, and any laps you edited by hand may change.
Common examples
Stryd running metrics
Form power, air power, leg spring stiffness, impact loading rate and more. Our separate guide has the exact names and fields: Unlocking Stryd data in IcuSync.
Connect IQ data fields
Apps from the Connect IQ Store (opens in a new tab) that run as a data field on Garmin watches and Edge computers write their values as developer fields. Wind data, gear ratio and similar fields can be pulled into a custom stream if the app records them every second.
Muscle oxygen sensors with different names
Some SmO2 devices, such as Train.Red (opens in a new tab), name their channels differently from Moxy, so Intervals.icu may not recognise them. A custom stream mapped to the device's field fixes this.
A second power meter
If you record two power sources, such as pedals and a smart trainer, a custom stream can keep the second one, for example named "PM Power", so you can compare them.
Advanced: script streams
A custom stream can run a short JavaScript script instead of reading a single field. It can read any message in the file, or calculate a new stream from existing ones, such as power divided by breathing volume. The Intervals.icu forum (opens in a new tab) has examples.
Using your custom streams with AI
Once a custom stream is set up, IcuSync picks it up automatically. There is nothing to configure on the IcuSync side.
When you ask about an activity, your AI assistant uses the get_extended_metrics tool. IcuSync reads the stream on its own servers, averages it for each interval and passes back a short summary.
Your recordings stay untouched. Your AI assistant never handles the raw second-by-second data, and IcuSync never changes it.
Well-known sensors such as Stryd and Tymewear get clear labels automatically. Any other stream is returned under the name you gave it, so a clear name with units helps your AI assistant understand it.
Try asking:
Show me the custom sensor data from yesterday's ride, per interval.
How did my muscle oxygen change across the VO2 max intervals on Tuesday?
Compare my core temperature on today's long run with last week's, given the heat.
Does my form power rise as I fatigue in my long runs?
Why IcuSync doesn't create streams for you
You set up custom streams in Intervals.icu, and IcuSync only reads them.
That choice stays with you. Adding, renaming or deleting a stream changes how your history is stored and can break charts or scripts that rely on it. Streams also stay read only, so the data your sensors recorded is never changed.
You can see the full list of what IcuSync can read and write on the tools page.
Troubleshooting
The field is not in the Record field dropdown
The list comes from the activity you have open. Make sure that activity was recorded with the sensor connected, or try a different recent one.
The stream is set up but shows no data
Reprocess the activity after adding the stream. Also check the activity came straight from your device, not through Strava.
The stream still does not appear on the chart
Delete the stream and add it again with the same name, then reprocess the activity. This clears a cached version.
My AI assistant says it can't find the data
Ask about a specific activity that you have reprocessed since adding the stream. Older activities only include the stream after you reprocess them.