When client profile updated in WellnessLiving, sync it to ProdataKey.
Sync updated client profiles in WellnessLiving to door access credentials in ProdataKey.
See all ProdataKey + WellnessLiving 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.
ProdataKey Explore ProdataKey →
TriggersFires when a lock managed by ProdataKey is unlocked.
Fires when ProdataKey grants someone access to a space.
Fires when a visitor or guest checks in via ProdataKey.
Creates a new access code or key via ProdataKey.
Revokes a guest's or employee's access in ProdataKey.
Registers a visitor or guest in ProdataKey.
WellnessLiving Explore WellnessLiving →
TriggersFires when a new contact or lead is added to WellnessLiving.
Fires when a field on a contact changes in WellnessLiving.
Fires when a deal, case or record moves to a new stage in WellnessLiving.
Fires when a deal is marked won in WellnessLiving.
Creates or updates a contact in WellnessLiving.
Creates a new deal in WellnessLiving.
Moves a deal or record to a new stage in WellnessLiving.
Logs a call, email, or note against a record in WellnessLiving.
Common questions
Can Knit build “When client profile updated in WellnessLiving, sync it to ProdataKey.” between ProdataKey and WellnessLiving?
Yes — describe it in the box above and Knit's Integrations Agent researches ProdataKey and WellnessLiving'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.