When all emnify events in EMnify, sync it to SMSFactor.
When an event occurs in EMnify, send an alert text via SMSFactor.
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.
SMSFactor Explore SMSFactor →
TriggersFires when a new text message is received in SMSFactor.
Fires when a new call comes in or out through SMSFactor.
Fires when a call is missed in SMSFactor.
Fires when a call recording finishes processing in SMSFactor.
Sends a text message through SMSFactor.
Starts an outbound call via SMSFactor.
Creates or updates a contact in SMSFactor.
Sends a recorded voice message via SMSFactor.
Common questions
Can Knit build “When all emnify events in EMnify, sync it to SMSFactor.” between EMnify and SMSFactor?
Yes — describe it in the box above and Knit's Integrations Agent researches EMnify and SMSFactor'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.