When device is on in Fingbox, sync it to Watershed LRS.
When a device switches on in Fingbox, record a network usage statement in Watershed LRS.
See all Watershed LRS + Fingbox 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.
Watershed LRS Explore Watershed LRS →
TriggersFires when a new report or dashboard is created in Watershed LRS.
Fires when a tracked metric in Watershed LRS crosses a set threshold.
Fires when a scheduled report finishes generating in Watershed LRS.
Creates or refreshes a dashboard in Watershed LRS.
Exports a report from Watershed LRS.
Sends an alert when a metric changes in Watershed LRS.
Fingbox Explore Fingbox →
TriggersFires when a device connected to Fingbox comes online.
Fires when a device connected to Fingbox goes offline.
Fires when a reading from a device in Fingbox crosses a set threshold.
Sends a control command to a device via Fingbox.
Adds a new device to Fingbox.
Records a sensor reading or event from Fingbox.
Common questions
Can Knit build “When device is on in Fingbox, sync it to Watershed LRS.” between Watershed LRS and Fingbox?
Yes — describe it in the box above and Knit's Integrations Agent researches Watershed LRS and Fingbox'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.