When device telemetry data - polling in myDevices, sync it to Google Sheets.
When device telemetry data is polled in myDevices, append a row containing sensor metrics into Google Sheets.
See all myDevices + Google Sheets 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.
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.
Google Sheets Explore Google Sheets →
TriggersFires when a row is added to a sheet in Google Sheets.
Fires when a row or column changes in Google Sheets.
Fires when a new spreadsheet or worksheet is created in Google Sheets.
Adds a new row to a sheet in Google Sheets.
Updates the values in an existing row in Google Sheets.
Finds a row by a column value in Google Sheets.
Common questions
Can Knit build “When device telemetry data - polling in myDevices, sync it to Google Sheets.” between myDevices and Google Sheets?
Yes — describe it in the box above and Knit's Integrations Agent researches myDevices and Google Sheets'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.