Strava integration

What it does

The Strava integration lets your agency read and write athlete data on behalf of your clients without leaving TaskJuice. Connect a client's Strava account once and you can pull the athlete profile, list and update activities, log manual entries, browse segments and clubs, and start a workflow whenever a new activity lands on the connected athlete's feed.

Connect a Strava account

1. Open your workspace in TaskJuice and navigate to Connections.
2. Choose Strava and click Connect.
3. Sign in with the Strava account whose data you want to manage on behalf of your client.
4. Grant the requested scopes (read profile, read activities, write activities).
5. TaskJuice returns you to the workspace with the connection ready to use in any workflow.

To revoke access at any time, visit Strava connected apps and remove the TaskJuice entry.

Triggers

• strava/new-activity polls the authenticated athlete's activity feed and fires once per cycle whose items array carries every activity recorded since the previous watermark. Drop a Loop node downstream to process each activity individually.

Actions

• strava/get-athlete returns the connected athlete's full profile, including measurement preference, FTP, and follower count.
• strava/update-athlete updates the connected athlete's weight (the only writable profile field exposed by the Strava API).
• strava/get-athlete-stats returns recent, year-to-date, and all-time totals for the connected athlete.
• strava/get-athlete-zones returns the connected athlete's configured heart-rate and power zones.
• strava/list-activities returns the connected athlete's activities with optional before, after, page, and per-page filters.
• strava/get-activity returns a single activity owned by the connected athlete, optionally including segment efforts.
• strava/create-activity logs a manual activity (run, ride, swim, or any sport type Strava recognizes).
• strava/update-activity updates the name, type, gear, description, or visibility of an existing activity.
• strava/get-activity-zones returns the heart-rate and power zone distribution for a single activity.
• strava/get-activity-laps returns the lap breakdown for a single activity.
• strava/get-activity-streams returns time, distance, heart-rate, and other measurement streams for a single activity.
• strava/list-activity-comments returns the comments left on a single activity.
• strava/list-activity-kudoers returns the athletes who have given kudos on a single activity.
• strava/get-segment returns the metadata for a Strava segment.
• strava/get-segment-effort returns a single segment effort by ID.
• strava/get-segment-effort-streams returns the measurement streams for a single segment effort.
• strava/get-segment-streams returns the measurement streams for a single segment.
• strava/list-segment-efforts lists the connected athlete's efforts on a segment, with optional time bounds.
• strava/list-starred-segments returns the segments the connected athlete has starred.
• strava/star-segment stars or unstars a segment for the connected athlete.
• strava/explore-segments returns popular segments inside a bounding box, optionally filtered by activity type or climb category.
• strava/get-club returns metadata for a Strava club.
• strava/list-athlete-clubs returns the clubs the connected athlete belongs to.
• strava/list-club-activities returns recent activities posted by members of a club.
• strava/list-club-admins returns the administrators of a club.
• strava/list-club-members returns the members of a club.
• strava/get-route returns the metadata for a saved route.
• strava/get-route-streams returns the measurement streams for a saved route.
• strava/list-athlete-routes returns the saved routes for an athlete.
• strava/get-gear returns a single gear record (bike or shoes) attached to the connected athlete.
• strava/get-upload-status returns the processing status of an activity upload by upload ID.

Known limitations

• Strava enforces a 200-read and 100-write rate-limit window every 15 minutes, with daily caps of 2000 reads and 1000 writes per access token. When a 429 is returned, TaskJuice surfaces it as a retryable rate-limit error and respects Strava's recommended backoff.
• Strava's Push Subscriptions API issues one subscription per registered application, not per athlete, and only Strava-approved applications can create subscriptions in production. TaskJuice uses a polling trigger over the athlete activities endpoint so every connected client receives near-real-time activity events without depending on a single shared subscription.
• The update-athlete action only accepts the weight field. Other profile attributes (name, city, sex) are read-only through the API and must be edited inside Strava.
• Manual activities created via create-activity cannot include GPS streams. Use the Strava Uploads endpoint outside TaskJuice when you need to ingest GPX or FIT files.