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