Disable devices in EMnify when new Google Calendar events end.
When a scheduled Google Calendar event ends, automatically disable the associated device in EMnify.
See all EMnify + Google Calendar 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 Calendar Explore Google Calendar →
TriggersFires when a new event is created in Google Calendar.
Fires when an event's time or details change in Google Calendar.
Fires when an event in Google Calendar is canceled.
Fires shortly before a scheduled event in Google Calendar starts.
Creates a new event in Google Calendar.
Updates an existing event in Google Calendar.
Cancels an event in Google Calendar.
Finds an open time slot on a calendar in Google Calendar.
Common questions
Can Knit build “Disable devices in EMnify when new Google Calendar events end.” between EMnify and Google Calendar?
Yes — describe it in the box above and Knit's Integrations Agent researches EMnify and Google Calendar'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.