When new subscriber in HotspotSystem, sync it to SendPulse.
When a new subscriber signs up in HotspotSystem, add them to a subscriber list in SendPulse.
See all SendPulse + 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.
SendPulse Explore SendPulse →
TriggersFires when a new subscriber is added in SendPulse.
Fires when a contact unsubscribes in SendPulse.
Fires when a subscriber opens or clicks a campaign in SendPulse.
Creates or updates a subscriber in SendPulse.
Unsubscribes a contact in SendPulse.
Adds a subscriber to a list or segment in SendPulse.
Sends a one-off transactional email via SendPulse.
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 subscriber in HotspotSystem, sync it to SendPulse.” between SendPulse and HotspotSystem?
Yes — describe it in the box above and Knit's Integrations Agent researches SendPulse 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.