When get system events in Addigy, sync it to Revel Digital.
When system events trigger in Addigy, forward event metadata to Revel Digital.
See all Addigy + Revel Digital integrations or talk to a human
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.
Revel Digital Explore Revel Digital →
TriggersFires when a new episode or production is published in Revel Digital.
Fires when someone subscribes or follows in Revel Digital.
Fires when a track is saved or added to a playlist in Revel Digital.
Adds a track or episode to a playlist in Revel Digital.
Creates a new episode or production in Revel Digital.
Adds a listener or subscriber in Revel Digital.
Common questions
Can Knit build “When get system events in Addigy, sync it to Revel Digital.” between Addigy and Revel Digital?
Yes — describe it in the box above and Knit's Integrations Agent researches Addigy and Revel Digital'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.