When new booking in LegitFit, sync it to CalGet.
When a new booking is made in LegitFit, sync calendar events to CalGet.
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.
LegitFit Explore LegitFit →
TriggersFires when a new member, client or user joins in LegitFit.
Fires when someone books a class or session in LegitFit.
Fires when a workout, habit, journal entry or goal is logged in LegitFit.
Creates or updates a member's profile in LegitFit.
Books a class or session for a client in LegitFit.
Logs a workout, habit or data point in LegitFit.
CalGet Explore CalGet →
TriggersFires when a new event is created in CalGet.
Fires when an event's time or details change in CalGet.
Fires when an event in CalGet is canceled.
Fires shortly before a scheduled event in CalGet starts.
Creates a new event in CalGet.
Updates an existing event in CalGet.
Cancels an event in CalGet.
Finds an open time slot on a calendar in CalGet.
Common questions
Can Knit build “When new booking in LegitFit, sync it to CalGet.” between LegitFit and CalGet?
Yes — describe it in the box above and Knit's Integrations Agent researches LegitFit and CalGet'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.