When get system events in Addigy, sync it to Todoist.
When system events trigger in Addigy, create a follow-up task in Todoist.
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.
Todoist Explore Todoist →
TriggersFires when a new task, job or item is created in Todoist.
Fires when a task in Todoist is marked complete.
Fires when a task's due date in Todoist is coming up.
Fires when a task, job or project changes status in Todoist.
Creates a new task, job or item in Todoist.
Updates a task's status or assignee in Todoist.
Posts a comment on a task in Todoist.
Assigns a task in Todoist to a team member.
Common questions
Can Knit build “When get system events in Addigy, sync it to Todoist.” between Addigy and Todoist?
Yes — describe it in the box above and Knit's Integrations Agent researches Addigy and Todoist'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.