When device enabled in EMnify, sync it to Google Forms (Legacy).
When a device is enabled in EMnify, record registration records in Google Forms (Legacy).
See all EMnify + Google Forms (Legacy) 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.
EMnify Explore EMnify →
TriggersFires when a device connected to EMnify comes online.
Fires when a device connected to EMnify goes offline.
Fires when a reading from a device in EMnify crosses a set threshold.
Sends a control command to a device via EMnify.
Adds a new device to EMnify.
Records a sensor reading or event from EMnify.
Google Forms (Legacy) Explore Google Forms (Legacy) →
TriggersFires when a form is submitted in Google Forms (Legacy).
Fires when a respondent finishes a survey in Google Forms (Legacy).
Fires when an existing response is edited in Google Forms (Legacy).
Creates or updates a form or survey in Google Forms (Legacy).
Looks up a specific form response in Google Forms (Legacy).
Adds a respondent or contact to a form in Google Forms (Legacy).
Common questions
Can Knit build “When device enabled in EMnify, sync it to Google Forms (Legacy).” between EMnify and Google Forms (Legacy)?
Yes — describe it in the box above and Knit's Integrations Agent researches EMnify and Google Forms (Legacy)'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.