When canceled class booking in GymMaster, sync it to Referrizer.
When a class booking is canceled in GymMaster, update customer engagement metrics in Referrizer.
See all Referrizer + GymMaster 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.
GymMaster Explore GymMaster →
TriggersFires when a new member, client or user joins in GymMaster.
Fires when someone books a class or session in GymMaster.
Fires when a workout, habit, journal entry or goal is logged in GymMaster.
Creates or updates a member's profile in GymMaster.
Books a class or session for a client in GymMaster.
Logs a workout, habit or data point in GymMaster.
Common questions
Can Knit build “When canceled class booking in GymMaster, sync it to Referrizer.” between Referrizer and GymMaster?
Yes — describe it in the box above and Knit's Integrations Agent researches Referrizer and GymMaster'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.