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. There are 6 options today.

1. Push Notification

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

https://cdn.elev.io/file/uploads/PEfBOej3wR4slKcXFF0VfOndFuEYx_C9vFdA35csXyc/OPBpFlXH0EAkighNALdLKpkDwlFLAmN-QaZJkCJ0s-0/Screen Shot 2018-01-12 at 11.11.34-4hg.png

2. Send email

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.

https://cdn.elev.io/file/uploads/PEfBOej3wR4slKcXFF0VfOndFuEYx_C9vFdA35csXyc/2fxD76udK-rw6hIxcEb1LlJ0JsQ4oTJVNju-T7O0GOQ/create_action-X8A.png

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:

  1. $VARIABLE$
  2. $BUCKET$
  3. $VALUE$
  4. $UNIT$
  5. $TIME$
  6. $LOCATION$
  7. $DEVICE$

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.

E-mails can also be sent directly from scripts in the Analysis. For such action, you can use the e-mail service. Check the terms of use, and your plan before using the e-mail service.

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

3. Send SMS

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).

https://cdn.elev.io/file/uploads/PEfBOej3wR4slKcXFF0VfOndFuEYx_C9vFdA35csXyc/l-wmkemg7o_ESPtiHM-Sp3bFp3dvlEx44XhX-SRe7pc/config_sms-gO4.png

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:

  1. $VARIABLE$
  2. $BUCKET$
  3. $VALUE$
  4. $UNIT$
  5. $TIME$
  6. $LOCATION$
  7. $DEVICE$

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.

Some costs may occur when using the SMS service, which varies based on the country of operation. Check pricing, terms of use, and your plan before using the SMS service.

4. 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

https://cdn.elev.io/file/uploads/PEfBOej3wR4slKcXFF0VfOndFuEYx_C9vFdA35csXyc/_SfWtNYeLTQhbBcf4mdchy7HZMoxF4ZYEu2Yv-pTuJk/config_analysis-4d0.png

5. Publish to MQTT

This action can publish to an MQTT topic defined by the developer. This means that every time your trigger criteria is met, TagoIO will publish data to that predefined MQTT topic, this is very useful if you need to forward data to devices and/or applications. Topics are separated by buckets, that means, that every device that is linked to the same bucket and subscribed to that topic will receive the data published by TagoIO.

To set the MQTT action up, select the option Publish to MQTT, select the bucket which will receive that topic and type in the topic. The content of the MQTT payload that subscribed devices will receive can be defined as well.


6. Post data to HTTP 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.

https://cdn.elev.io/file/uploads/PEfBOej3wR4slKcXFF0VfOndFuEYx_C9vFdA35csXyc/keru9Dp4hNDnzZAMg7fbpVquvDs9X4P30yfsaGCBJVc/config_endpoint-6S4.png