When new visit in Referrizer, sync it to Gymdesk.
When a new visit triggers in Referrizer, sync member attendance data to Gymdesk.
See all Referrizer + Gymdesk integrations or talk to a human
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.
Referrizer Explore Referrizer →
TriggersFires when a new lead or contact is captured in Referrizer.
Fires when a contact enters an automation in Referrizer.
Fires when a field on a contact changes in Referrizer.
Fires when a contact unsubscribes in Referrizer.
Creates or updates a contact in Referrizer.
Adds a contact to a workflow or campaign in Referrizer.
Sends an email or message to a contact via Referrizer.
Changes a contact's tags in Referrizer.
Gymdesk Explore Gymdesk →
TriggersFires when a new member, client or user joins in Gymdesk.
Fires when someone books a class or session in Gymdesk.
Fires when a workout, habit, journal entry or goal is logged in Gymdesk.
Creates or updates a member's profile in Gymdesk.
Books a class or session for a client in Gymdesk.
Logs a workout, habit or data point in Gymdesk.
Common questions
Can Knit build “When new visit in Referrizer, sync it to Gymdesk.” between Referrizer and Gymdesk?
Yes — describe it in the box above and Knit's Integrations Agent researches Referrizer and Gymdesk'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.