When new user in Kisi, sync it to Walla.
When a new user is created in Kisi, sync membership profiles to Walla.
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.
Walla Explore Walla →
TriggersFires when a new booking or appointment is made in Walla.
Fires when a booking in Walla is changed or canceled.
Fires when a new customer books for the first time in Walla.
Creates a new booking or appointment in Walla.
Cancels or moves a booking in Walla.
Creates or updates a customer record in Walla.
Adds a booking from Walla to a connected calendar.
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 Walla.” between Walla and Kisi?
Yes — describe it in the box above and Knit's Integrations Agent researches Walla 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.