Strava2Endurain

Fetches your Strava activities, downloads the original FIT files, patches the workout name into the FIT metadata (so platforms like Endurain show a proper title when performing a virtual ride e.g. MyWhoosh), and triggers a bulk import into an Endurain instance.

How it works

1. login — saves your Strava session cookie (interactive browser via Playwright, or pass --cookie manually).
2. get-activity-ids — fetches recent activity IDs/names from Strava's training page.
3. export-activities — downloads the original FIT files for each activity.
4. set-fit-name — patches each FIT file's workout name field to match the Strava activity name (handy for MyWhoosh virtual rides that export as generic names, so Endurain gets a proper title; can be omitted if not needed).
5. endurain-bulk-import — triggers Endurain's bulk import endpoint so it picks up the patched files.

The run command runs steps 2–5 in one go (also supports --dest to copy files to a directory). The run.sh wrapper is used by cron:

Crontab

Run daily at midnight:

0 0 * * * cd /path/to/strava2endurain && ./run.sh >> strava2endurain.log 2>&1

Setup

python3 -m venv .venv
.venv/bin/pip install -r requirements.txt
.venv/bin/playwright install chromium
cp .env.example .env   # configure your credentials