When new notification in K Factors, sync it to Addigy.
When a new notification is logged in K Factors, sync the event data to Addigy.
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.
Addigy Explore Addigy →
TriggersFires when a device connected to Addigy comes online.
Fires when a device connected to Addigy goes offline.
Fires when a reading from a device in Addigy crosses a set threshold.
Sends a control command to a device via Addigy.
Adds a new device to Addigy.
Records a sensor reading or event from Addigy.
K Factors Explore K Factors →
TriggersFires when a new lead comes in from an ad campaign in K Factors.
Fires when K Factors records a conversion or offline event.
Fires when a new ad or campaign goes live in K Factors.
Sends an offline or server-side conversion event to K Factors.
Adds a contact to a custom audience or customer list in K Factors.
Removes a contact from a custom audience in K Factors.
Common questions
Can Knit build “When new notification in K Factors, sync it to Addigy.” between Addigy and K Factors?
Yes — describe it in the box above and Knit's Integrations Agent researches Addigy and K Factors'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.