When folder created in EARLY, sync it to Luxafor.
When a new folder is created in EARLY, sync the creation event to trigger status changes on Luxafor devices.
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.
Luxafor Explore Luxafor →
TriggersFires when a device connected to Luxafor comes online.
Fires when a device connected to Luxafor goes offline.
Fires when a reading from a device in Luxafor crosses a set threshold.
Sends a control command to a device via Luxafor.
Adds a new device to Luxafor.
Records a sensor reading or event from Luxafor.
EARLY Explore EARLY →
TriggersFires when a new client is added in EARLY.
Fires when a new project is created in EARLY.
Fires when a new time entry is logged in EARLY.
Fires when a timer is started in EARLY.
Creates a new client in EARLY.
Creates a new project in EARLY.
Logs a new time entry in EARLY.
Starts a timer in EARLY.
Common questions
Can Knit build “When folder created in EARLY, sync it to Luxafor.” between Luxafor and EARLY?
Yes — describe it in the box above and Knit's Integrations Agent researches Luxafor and EARLY'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.