Once Strava is connected, Helpers can:
Pull your recent Strava activities (runs, rides, and other workout types)
Return activity details (date, distance, duration, pace/speed, elevation)
Include performance metrics when available (heart rate, calories, power, cadence)
Provide run split details when available (pace and heart rate by split)
To enable these actions Set up a Strava integration first.
_______________________________________________________________________________________
With Strava integration Helpers can't:
Create, upload, or publish new activities to Strava
Edit existing activities (titles, descriptions, privacy, photos)
Delete activities
Interact with Strava social features (kudos, comments, follows, clubs, challenges)
Create or manage routes, segments, or starred content
Access advanced analytics like segments/PRs, heatmaps, or training calendars
Connect or manage devices, or track activities in real time
These actions have to be done manually by you in Strava.
_______________________________________________________________________________________
Working with activities (Activities)
When the Strava integration is connected, Helpers can retrieve your most recent workout activities and return them in a structured, easy-to-read format. All actions are triggered through clearly formulated prompts and are executed within the permissions of your Strava account.
Helpers can perform the following actions with activities when the Strava integration is set up:
Get last N activities (get last n strava activities)
Filter by activity type (run, ride, all)
Include key activity details (date, type, distance, duration)
Include performance metrics (average/max speed, heart rate, calories, power, cadence -when available)
Include running splits (pace, per-split heart rate, elevation changes - runs only)
To enable these actions, make sure the Strava integration is connected in your workspace.
Prompt example:
Get my last 4 Strava activities (activity type: all) and summarize each with start date, activity type, distance, duration, and average/max speed. If heart rate, calories, power, or cadence are available, include them too.
_______________________________________________________________________________________
Important note:
Choosing activity type and handling limits.
If your prompt is broad (for example, “Please provide my last 4 Strava activities”), the Helper may ask how you want the activities pulled: as all activities or only runs / rides. To avoid an extra follow-up, include the activity type in your prompt (all, run, or ride).
Also keep in mind that if you request more activities of a specific type than exist in your Strava history (for example, asking for 4 runs when only 2 runs are available), the Helper may not be able to complete the request and can return an error message. If this happens, the Helper will typically suggest quick alternatives, such as pulling the last N activities of all types, or pulling the available number of runs first and then trying to increase the number.
_______________________________________________________________________________________
Working with rides (Rides)
When you filter by ride, Helpers can pull your latest cycling activities and highlight the metrics that matter most for cycling - beyond the basics like distance and duration. This is especially useful for quick performance recaps and for pulling cycling-specific data such as cadence and power when it’s available.
Helpers can perform the following actions with rides when the Strava integration is set up:
Retrieve recent rides (get last n strava activities with activity type: ride)
Include ride details (start date, distance, duration)
Include performance metrics (average/max speed, heart rate, calories - when available)
Include cycling-specific metrics (cadence and power - when available)
Prompt example:
Get my last 4 Strava rides (activity type: ride) and summarize each with start date, distance, duration, average/max speed, and heart rate (avg/max). If cadence or power is available, include those too.
_______________________________________________________________________________________
Working with runs (Runs)
Runs often provide the most detailed view in Strava. When you filter by run, Helpers can return not only the workout basics but also split-level details when available - so you can quickly see where your pace dropped, where you pushed hardest, and how your heart rate changed across the session.
Helpers can perform the following actions with runs when the Strava integration is set up:
Retrieve recent runs (get last n strava activities with activity type: run)
Include run basics (start date, distance, duration, average/max speed or pace)
Include performance metrics (heart rate avg/max, calories — when available)
Include running splits (pace, per-split heart rate, elevation changes — runs only, when available)
Prompt example:
Get my last 3 Strava runs (activity type: run) and summarize each with start date, distance, duration, average pace/speed, and heart rate (avg/max). Then include splits and highlight where my pace slowed down the most and where my heart rate peaked.
_______________________________________________________________________________________
The Strava integration lets Helpers pull your recent workout data directly into the chat - so you can get quick recaps, pull key performance metrics, and review run-specific splits when available, without leaving your workflow.
Related article: How to generate a workout plan? https://help.sintra.ai/en/articles/13059815-how-to-generate-a-workout-plan
For the most reliable results, specify two things in your prompt: how many activities you want (n) and which activity type to pull (all, run, or ride). If something doesn’t return as expected, switching to “all” activities or requesting fewer items of a specific type usually resolves it quickly and keeps the output accurate and consistent.