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