Evalink Integration
Evalink is an alarm-management platform. The Gaard integration closes the loop on an alarm that already exists in Evalink: it reads the original alarm referenced in the classification’s metadata and, when classification completes, creates a follow-up alarm in Evalink carrying the outcome: an actionable alarm when the clip is risky, or a false-alarm code when it is safe. The follow-up is linked back to the original alarm and to the clip in Gaard, so an operator sees the AI verification alongside the event that triggered it.
This page is part of Alarm Platforms.
How it works
Section titled “How it works”For Gaard to match the original alarm, each classification you send must carry two fields in its metadata:
source: the alarm source (Evalink).alarm_id: the identifier of the original Evalink alarm.
When the classification finishes, Gaard reads the original alarm from Evalink, creates a new alarm that references it, and marks the new alarm’s source as Gaard so it is never re-classified in a loop. If the integration is inactive, or the referenced alarm is already sourced from Gaard, no follow-up is created.
Prerequisites
Section titled “Prerequisites”- An admin role in the tenant.
- A flow to attach the integration to. See Flows.
- An Evalink API key.
- Classifications on the flow that carry
sourceandalarm_idin their metadata.
Set up the integration
Section titled “Set up the integration”-
In Settings → Platform → Integrations, select Evalink.
-
Choose the Flow.
-
Enter a Name.
-
Paste the API Key issued by Evalink.
-
Save.
Verify it
Section titled “Verify it”- Trigger a classification on the flow, with
sourceandalarm_idset in the request metadata so Gaard can find the original alarm. - In Evalink, confirm a new alarm appears, sourced from Gaard, referencing the original alarm and linking to the clip in Gaard.
If nothing appears, check that the integration status is active, the API key is valid, and the metadata carried a matching alarm_id.