When user companies - polling in myDevices, sync it to Homebot.
When user company data is polled in myDevices, update client property device metrics in Homebot.
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.
myDevices Explore myDevices →
TriggersFires when a device connected to myDevices comes online.
Fires when a device connected to myDevices goes offline.
Fires when a reading from a device in myDevices crosses a set threshold.
Sends a control command to a device via myDevices.
Adds a new device to myDevices.
Records a sensor reading or event from myDevices.
Homebot Explore Homebot →
TriggersFires when Homebot captures a new lead or sign-up.
Fires when someone views, clicks or completes something in Homebot.
Fires when a post, page or asset is published from Homebot.
Creates or updates a contact or lead in Homebot.
Adds a contact to a campaign, audience or segment in Homebot.
Common questions
Can Knit build “When user companies - polling in myDevices, sync it to Homebot.” between myDevices and Homebot?
Yes — describe it in the box above and Knit's Integrations Agent researches myDevices and Homebot'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.