Skip to main content
Cisco Meraki

MT Automation Builder


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 setting up a Dashboard Automation or an external automation via a Webhook Integration.


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 only for representation


Step 2 - Create Rule

Once the Automation is named, the next step is to define the Rule for the Automation. These are further divided into 3 sub-steps



Choose a Sensor

In the 1st sub-step, users can select which sensor should the Automation be monitoring. At the time, only the MT30 Button Sensor could be selected in this step. The list will be further expanded to other sensor types in the future. 



Choose a Trigger

In the 2nd 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, will trigger the automation

  • 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 last step, the Action needs to be selected.

The Automation Builder has 5 different actions that can be enabled with a checkbox. This allows users to perform multiple actions with a single trigger. The Actions are as below:

Send a Notification

This action allows the user to configure a custom notification to an Email address or an SMS

Camera Snapshot

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.


  1. Snapshots are taken at the time of Event generation and NOT the button press. There’s about 5-10 second of delay between the button press and the snapshot time.

  2. Both Email and SMS recipients will receive a time stamped video link of the button press as well.

  3. Images will be converted to MMS for US/Canada numbers. Please make sure the end user can receive MMS. Carrier rates will apply to receive MMS.

  4. For Worldwide users, the image will be hosted by Twilio and a short url will be sent out.

Toggle SSID

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/turn on/turn off.

Only SSIDs in the same network as the MT30 can be selected as an action.

Toggle Switchport

Using this action, a user can configure a specific MS switchport to be toggled/turn on/turn off a specific or a group of switchport triggered by a button press



Send a Webhook command

Last but not the least, a Webhook action can also be added to the automation. In this action, users can configure a custom message to be included in the outbound Webhook payload.

The Webhook servers need to be configured under Network-wide>Alerts and only then will they show up in the 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.

Preview Automation

The last step in creating the automation is a quick Preview of the current configuration before the automation can be saved and applied.

  • Was this article helpful?