When client cancels whilst in a trial in FITR, sync it to Strava.
When a client cancels during a trial in FITR, update activity sync settings with Strava.
4.9/5 on G2·
Google for Startups Accelerator
How Knit builds this workflow
The Agent researches both APIs and wires the trigger on one side to the action on the other — no pre-built connector required. Here is the vocabulary it has to work with.
Strava Explore Strava →
TriggersFires when a new member, client or user joins in Strava.
Fires when someone books a class or session in Strava.
Fires when a workout, habit, journal entry or goal is logged in Strava.
Creates or updates a member's profile in Strava.
Books a class or session for a client in Strava.
Logs a workout, habit or data point in Strava.
FITR Explore FITR →
TriggersFires when a new member, client or user joins in FITR.
Fires when someone books a class or session in FITR.
Fires when a workout, habit, journal entry or goal is logged in FITR.
Creates or updates a member's profile in FITR.
Books a class or session for a client in FITR.
Logs a workout, habit or data point in FITR.
Common questions
Can Knit build “When client cancels whilst in a trial in FITR, sync it to Strava.” between Strava and FITR?
Yes — describe it in the box above and Knit's Integrations Agent researches Strava and FITR's public API docs (or your own uploaded docs) and builds a working workflow, whether or not either app already has a pre-built connector.
How long does it take to build?
Minutes to a first working version, not weeks — you test it against real data before it goes anywhere near production.