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. Currently, we offer 7 options.

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 notification using analysis. If you want to send a notification to a Run Usersee the next option.

2. Push Notifications to Run Users

This action can notify a Run User that belongs to your Run.

The structure is the same as the option above, with the exception that in this option you must specify which Run User you want to send the notification to.

3. Send Email

An e-mail will be sent when a condition is met. To create this action you must set the type as Send Email, enter the email recipients, and a subject.

You can set multiple recipients in the Send to field by separating them with a ;

You can use variables of the payload that triggered your action inside of the title and message. To understand more, check the end of this article.

To avoid sending e-mails continuously when a trigger condition is met, you may want to define a reset trigger condition. Check Trigger Unlock 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.

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

4. Send SMS

An SMS will be sent when a condition is met. To create this action, select Send SMS and enter the recipient phone numbers. 

Don`'t forget to use the country code on each phone number. If there is no country code, the system will assume the USA code (+1).

You can set multiple phone numbers in the field by separating them with a ;

You can use variables of the payload that triggered your action inside of the title and message. To understand more, check the end of this article.

To prevent the system from sending multiple SMS continuously when a trigger condition is met, you can define a reset trigger condition. Check Trigger unlocks to avoid issues with your logic and even with your account (high number of SMS, 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.

5. 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 Type of action as Run Analysis. In the fields below you can link up to 10 analysis that will be run when the action conditions are met.


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

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

You can use payload fields in the HTTP endpoint and in the HTTP headers, like the example above (http://myendpoint.com/post/$VALUE$).

Message Variables

In some action types, the message body can be as simple as a text like  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 payload 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 result in the message being:

  • Hi, your Passat reached 73 mph at the coordinates 43.05334,-86.45340

Also check out:

  • Actions
  • Analysis
  • Notifications