📑Add Task

🔖 Adding a Task

1. Add a Send Email Task

On the Manage IoT Rules screen, select a condition to which you wish to add a task, and then select Send Email.

Input the email subject, recipient, and content in the newly added text box, and then click the Save Rule button to add the conditional task.

2. Adding a Send SMS Task

Click Add Condition on the IoT Rule Management screen to add a condition.

After entering the recipient and message content in the newly added input box, click Save Rule to add the conditional task.

3. Adding a Send Control Command Task

Click Add Condition on the IoT Rule Management screen to add a condition.

To add a conditional task, select a product model, device, and unit in the added input window, enter a control command, and click the Save Rule button.

4. Adding a Send Notification Task

Click Add Condition on the IoT Rule Management screen to add a condition.

Select the notification type, title, and recipient in the added input window, enter the content of the notification, and click the Save Rule button to add conditional task.

5. Adding an External Server Call Task

Click Add Condition on the IoT Rule Management screen to add a condition.

Server Address: This is the URL to which to send the request.

HTTP Method: Select the Request HTTP Method. You can select either POST, PATCH, PUT, or DELETE.

Header: The request header is defined as a key/value pair.

Body or Param: Configure the payload according to the request server rules. Body data may be configured in the following three ways.

raw(JSON): Configure and transmit the payload using the JSON format. The value of the Content-type header field is set to application/json.

form-data: The payload is configured as form data and transmitted. The value of the Content-type header is set to multipart/formdata.

x-www-form-urlencoded: The payload is constructed as a querystring before being transmitted. Key/value pairs are separated by an ampersand (&) and the key and value are separated by an equals sign (=). The value of the Content-type header is set to application/x-www-form-urlencoded.

For the Param, payload is configured as querystring and transmitted. Key/value pairs are separated by an ampersand (&) and the key and value are separated by an equals sign (=).