--- title: "Strava Integration" description: "Connect over OAuth to read athlete profiles and stats, create and update activities, explore segments, browse clubs, and look up gear and routes through the Strava API v3." url: https://flowrunner.ai/integrations/strava date_modified: 2026-08-07T17:20:23-07:00 --- # Strava [Utilities & Personal](https://flowrunner.ai/integrations/category/utilities-personal) Connect over OAuth to read athlete profiles and stats, create and update activities, explore segments, browse clubs, and look up gear and routes through the Strava API v3. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 22 actions · OAuth · available [Strava website](https://strava.com/) · [Platform Documentation](https://developers.strava.com) · Capability data verified 2026-07-14 1. A new completed activity appears for a connected athlete 2. Agent fetches the newest activity with List Activities 3. Agent reads distance, time, and pace from the activity 4. Agent checks gear mileage against the maintenance threshold 5. Agent drafts a training-log entry and a maintenance reminder 6. Agent confirms the entry is complete and correctly attributed 7. Any write back to Strava or shared export waits for approval ## What This Integration Enables The Strava connector lets agents read athletic data and, with the right scopes, write it back. Agents read athlete stats, profiles, zones, and clubs; list, fetch, and inspect activities down to laps, comments, and kudoers; explore, star, and read segments; browse clubs and their feeds; and look up gear and routes. Create Activity and Update Activity write, and require the relevant write scope. Distances come back in meters and times in seconds, per the Strava API. The connector supplies the data and the write actions; the surrounding flow decides what to record, what to share, and what needs a human first. ### Without FlowRunner **Activities re-entered by hand**: Someone copies distance and time from Strava into a log **Totals tracked manually**: Weekly and year-to-date totals get tallied by hand **Gear wear untracked**: Shoes and bikes pass their mileage without anyone noticing ### With FlowRunner **Activities synced automatically**: The agent reads each new activity and drafts a log entry **Totals pulled on demand**: Athlete stats supply weekly, YTD, and all-time totals directly **Gear wear surfaced**: Mileage thresholds become maintenance reminders a person acts on ## Use Case Scenarios ### Training-Log Sync After a workout, the agent calls List Activities to fetch the newest activity, then appends its distance, time, and pace to a training-log spreadsheet. Because the read is routine and non-consequential, most entries flow straight through. The sync keeps a complete log without the athlete re-entering anything. ### Progress Summary The agent calls Get Athlete Stats to pull weekly, year-to-date, and all-time totals plus personal bests, then emails the athlete a progress summary. The stats action returns data only for the authenticated athlete, so the summary reflects the connected account and nothing else. ### Gear Maintenance Reminder The agent monitors gear mileage with Get Gear. When a bike or a pair of shoes crosses a maintenance threshold, it drafts a reminder and posts it to the athlete's channel. The reminder is a nudge, not an automatic change, so the athlete decides when to service or replace the gear. ## Human-in-Loop Highlight Reading a workout is low-stakes. Writing to Strava or sharing private athletic data is not, and the connector's write actions and private scopes make that line worth respecting. When a workflow would create or update an activity, or export private data beyond the athlete, the agent stops. Before a write, it assembles the change and routes to the athlete through their channel: "This treadmill session is not in Strava yet. Create it as a manual activity with 5.2 km and 28 minutes, or leave it out?" The same pause guards any share of private profile or activity data. This is [human-in-the-loop](https://flowrunner.ai/concepts/human-in-the-loop) at the boundary between reading a record and changing or exposing it: the agent handles the gathering, and a person owns every write and every disclosure. Agent processes routinely Detects exception requiring judgment Clear match Continues automatically Ambiguous Routes to human via preferred channel Human decides Agent resumes with decision ## Agent Capabilities 22 actions ### Athlete 5 - **Get Athlete Stats** Retrieve weekly, year-to-date, and all-time totals plus personal bests for the authenticated athlete. - **Get Authenticated Athlete** Fetch the profile of the connected athlete. - **List Athlete Clubs** List the clubs the authenticated athlete belongs to. - **List Athlete Zones** Retrieve the athlete's heart rate and power zones. - **Update Athlete** Update fields on the authenticated athlete profile. Requires the profile write scope. ### Activities 7 - **Create Activity** Create a manual activity, for example a treadmill or non-GPS workout. Requires the activity write scope. - **Get Activity** Fetch a single activity by id. - **Get Activity Comments** Fetch the comments on an activity. - **Get Activity Kudoers** Fetch the athletes who gave kudos to an activity. - **Get Activity Laps** Fetch the laps recorded within an activity. - **List Activities** List the authenticated athlete's activities. - **Update Activity** Update fields on an existing activity. Requires the activity write scope. ### Segments 4 - **Explore Segments** Explore segments within a geographic bounding box. - **Get Segment** Fetch detail for a single segment. - **Get Segment Efforts** Fetch efforts recorded on a segment. Requires an active subscription on the connected account. - **List Starred Segments** List the segments the athlete has starred. ### Clubs 3 - **Get Club** Fetch detail for a single club. - **Get Club Activities** Fetch a club's recent activity feed. - **Get Club Members** List the members of a club. ### Gear 1 - **Get Gear** Look up gear detail and mileage for maintenance planning. ### Routes 2 - **Get Route** Fetch a single route by id. - **List Athlete Routes** List the authenticated athlete's routes. ## Frequently Asked Questions ### What can FlowRunner do with Strava? FlowRunner agents can run Get Athlete Stats, Get Authenticated Athlete, and List Athlete Clubs in Strava, plus 19 more actions. ### Does connecting Strava to FlowRunner require OAuth? Yes. Strava connects to FlowRunner with OAuth 2.0, so agents authenticate without handling raw credentials. ### Can Strava trigger a FlowRunner workflow automatically? Strava doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at Strava?** This integration exposes Strava to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current. --- Markdown version of https://flowrunner.ai/integrations/strava. Site index: https://flowrunner.ai/llms.txt