When get system events in Addigy, sync it to Zoho Desk.
When system events occur in Addigy, create a ticket in Zoho Desk.
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.
Zoho Desk Explore Zoho Desk →
TriggersFires when a new support ticket or chat conversation starts in Zoho Desk.
Fires when a ticket's status changes in Zoho Desk.
Fires when a ticket in Zoho Desk is assigned to an agent.
Fires when a ticket in Zoho Desk breaches its response SLA.
Creates a new ticket in Zoho Desk.
Updates a ticket's status in Zoho Desk.
Assigns a ticket in Zoho Desk to an agent.
Posts a reply or internal note on a ticket or conversation in Zoho Desk.
Common questions
Can Knit build “When get system events in Addigy, sync it to Zoho Desk.” between Addigy and Zoho Desk?
Yes — describe it in the box above and Knit's Integrations Agent researches Addigy and Zoho Desk'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.