When location devices - polling in myDevices, sync it to Pingdom.
When location device polling occurs in myDevices, cross-reference device status with Pingdom uptime checks.
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.
myDevices Explore myDevices →
TriggersFires when a device connected to myDevices comes online.
Fires when a device connected to myDevices goes offline.
Fires when a reading from a device in myDevices crosses a set threshold.
Sends a control command to a device via myDevices.
Adds a new device to myDevices.
Records a sensor reading or event from myDevices.
Pingdom Explore Pingdom →
TriggersFires when a monitor or check in Pingdom raises an alert.
Fires when an incident is opened or updated in Pingdom.
Fires when a monitored site, service or alarm in Pingdom changes state.
Opens a new incident or alert in Pingdom.
Acknowledges an open incident in Pingdom.
Resolves an incident in Pingdom.
Common questions
Can Knit build “When location devices - polling in myDevices, sync it to Pingdom.” between myDevices and Pingdom?
Yes — describe it in the box above and Knit's Integrations Agent researches myDevices and Pingdom'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.