When get system events in Addigy, sync it to ServiceNow.
When system events trigger in Addigy, create an incident record in ServiceNow.
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.
ServiceNow Explore ServiceNow →
TriggersFires when a new ticket or incident is logged in ServiceNow.
Fires when a ticket or incident is updated in ServiceNow.
Fires when a new user, client or device record is added in ServiceNow.
Creates a ticket or incident in ServiceNow.
Updates an existing ticket or incident in ServiceNow.
Adds a note to a ticket in ServiceNow.
Common questions
Can Knit build “When get system events in Addigy, sync it to ServiceNow.” between Addigy and ServiceNow?
Yes — describe it in the box above and Knit's Integrations Agent researches Addigy and ServiceNow'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.