When new message in Octorate, sync it to Livvi.
When a new message arrives in Octorate, pass the message text to Livvi.
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.
Octorate Explore Octorate →
TriggersFires when a lease is created, starts or ends in Octorate.
Fires when a new property listing is added in Octorate.
Fires when a reservation, offer or transaction is created in Octorate.
Fires when an inspection is scheduled, closed or cancelled in Octorate.
Adds a client, tenant or prospect in Octorate.
Creates or updates a property listing in Octorate.
Creates a maintenance task or work order in Octorate.
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.
Common questions
Can Knit build “When new message in Octorate, sync it to Livvi.” between Octorate and Livvi?
Yes — describe it in the box above and Knit's Integrations Agent researches Octorate and Livvi'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.