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