When new customer in HotspotSystem, sync it to Lexware Office.
When a new customer connects in HotspotSystem, add them as a contact in Lexware Office.
See all HotspotSystem + Lexware Office 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.
Lexware Office Explore Lexware Office →
TriggersFires when a new invoice is created in Lexware Office.
Fires when a payment is recorded in Lexware Office.
Fires when an invoice in Lexware Office passes its due date unpaid.
Fires when a new expense is recorded in Lexware Office.
Creates a new invoice in Lexware Office.
Records a payment against an invoice in Lexware Office.
Creates a new expense entry in Lexware Office.
Syncs a customer's billing record in Lexware Office.
Common questions
Can Knit build “When new customer in HotspotSystem, sync it to Lexware Office.” between HotspotSystem and Lexware Office?
Yes — describe it in the box above and Knit's Integrations Agent researches HotspotSystem and Lexware Office'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.