Actions is a very powerful feature that gives you total control over your devices based on events determined by you. More than sending an e-mail or SMS based on certain conditions, with Actions you start tasks to send data back to the device, run scripts in the Analysis, and make a HTTP Post endpoint (very helpful when integrating Tago with other back-end systems). With these capabilities combined, there are limitless possibilities to create any event condition, not limited to a simple if/else condition.
To create a new Action, just click on the button ‘Action’ located at the sidebar, then click on + (the top right button). Give a name for your action and click Save.
The first thing to do when configuring an Action is to define which action you want it to take. Each type of action is described in the section below.
An e-mail will be sent when the condition is met. To create this action, select the Action to be takenas: Send e-mail, enter with the e-mail address, and a subject.
The message body can be as simple as a text: ‘Hi, your car is over the speed limit’. Or you can use special fields on the message to personalize it with real-time data from your bucket and devices. You can use most of the JSON field from our API:
For example, a personalized message like this: ‘Hi, your $DEVICE$ reached $VALUE$ $UNIT$ at $LOCATION$’, could created an e-mail like: ‘Hi, your Passat reached 73 mph at 43.0533,-86.4534’
To avoid sending e-mails continuously when a trigger condition is met, you may want to define a reset trigger condition. Check reset trigger to avoid issues with your logic and even your account.
Note: Tago has the capability to handle a high rate of emails per certain period of time. However, to scale it up smoothly and protect your account, notify us in advance in case you need to send more than 50,000 / day
An SMS will be sent when the condition Defining condition is met. To create this action, select the Action to be taken as: Send SMS, and enter with the phone number, including the country code. If there is no country code, the system will assume the USA code (+1).
The message body can be as simple as a text: ‘Hi, your car is over the speed limit’. Or you can specify fields in the message to personalize it with real-time data from your bucket and devices. You can use most of the JSON fields from our API:
For example, a personalized message like this: ‘Hi, your $DEVICE$ reached $VALUE$ $UNIT$ at the coordinates $LOCATION$’, would text: ‘Hi, you Passat reached 73 mph at the coordinates 43.05334,-86.45340’
To prevent from sending SMSs continuously when a trigger condition is met, you can define a reset trigger condition. Check Reset Trigger to avoid issues with your logic and even with your account (high number of SMSs, for example).
SMS can also be sent directly from scripts in the Analysis. For such action, you can use the SMS service.
Run Analysis Script
Actions can also initiate scripts that run in the Analysis. This is a very powerful feature, as you can define when your code will initiate. For example, you can initiate a data analysis every time certain data is sent from a device, or when it meets a certain condition.
To create this action, you need to select the Action to be taken as: Run analysis. Then, in the Run Analysis field, select the script that you coded and saved in the Analysis
HTTP Post End-Point
This action can post a data directly to an end point defined by you. When the action is initiated, it will POST the JSON data received (as defined by the variable in the Set Trigger) to the HTTP address defined.
To create this action, you just need to select the Action to be taken as: HTTP Post end-point. Then, in the HTTP Post End-point field, enter with the HTTP address. Below, we show one example.
This action can notify you on your account via browser or via the mobile app. You can set the title and the content of the notification.
The notification is only sent to the account where it was created, if you need to notify different accounts, check our documentation on the notification using analysis
In order to initiate an action process, certain conditions should be met. Internally, Tago uses triggersas flags to monitor this process.
One valid condition to start the action is when the selected variable meets the criteria defined in Set Trigger.
To configure how the event will be initiated, you need to configure the triggers. Enter with the variable to be tested (it is tested every time a new value arrives), the Condition, and the value to be compared against. When the condition is true, the trigger is set. Same thing for the condition defined to reset trigger.
The available test conditions are:
- Less than - condition is true when the value of the variable is less than the value defined
- Greater than - condition is true when the value of the variable is greater than the value defined
- Equal to - condition is true when the value of the variable is equal to the value defined
- Different from - condition is true when the value of the variable is different from the value defined
- Any- condition is true whenever a new value of the variable is sent to the bucket
Another condition depends on the Lock trigger after action is taken switch status. If it is NO, the action will be taken solely based on the Set Trigger condition explained above. If it is set to YES, the condition above will only be tested if the Trigger is not Locked. The status of the trigger can be manually changed as showed below, that is under the session ‘More’. A more common option to unlock the trigger is to use the Reset Trigger setup.
Note: Combined logic tests can be easily implemented in the Analysis. For example, if you want to take an action to send an SMS when the (temperature > 95C) AND (time_of_day == night) AND (User_at_home == false), you can simply create an Action to Run a script in Analysis every time the new temperature variable arrives, and just write a simple script to make the logic test. This method is very powerful to test basically any complex combination.
Each time a Set Trigger condition is met, the trigger is locked if the Lock trigger after action is takenswitch is set YES. In this case, the Set Trigger condition will only be tested again when the Reset Trigger condition is met. This is helpful to create an hysteresis for example.
However, if the Lock trigger after action is taken switch is set NO, the trigger will never be locked, and any time that the Set Trigger condition is met, it will take the defined action. Depending on your logic, it may be undesirable.
One example of undesirable situation could occur when you want to receive only one SMS when the temperature crosses above 95 C, but instead you receive one SMS for each time a new value of temperature above 95 C is sent (unnecessary and costly). You may want to implement an hysteresis using a Reset Trigger condition. If you define the condition to reset when temperature < 90 C for example, it would prevent this issue. Only one SMS would be sent, and the system would be locked until the temperature goes below 90 C. Which seems much more reasonable in this example.