When key share on lock in Nexkey, sync it to SimplyBook.me.
When a key is shared on a Nexkey lock, attach physical access details to the client booking in SimplyBook.me.
See all Nexkey + SimplyBook.me 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.
Nexkey Explore Nexkey →
TriggersFires when a lock managed by Nexkey is unlocked.
Fires when Nexkey grants someone access to a space.
Fires when a visitor or guest checks in via Nexkey.
Creates a new access code or key via Nexkey.
Revokes a guest's or employee's access in Nexkey.
Registers a visitor or guest in Nexkey.
SimplyBook.me Explore SimplyBook.me →
TriggersFires when a new booking or appointment is made in SimplyBook.me.
Fires when a booking in SimplyBook.me is changed or canceled.
Fires when a new customer books for the first time in SimplyBook.me.
Creates a new booking or appointment in SimplyBook.me.
Cancels or moves a booking in SimplyBook.me.
Creates or updates a customer record in SimplyBook.me.
Adds a booking from SimplyBook.me to a connected calendar.
Common questions
Can Knit build “When key share on lock in Nexkey, sync it to SimplyBook.me.” between Nexkey and SimplyBook.me?
Yes — describe it in the box above and Knit's Integrations Agent researches Nexkey and SimplyBook.me'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.