Page History
...
| Parameter | Description |
|---|---|
| Name | Name of the action (optional) |
| Method | Which HTTP method should be used. |
| Port | Port of the target endpoint Example: 80 |
| Hostname | Hostname of the target endpoint Example: belladatiiotservice.com |
| Relative URI | Relative URI of the target endpoint Example:/postendpoint |
| HTTP headers | Specification of HTTP headers; one header per row Example: header1=value1header2=value2 |
| HTTP POST content | Specification of HTTP body. It is possible to reference the input values by using tags with following format: ${NameOfField}. Example: The pressure is ${pressure} and the temperature is ${temperature}. |
| Send as Form | Enables URL-encoding of the data, similar to --data-urlencode from cUrl. When enabled, each row of the content is one entry splitted by =. Example: From=+123456789 Body=This is the message To=+987654321 |
| Authentication type | What type of authentication should be used. Available options:
|
| Use SSL | Enables SSL. |
| Continue on error | This toggle influences the behavior of the sender in a situation when the sending of the data fails. When disabled, unprocessed data are not deleted from the receiver and the action is triggered on the same data again. When enabled, the data are deleted from the receiver and the action is not triggered until new data arrive. |
...
Overview
Content Tools