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