Setup guide

Get integrations ready

Start with one useful connection, confirm what it can read or write, then bring it into the planner only when it is ready.

3 steps
  1. 1Choose the jobPick the place where external data should help: workout publishing, calendar context, or archive import.
  2. 2Connect deliberatelyGrant only the provider access you need. FAAAST keeps helper flows visible even before every provider is fully live.
  3. 3Use it from planningSend workouts, copy feeds, or review imported history from the planner once the connection is ready.

Workout device sync

Garmin

Available

Connect Garmin to publish structured workouts and inspect sync readiness.

  • Connection state is user-scoped and can be turned on or off from this view.
  • Workout publishing stays previewable; production writes remain fenced at the provider boundary.
  • Missing permissions are shown as a reconnect path instead of hiding the integration.

Garmin

Send planned workouts to Garmin Connect.

Workout device sync

Suunto

Coming later

Prepare Suunto as a structured workout and completed-activity sync target.

  • The shared workout export contract now recognizes Suunto as its own provider.
  • Connection controls should stay disabled until OAuth, permission checks, and provider writes are wired.
  • Treat this as a Garmin-adjacent adapter path: structured workout push first, completed-activity import second.

Suunto controls are not enabled in this build.

The option stays visible here so the integrations view can show the full provider surface while feature policy decides which controls are live.

Bike computer sync

Wahoo

Coming later

Prepare Wahoo as a bike-first structured workout and completed-activity sync target.

  • The shared workout export contract now recognizes Wahoo as its own provider.
  • Bike workouts are the first supported shape in the provider-readiness model.
  • Connection controls should stay disabled until OAuth, scopes, and Wahoo workout payloads are confirmed.

Wahoo controls are not enabled in this build.

The option stays visible here so the integrations view can show the full provider surface while feature policy decides which controls are live.

Calendar context

Google Calendar

Coming later

Use calendar context for week planning and publish workout blocks when enabled.

  • The card remains visible even while the feature policy keeps live connection controls hidden.
  • When enabled, the selected calendar owns both publish target and context refresh.
  • Sync logs and suggestions belong inside the provider subview, not the main planner chrome.

Google Calendar controls are not enabled in this build.

The option stays visible here so the integrations view can show the full provider surface while feature policy decides which controls are live.

Readonly subscription

Calendar share

Available

Create a readonly feed for planned workouts without granting provider access.

  • The feed is opt-in and can be disabled without deleting the underlying planner data.
  • Copying the subscription URL is only offered after a ready, active feed exists.
  • This is an outbound subscription, so it does not import external calendar context.

Calendar share

Checking calendar sharing...

Import helper

TrainingPeaks

Helper

Open the current TrainingPeaks archive/import helper.

  • This remains a helper workflow rather than a normal always-on connection card.
  • Admin-only production import controls stay inside the helper route.
  • Promote it to a standard provider subview only once connection state and sync behavior are productized.

TrainingPeaks import helper

Open the existing helper to plan archive imports, run local-safe imports, and use admin-only production controls when available.

Open helper