When new contact in Member365, sync it to Everfit.
When a new contact is created in Member365, register them as a client in Everfit.
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.
Member365 Explore Member365 →
TriggersFires when a new contact or lead is added to Member365.
Fires when a field on a contact changes in Member365.
Fires when a deal, case or record moves to a new stage in Member365.
Fires when a deal is marked won in Member365.
Creates or updates a contact in Member365.
Creates a new deal in Member365.
Moves a deal or record to a new stage in Member365.
Logs a call, email, or note against a record in Member365.
Everfit Explore Everfit →
TriggersFires when a new member, client or user joins in Everfit.
Fires when someone books a class or session in Everfit.
Fires when a workout, habit, journal entry or goal is logged in Everfit.
Creates or updates a member's profile in Everfit.
Books a class or session for a client in Everfit.
Logs a workout, habit or data point in Everfit.
Common questions
Can Knit build “When new contact in Member365, sync it to Everfit.” between Member365 and Everfit?
Yes — describe it in the box above and Knit's Integrations Agent researches Member365 and Everfit'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.