When location devices - polling in myDevices, sync it to Slack.
When location device updates are polled in myDevices, push alert notifications to Slack.
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.
Slack Explore Slack →
TriggersFires when a new message is posted to a channel in Slack.
Fires when your team or a keyword is mentioned in Slack.
Fires when a new channel is created in Slack.
Fires when a new file is shared in Slack.
Posts a message to a channel in Slack.
Sends a direct message to a person in Slack.
Creates a new channel in Slack.
Adds a user to a channel in Slack.
Common questions
Can Knit build “When location devices - polling in myDevices, sync it to Slack.” between myDevices and Slack?
Yes — describe it in the box above and Knit's Integrations Agent researches myDevices and Slack'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.