When a reservation is modified in Livvi, sync the booking data to Guesty.
When a reservation is modified in Livvi, sync the booking data to Guesty.
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.
Livvi Explore Livvi →
TriggersFires when a device connected to Livvi comes online.
Fires when a device connected to Livvi goes offline.
Fires when a reading from a device in Livvi crosses a set threshold.
Sends a control command to a device via Livvi.
Adds a new device to Livvi.
Records a sensor reading or event from Livvi.
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.
Common questions
Can Knit build “When a reservation is modified in Livvi, sync the booking data to Guesty.” between Livvi and Guesty?
Yes — describe it in the box above and Knit's Integrations Agent researches Livvi and Guesty'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.