When new customer in HotspotSystem, sync it to Clickatell.
When a new customer registers in HotspotSystem, send an SMS alert via Clickatell.
See all Clickatell + HotspotSystem 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.
Clickatell Explore Clickatell →
TriggersFires when a new text message is received in Clickatell.
Fires when a new call comes in or out through Clickatell.
Fires when a call is missed in Clickatell.
Fires when a call recording finishes processing in Clickatell.
Sends a text message through Clickatell.
Starts an outbound call via Clickatell.
Creates or updates a contact in Clickatell.
Sends a recorded voice message via Clickatell.
HotspotSystem Explore HotspotSystem →
TriggersFires when a device connected to HotspotSystem comes online.
Fires when a device connected to HotspotSystem goes offline.
Fires when a reading from a device in HotspotSystem crosses a set threshold.
Sends a control command to a device via HotspotSystem.
Adds a new device to HotspotSystem.
Records a sensor reading or event from HotspotSystem.
Common questions
Can Knit build “When new customer in HotspotSystem, sync it to Clickatell.” between Clickatell and HotspotSystem?
Yes — describe it in the box above and Knit's Integrations Agent researches Clickatell and HotspotSystem'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.