When get system events in Addigy, sync it to Daylite.
When system events occur in Addigy, log the event against matching contact or project records in Daylite.
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.
Daylite Explore Daylite →
TriggersFires when a new contact or lead is added to Daylite.
Fires when a field on a contact changes in Daylite.
Fires when a deal, case or record moves to a new stage in Daylite.
Fires when a deal is marked won in Daylite.
Creates or updates a contact in Daylite.
Creates a new deal in Daylite.
Moves a deal or record to a new stage in Daylite.
Logs a call, email, or note against a record in Daylite.
Common questions
Can Knit build “When get system events in Addigy, sync it to Daylite.” between Addigy and Daylite?
Yes — describe it in the box above and Knit's Integrations Agent researches Addigy and Daylite'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.