Automated pipeline that syncs workout data from intervals.icu to Garmin Connect by leveraging Fit-File-Faker to transform FIT files from non-Garmin devices into Garmin-compatible format.

The Problem: Many athletes use non-Garmin devices (Coros, Hammerhead, Wahoo, etc.) but want to access Garmin's ecosystem:

• Training Status and Training Readiness
• Body Battery and HRV Status
• Performance metrics (VO2 max, Training Load, etc.)
• Garmin Coach training plans
• Complete activity history in one place

The Solution: This pipeline automatically:

1. Downloads your workout FIT files from intervals.icu
2. Processes them with Fit-File-Faker to appear as Garmin-created files
3. Uploads them to Garmin Connect
4. Runs on a schedule to keep everything in sync

intervals.icu → Download → Fit-File-Faker → Garmin Connect
                  ↓           (Transform)         ↓
              downloaded/                    All Garmin
                  ↓                          Metrics Available
              processed/ ✓
                  ↓
              errors/ ✗

Key Component: Fit-File-Faker does the heavy lifting by modifying FIT file device information so Garmin Connect accepts files from non-Garmin devices. This pipeline automates the entire workflow.

• 📥 Automated Downloads - Pulls original FIT files from intervals.icu API
• 🔧 Device Transformation - Uses Fit-File-Faker to make files Garmin-compatible
• 📤 Automatic Upload - Sends processed files to Garmin Connect
• 🔄 Scheduled Sync - Runs on a schedule to keep data current
• 📝 Detailed Logging - Tracks all operations with timestamps
• ❌ Error Handling - Quarantines problematic files for manual review
• 🔒 Secure - API keys stored locally, never committed to git

Perfect for athletes who:

• Use Coros, Hammerhead, Wahoo, or other non-Garmin devices
• Sync activities to intervals.icu for analysis
• Want to access Garmin's training metrics and ecosystem
• Need complete activity history in Garmin Connect
• Want automated synchronization without manual uploads

Example Workflow:

1. Complete workout with Coros watch
2. Activity auto-syncs to intervals.icu
3. This pipeline downloads and processes it (runs every hour)
4. Activity appears in Garmin Connect with all metrics
5. Garmin's Training Status, Body Battery, etc. stay up-to-date

• Windows 11 (or Windows 10)
• PowerShell 5.1 or later
• Fit-File-Faker - Install via pipx: pipx install fit-file-faker
  • See Fit-File-Faker Setup Guide for detailed configuration
• intervals.icu account with API key (get here)
• Garmin Connect account configured in Fit-File-Faker

See SETUP.md for detailed installation instructions.

# 1. Clone the repository
git clone https://github.com/yourusername/fit-file-sync-pipeline.git
cd fit-file-sync-pipeline

# 2. Create your configuration
Copy-Item scripts\config.template.ps1 scripts\config.ps1

# 3. Edit config.ps1 with your settings
notepad scripts\config.ps1

# 4. Run initial test sync
.\scripts\monitor-and-sync.ps1 -RunOnce -DryRun

# 5. Run actual sync
.\scripts\monitor-and-sync.ps1 -RunOnce

# Download files for a specific date range
.\scripts\download-from-intervals.ps1 -OldestDate "2025-11-01" -NewestDate "2025-11-30"

# Process and upload downloaded files
.\scripts\process-and-upload.ps1

# Run complete sync cycle once
.\scripts\monitor-and-sync.ps1 -RunOnce

# Test mode (downloads and processes but doesn't upload)
.\scripts\monitor-and-sync.ps1 -RunOnce -DryRun

# Run continuous monitoring (checks every hour by default)
.\scripts\monitor-and-sync.ps1

Recommended: Set up Windows Task Scheduler to run automatically (see SETUP.md).

Edit scripts\config.ps1 to customize:

$Config = @{
    IntervalsApiKey = "your_api_key"      # From intervals.icu/settings
    SyncIntervalMinutes = 60               # How often to check for new files
    LookbackDays = 7                       # How far back to check each sync
    DryRun = $false                        # Set true for testing
}

fit-file-sync-pipeline/
├── scripts/
│   ├── download-from-intervals.ps1    # Downloads from intervals.icu
│   ├── process-and-upload.ps1         # Processes with Fit-File-Faker
│   ├── monitor-and-sync.ps1           # Main automation script
│   └── config.ps1                     # Your configuration (not in git)
├── data/
│   ├── downloaded/                    # Raw FIT files from intervals.icu
│   ├── processed/                     # Successfully uploaded files
│   └── errors/                        # Files that failed processing
├── logs/
│   └── sync-YYYY-MM-DD.log           # Daily activity logs
└── docs/
    ├── SETUP.md                       # Installation guide
    └── TROUBLESHOOTING.md            # Common issues

• README - Project overview and quick start
• SETUP - Complete installation guide
• TROUBLESHOOTING - Common issues and solutions
• Fit-File-Faker Setup - Tool-specific configuration

• PROJECT HISTORY - Complete development history and context
• ARCHITECTURE - Technical architecture and design decisions
• DEVELOPMENT NOTES - Quick reference for development
• CONTRIBUTING - How to contribute
• ROADMAP - Future development plans

Fit-File-Faker modifies FIT files to change device identification fields, making them appear as if they came from a Garmin device. This allows:

• Non-Garmin activities to be uploaded to Garmin Connect
• Full metric calculation (VO2 max, Training Status, etc.)
• Historical data import from other platforms
• Device consolidation in one training ecosystem

Important: Fit-File-Faker must be configured with your Garmin Connect credentials before this pipeline will work. See their documentation for setup.

Any device that produces FIT files and syncs to intervals.icu:

• ✅ Coros (Pace, Apex, Vertix, etc.)
• ✅ Hammerhead (Karoo)
• ✅ Wahoo (ELEMNT, RIVAL)
• ✅ Polar (Vantage, Grit, Pacer)
• ✅ Suunto
• ✅ Any other FIT-compatible device

See TROUBLESHOOTING.md for solutions to common issues:

• Authentication errors
• Malformed FIT files
• Upload failures
• Scheduling problems

• Windows only - Currently PowerShell-based (Linux/Mac version planned)
• intervals.icu required - Must have activities in intervals.icu
• Garmin Connect account - Required for uploads
• Original FIT files - Only activities with original files can be processed
• ⚠️ Duplicate activities on connected services - Services connected to both your device AND Garmin Connect may receive duplicate activities. Services like Strava and Ride with GPS seem to handle this automatically, but others like TrainingPeaks require you to disable Garmin auto-sync. This is a known limitation requiring workarounds. See Troubleshooting Guide for details.

Contributions welcome! Please:

1. Fork the repository
2. Create a feature branch
3. Submit a pull request

See CONTRIBUTING.md for guidelines.

• Linux/Mac support (bash scripts)
• Direct integration with other platforms (Strava, TrainingPeaks)
• Retry logic for failed uploads
• Web dashboard for monitoring
• Docker container option

• Fit-File-Faker - The core tool that makes this possible
• intervals.icu - Excellent training analysis platform
• GarminDB - Alternative for Garmin data analysis

MIT License - see LICENSE

• Fit-File-Faker by @jat255 - The essential tool that enables device-agnostic uploads to Garmin Connect
• intervals.icu by @david - Excellent API and training platform
• The endurance sports open-source community

This tool is for personal use. Ensure you comply with the terms of service for intervals.icu and Garmin Connect. This project is not affiliated with Garmin, intervals.icu, or Fit-File-Faker.

Questions? Open an issue or check TROUBLESHOOTING.md