Automation Builder is a powerful tool purposefully built to provide a way to tie Dashboard actions to a click of the MT30 Smart Automation Button. This article is intended to walkthrough the setup of a Dashboard Automation or an external automation via a Webhook Integration.
Creating Automations requires full organization or network admin permissions.
Currently Automations can only be assigned to an MT30 Smart Button.
Creating an Automation
The Automation Builder can be accessed by navigating to the Environmental>Overview page and selecting the Automations tab
Users can create a New Automation using the option on the top to get started with you first Automation
Once the New Automation option is selected, users are presented with a guided flow to create the automation
Step 1 - Start Here
In the first step, users can give a name to the automation and also select an icon for quick reference. These icons are for representational purposes only and have no effect on the Automation functionality.
Step 2 - Create Rule
Once the Automation is named, the next step is to define the Rule for the Automation. This is further divided into 3 sub-steps.
Choose a Sensor
In the first sub-step, the user selects which sensor the Automation will be monitoring. As of this moment, only the MT30 Button Sensor can be selected in this step. The list will be further expanded to other sensor types in the future.
Choose a Trigger
In the second sub-step, the type of reading can be selected to be used to trigger this Automation. In the case of MT30, the following triggers can be selected:
Any Press - Anytime the MT30 is pressed (regardless of how long its been pressed for) the automation will be triggered
Short Press - When the MT30 button is pressed for less than 1 second, the Automation will be triggered
Long Press - When the MT30 button is pressed for more than 1 second, the Automation will be triggered
Choose an Action
In the third and final sub-step, the Action is selected.
The Automation Builder has five different actions. These actions can be configured using the simple Graphical User Interface (GUI), as shown above. One or more of the actions can be selected, which allows users to perform multiple actions with a single trigger. The available Actions are detailed below:
Send a Notification
This action allows the user to configure a custom notification to an Email address or an SMS
The Camera Snapshot action allows the user to configure up to 5 MV camera snapshots to be taken when the MT30 button is pressed.
Once the MV cameras are selected, an Email Recipient or an SMS Recipient can be added.
Snapshots are taken at the time of Event generation and NOT immediately following button press. There is approximately a 5-10 second delay between the moment the button is pressed and the moment the snapshot is taken.
Both Email and SMS recipients will receive a time-stamped video link (leading to dashboard footage) of the button press as well.
Images will be converted to MMS for US/Canada numbers. Please ensure the end user can receive MMS. Carrier rates will apply to receive MMS.
For users outside US/Canada, the image will be hosted by Twilio and a short URL will be sent instead.
Another Dashboard automation where a user can configure a specific SSID in the same Wireless Network to be toggled when a button is triggered.
In this action, users can select which SSID they want to toggle on or off.
Only SSIDs in the same network as the MT30 can be selected as an action.
Using this action, the user can configure a specific MS switchport (or a group of switchports) to be toggled on or off, triggered by a button press.
Send a Webhook command
A Webhook action can also be added to the automation. In this action, the user configures a custom message to be included in the outbound Webhook payload.
The Webhook servers must first be configured under Network-wide>Alerts. Only then will they appear in the dropdown list.
Step 3 - Assign Devices
Once the Automation rule is set up with the trigger and the action, the guided flow will allow users to assign a device to the automation. The list will only show MT30s in the network at the moment.
The the final step, the user sees a Preview of the current configuration before the automation is saved and applied.