When user companies - polling in myDevices, sync it to Dastra.
When user company updates are polled in myDevices, process compliance and data privacy records in Dastra.
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.
Dastra Explore Dastra →
TriggersFires when a new task, job or item is created in Dastra.
Fires when a task in Dastra is marked complete.
Fires when a task's due date in Dastra is coming up.
Fires when a task, job or project changes status in Dastra.
Creates a new task, job or item in Dastra.
Updates a task's status or assignee in Dastra.
Posts a comment on a task in Dastra.
Assigns a task in Dastra to a team member.
Common questions
Can Knit build “When user companies - polling in myDevices, sync it to Dastra.” between myDevices and Dastra?
Yes — describe it in the box above and Knit's Integrations Agent researches myDevices and Dastra'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.