Record new Flic presses with presence in the MOCO app.
Whenever a Flic button is pressed, record presence or clocking activity into the MOCO app.
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.
Flic Explore Flic →
TriggersFires when a device connected to Flic comes online.
Fires when a device connected to Flic goes offline.
Fires when a reading from a device in Flic crosses a set threshold.
Sends a control command to a device via Flic.
Adds a new device to Flic.
Records a sensor reading or event from Flic.
MOCO Explore MOCO →
TriggersFires when a new contact or lead is added to MOCO.
Fires when a field on a contact changes in MOCO.
Fires when a deal, case or record moves to a new stage in MOCO.
Fires when a deal is marked won in MOCO.
Creates or updates a contact in MOCO.
Creates a new deal in MOCO.
Moves a deal or record to a new stage in MOCO.
Logs a call, email, or note against a record in MOCO.
Common questions
Can Knit build “Record new Flic presses with presence in the MOCO app.” between Flic and MOCO?
Yes — describe it in the box above and Knit's Integrations Agent researches Flic and MOCO'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.