When company locations - polling in myDevices, sync it to Robofy.
When company locations are polled in myDevices, feed location data into Robofy chatbot knowledge bases.
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.
Robofy Explore Robofy →
TriggersFires when a new chat or conversation begins in Robofy.
Fires when Robofy captures a lead during a conversation.
Fires when Robofy escalates a conversation to a human.
Sends a message to a user through Robofy.
Asks Robofy a question against its knowledge base and returns the answer.
Uses Robofy to summarize a chat transcript.
Opens a support ticket from an Robofy conversation.
Common questions
Can Knit build “When company locations - polling in myDevices, sync it to Robofy.” between myDevices and Robofy?
Yes — describe it in the box above and Knit's Integrations Agent researches myDevices and Robofy'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.