Setting up Vector Search Actions

Overview

Actions are customizable HTTP(S) requests that, with the power of Large Multimodal Models (LMM), are automatically triggered based on the outcome of a Policy assessment, using a natural language description of the Action's purpose.

Getting Started

Actions can be managed from the Actions page of Vector Search. Here, you will be able to Create a New Action, as well as View And Update Existing Actions.

Create a New Action

New Actions can be created by filling out the Create Action form at the bottom of the page.

Each Action has two sets of components: the Name and Description which determine when the Action should be triggered, and the HTTP(S) request configurations that determine the exact request to be triggered.

Use Prefills as a Starting Base

To help get started, Camio provides a number of modifiable preconfigured Actions in the Prefill dropdown of the Create Action form, which cover some of the more common use cases:

  • Notifying of compliance or violations on multiple cloud-based communication platforms, such as Slack and Teams.
  • Creating new issues or incidents in service management tools such as ServiceNow.
  • Creating new entries in cloud-based data storage and databases such as Snowflake and BigQuery.

Each Prefill will require the configuration of information to direct the request to the desired channel or instance on the select platform, such as a webhook URL or authorization header. Any required information is specified in all caps.

Using Natural Language to trigger an Action

Each Action requires a Name and Description, which the LMM will then use to determine whether the Action should be triggered after a given Policy assessment. These Descriptions can be used to trigger the Action in a specific state of compliance (compliant or noncompliant), or in the presence of a specific type of Policy violation described in the account's configured Policy.

The following are best practices for writing a Description:

  • Be concise. The LMM is often able to better understand a short single-sentence explanation of the Action's purpose than a longer multi-sentence explanation.
  • Specify the state of compliance when relevant. As it is possible to trigger Actions on either compliant or noncompliant Policy Assessments, Actions that should be triggered when there is no violation of Policy should clearly state such, and Actions that should be triggered on violation of Policy should clearly state such.
  • Use relevant keywords from the Policy. As the LMM will be directly referencing the configured Policy when determining the relevance of an Action to a Policy Assessment, it is best to use keywords that are present in the Policy in order to link an Action directly to a certain component of the Policy.

Below are various examples of various ways of using the Descriptions to leverage the LLM for fine-grained Action triggers.

Example: Differentiate Actions between compliance state and Policy components

A Policy configured to assess the compliance of vehicles, as well as potential fires in the area, can have three separate Actions to perform on noncompliant and compliant events:

  • "Use this to notify the security team of policy violations related to vehicles." Will trigger on noncompliant assessments containing any violation by a vehicle.
  • "Use this to alert the security team of a potential fire." Will trigger on noncompliant assessments that were flagged for any indications of smoke or fire.
  • "Use this to notify the team of a compliant assessment." Will trigger when an assessment is fully compliant.

Example: Differentiate Actions through details of a given subject of the Policy

If the Policy relates to the compliance of vehicles, and acts on and/or exempts certain classes of vehicles, such as construction and emergency vehicles, Actions can be configured to trigger based on the presence of a specific class of vehicle:

  • "Use this to alert the team of an emergency vehicle." Will trigger in the presence of any emergency vehicle (police, fire, EMS)
  • "Use this to alert the team of an ambulance or other EMS vehicle." Will only trigger in the presence of an EMS vehicle, and not other emergency vehicles.

The same can apply to a Policy which assesses the presence of uniformed employees wearing reflective vests and hard hat in a given area:

  • "Use this to alert the channel of a employee missing the required reflective vest or hard hat in violation of policy." Will trigger on policy violation when an employee is missing either component of the required safety gear.

Including Policy Assessment Information through the Body Template

To allow flexible inclusion of information related to the associated Policy Assessment that triggers the Action, Camio's Vector Search provides a set of parameters associated with the Policy Assessment that can be referenced in the Body of the request, configurable from the BODY tab of the form, by including the parameter wrapped in double curly braces. 

Below is the usage and description of all of the Camio-provided parameters:

Name Description Usage
title The title of the overall assessment, explaining the general reasoning for the assessment.

Input:

{{title}}

Output:

"An employee is missing the proper gear..."

description A detailed description of the event and the overall assessment.

Input:

{{description}}

Output:

"An employee is missing the proper gear (hard hat) required. This is in violation of the policy. Description: Two employees are visible on scene. The employee on the left side is wearing a reflective vest and white hard hat. The employee on the right is wearing a reflective vest, but is not wearing a white hard hat as required by policy, and is therefore in violation."

camera_name The name of the camera subject to the assessment.

Input:

{{camera_name}}

Output:

"CompanyCamera4K-01"

timestamp The timestamp of the Camio event in ISO 8601 format.

Input:

{{timestamp}}

Output:

"2025-01-15T02:59:15.588401+00:00"

search_url The Camio search URL to view the associated event(s) in the Camio feed.

Input:

{{search_url}}

Output:

"https://test.camio.com/app/#search;q=4KCamera+noncompliant"

image_url A link to the JPG cover image of the associated assessment, if available.

Input:

{{image_url}}

Output:

"https://ai.camio.com/api/content/u%2Fg_123456789.jpg"

content_url A link to the MP4 video of the associated event, if available.

Input:

{{content_url}}

Output:

"https://ai.camio.com/api/content/u%2Fg_123456789.mp4"

View And Update Existing Actions

At the top of the page is a table of all of the existing Actions associated with the current logged-in account. The rightmost column for each Action will contain the option to either Edit the Action, and update any of its existing configurations, or permanently Delete the Action from the account. 

Upcoming Features

In the future, we plan to enhance the Actions feature by allowing the LMM to automatically fill in custom parameters for the Action based on the results of the Policy Assessment, which can then be inserted into the HTTP(S) request as part of the Body, Path, or Query, much like the current Camio-provided parameters can.

 

 

 

 

Have more questions? Submit a request

Comments