When get system events in Addigy, sync it to Security Reporter.
When system events trigger in Addigy, log security telemetry in Security Reporter.
See all Security Reporter + Addigy 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.
Security Reporter Explore Security Reporter →
TriggersFires when a new user account is created in Security Reporter.
Fires when a new security or access event is logged in Security Reporter.
Fires when a scan, verification or risk check finishes in Security Reporter.
Creates a new user account in Security Reporter.
Deactivates a user's access in Security Reporter.
Runs a verification, fraud or risk check on a record in Security Reporter.
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.
Common questions
Can Knit build “When get system events in Addigy, sync it to Security Reporter.” between Security Reporter and Addigy?
Yes — describe it in the box above and Knit's Integrations Agent researches Security Reporter and Addigy'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.