When key share on lock in Nexkey, sync it to Kit.
When a key share occurs on a Nexkey lock, sync the user's information with subscriber records in Kit.
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.
Kit Explore Kit →
TriggersFires when a new subscriber is added in Kit.
Fires when a contact unsubscribes in Kit.
Fires when a subscriber opens or clicks a campaign in Kit.
Creates or updates a subscriber in Kit.
Unsubscribes a contact in Kit.
Adds a subscriber to a list or segment in Kit.
Sends a one-off transactional email via Kit.
Common questions
Can Knit build “When key share on lock in Nexkey, sync it to Kit.” between Nexkey and Kit?
Yes — describe it in the box above and Knit's Integrations Agent researches Nexkey and Kit'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.