When new customer in HotspotSystem, sync it to Cloudbeds.
When a new customer connects in HotspotSystem, sync their guest profile to Cloudbeds.
See all HotspotSystem + Cloudbeds integrations or talk to a human
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.
HotspotSystem Explore HotspotSystem →
TriggersFires when a device connected to HotspotSystem comes online.
Fires when a device connected to HotspotSystem goes offline.
Fires when a reading from a device in HotspotSystem crosses a set threshold.
Sends a control command to a device via HotspotSystem.
Adds a new device to HotspotSystem.
Records a sensor reading or event from HotspotSystem.
Cloudbeds Explore Cloudbeds →
TriggersFires when a new booking or appointment is made in Cloudbeds.
Fires when a booking in Cloudbeds is changed or canceled.
Fires when a new customer books for the first time in Cloudbeds.
Creates a new booking or appointment in Cloudbeds.
Cancels or moves a booking in Cloudbeds.
Creates or updates a customer record in Cloudbeds.
Adds a booking from Cloudbeds to a connected calendar.
Common questions
Can Knit build “When new customer in HotspotSystem, sync it to Cloudbeds.” between HotspotSystem and Cloudbeds?
Yes — describe it in the box above and Knit's Integrations Agent researches HotspotSystem and Cloudbeds'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.