Third-party integration strategy and specific requests
Raw Developer Origin & Technical Request
GitHub Issue
Mar 30, 2026
## Integration Requests
This is the central place to collect and discuss integration requests for TREK.
We get a lot of requests for connecting TREK with external services. Since we can't integrate everything, this issue serves as a **voting thread** — upvote (👍) the integrations you'd like to see, and the most requested ones may be considered for future releases.
### How to request an integration
1. **Check the comments below** to see if your integration has already been requested
2. If yes → **upvote it** with a 👍 reaction
3. If no → **add a comment** with:
- Service name (e.g. "Komoot", "Google Calendar")
- What it should do (e.g. "Import routes", "Sync trip dates")
- Why it's useful for trip planning
### Currently integrated
- **Immich** — Self-hosted photo sharing (Photos addon)
- **Google Places API** — Place search, details, photos
- **OpenStreetMap / Nominatim** — Free place search fallback
- **Nager.Date** — Public holiday data (Vacay)
- **GPX import** — Import waypoints from any GPX-compatible app
---
*Not every integration can or will be built. TREK is a self-hosted tool and prioritizes integrations that align with the self-hosted philosophy (Immich, OSM, GPX). Cloud-only services with complex OAuth flows are lower priority.*
Developer Debate & Comments
Adjacent Repository Pain Points
Other highly discussed features and pain points extracted from mauriceboe/TREK.
Engagement Signals
Cross-Market Term Frequency
Quantifies the cross-market adoption of foundational terms like API and Integration Requests by tracking occurrence frequency across active SaaS architectures and enterprise developer debates.
Market Trends