Reconfigure EMnify devices from new updated Salesforce records.
When a Salesforce record is updated, reconfigure the corresponding device in EMnify.
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.
Salesforce Explore Salesforce →
TriggersFires when a new contact or lead is added to Salesforce.
Fires when a field on a contact changes in Salesforce.
Fires when a deal, case or record moves to a new stage in Salesforce.
Fires when a deal is marked won in Salesforce.
Creates or updates a contact in Salesforce.
Creates a new deal in Salesforce.
Moves a deal or record to a new stage in Salesforce.
Logs a call, email, or note against a record in Salesforce.
Common questions
Can Knit build “Reconfigure EMnify devices from new updated Salesforce records.” between EMnify and Salesforce?
Yes — describe it in the box above and Knit's Integrations Agent researches EMnify and Salesforce'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.