When client's birthday in FITR, sync it to Exercise.com.
When a client's birthday is noted in FITR, sync their profile data and birth date over to Exercise.com.
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.
Exercise.com Explore Exercise.com →
TriggersFires when a new member, client or user joins in Exercise.com.
Fires when someone books a class or session in Exercise.com.
Fires when a workout, habit, journal entry or goal is logged in Exercise.com.
Creates or updates a member's profile in Exercise.com.
Books a class or session for a client in Exercise.com.
Logs a workout, habit or data point in Exercise.com.
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's birthday in FITR, sync it to Exercise.com.” between Exercise.com and FITR?
Yes — describe it in the box above and Knit's Integrations Agent researches Exercise.com 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.