Note: This documentation refers to Gravio 3.8 or older. For Gravio 4 or newer, please refer to the respective documentation on .

The HTTP Post Action Component allows you to create HTTP POST and GET requests to an URL.

Important Note:

  1. “Query String” is used for the query string, which is passed as a query string in the URL parameter. This can be used for GET or POST and any format of Content-Type.
  2. “Body” is used for the content body of HTTP request. This can be only used for POST request and it’s ignored for GET requests.
  3. Both “Query String” and “Body” can be specified in the format var1=value1&var2=value2. The component parses this string and formats corresponding the “Content-Type”. So, if you choose application/json, the above value in the “Body” would have to be { "var1": "value1", "var2": "value2"}.

You can use the sensor data as variables within a string. An example could be the following application/json that posts the sensor type as well as the value: "{\"DataKind\":\"" + av.DataKind + "\", \"DataValue\":\""+av.DataValue+"\", \"SenderId\:\""+ av.SenderId +"\"}"

av. in the variable name stands for “action variable” which is the variable that’s passed on by the sensor / trigger.

When “Authentication Type” is selected, basic authentication or Bearer authentication can be used. Please specify the authorization token in “Authorization Value”.

If you tick the “output request/response as file” checkbox, you will find the files corresponding to the requests under <your os' application support folder>Gravio/action/data/httppostdump . This functionality is intended to be used for debugging purposes.

If you decide to “output request/response files”, you will find the post and response data in the folder httppostdump in your <Gravio>/action/data folder of Gravio.

Was this helpful?

Yes No
You indicated this topic was not helpful to you ...
Could you please leave a comment telling us why? Thank you!
Thanks for your feedback.