See which meetings spike your stress
Line up your intraday stress with your calendar to find which meetings, and which people, wind you up.
Data you need:
- Intraday stress: garmin
Also needs (in the same chat):
- Google Calendar
See what stress data you have
First, let your assistant discover which stress metrics are on your account and how far back they go. This also confirms your watch actually records the all-day stress signal.
Run list_metrics and show me which stress and body-battery metrics I have, with their date ranges and source.
Always run list_metrics first, because metric names differ per device.
Pull one busy day at full detail
Ask for a single meeting-heavy weekday at 3-minute resolution. The raw payload carries the intraday stress curve, not just the daily average.
Using query_metrics with include_raw, pull stress_avgStressLevel for last Tuesday. Read the timeOffsetStressLevelValues series. Ignore any negative values (-1 to -5 mean no reading, not calm). Convert each point to my local wall-clock time using startTimeInSeconds and startTimeOffsetInSeconds, and describe how my stress moved through the day.
Line it up with your calendar
Now bring in your calendar connector in the same conversation and let the assistant overlay your meetings on the stress curve.
Pull my Google Calendar events for that same day. For each meeting, tell me my average stress during it (excluding no-reading values) and how it compares to my daily baseline. Which meetings, and which attendees, line up with my biggest stress climbs?
What you'll see
You'll get a readout roughly like this: a calm morning baseline, a sharp climb through a back-to-back block of afternoon meetings, and a slow recovery afterwards. Meetings with certain attendees or certain formats (large group, status reviews) tend to show up as the steepest climbs.
The numbers in this recipe are illustrative, not from a real day.
Good to know
Garmin only today. Garmin is the one source freddy holds a true intraday stress signal for. WHOOP cannot do this, because its API exposes no intraday stress or heart-rate data at all.
Your calendar connector must be active in the same conversation as freddy, or the assistant only sees the stress curve with no meeting labels.
Negative stress values (-1 to -5) are gaps (off-wrist, motion, not enough data), not low stress. Averaging them in will quietly skew the result.
Attribute the data as Garmin.