Strava
On this page
Purpose
Strava connects a user's Strava account through Composio. After authentication, it loads provider actions for the connected account.
Tool Mode exposes each selected action as a separate Agent tool. Normal mode runs one selected action and returns a DataFrame.
When to use it
- List recent activities and summarize training volume or trends.
- Retrieve an athlete profile, activity, or aggregate statistics.
- Add Strava and Google Sheets tools to the same coaching Agent.
- Run one fixed Strava read in a non-Agent flow.
Required setup
- Create a separate Composio project API key in Settings > Project Settings > API Keys. Configure it through the Strava component or a saved Arkus Credential. Never put a key in a prompt or example.
- Authorize the Strava account separately. The auth config controls the OAuth scheme and scopes. Strava OAuth application approval and the application's athlete capacity can limit how many athlete accounts can connect. See the authentication overview for the connection flow.
- Confirm that the intended connected account is active. Arkus loads provider actions for that account, and selected actions become separate Agent tools.
If actions are missing, verify the project key, connected account, and approved scopes first. Reconnect the account after changing the auth config or scopes. The linked Strava toolkit catalog shows the broader current provider catalog.
Activity routes, locations, health-adjacent metrics, and profile data can be sensitive. Do not present fitness summaries as clinical advice.
How to use it
In Tool Mode:
- Add Strava, select the Composio Credential, and authorize the athlete account.
- Turn on Tool Mode and choose the actions to expose.
- Connect the Toolset output to Agent Core.
- Start with read actions such as authenticated athlete, athlete stats, list athlete activities, and get activity.
- Add write-capable actions only for a stated workflow with narrow instructions.
When no actions are selected or saved, Arkus initially enables the first five provider actions it fetches.
For a fixed Normal-mode flow, leave Tool Mode off, select one Action, fill its generated fields, and use the DataFrame output.
Configuration
| Setting | What it controls | Recommended starting point |
|---|---|---|
| Composio API Key | Access to Composio and its action schemas | Select a saved Credential |
| Connection | The authorized Strava account | Connect one intended athlete account |
| Action | The direct-mode Strava action | Start with an athlete or activity read |
| Tool Mode | Replaces direct output with Agent tools | Use for a coaching Agent |
| Actions | The Agent-visible action set | Select only the actions the Agent needs |
Expected result
Normal mode returns a DataFrame. Tool Mode provides one Agent tool for each selected Strava action.
The component is not inherently read-only. Create, update, upload, star, and other write-capable actions can change the connected account when enabled. Missing or ambiguous active accounts require reconnection before execution. Runtime failures during an action remain generic.
Reference details
Entity ID is an advanced editor identity value and is ignored in deployment. Action parameters are generated from the live schema. Use IDs and page bounds returned by earlier actions rather than guessing them.
The Composio Strava toolkit catalog shows the broader current catalog. Actions available in Arkus can vary by connected account and Arkus's pinned toolkit version.
An Agent can combine Strava with Google Sheets to persist selected training metrics. DataFrame Operations can filter a fixed Normal-mode read.