I tried searching in the documentation, but I could not find what is the exact format of the JSON that the “Post data to HTTP End-Point” Action sends. Here it mentions it is “as defined by the variable in the Trigger”. That means that it is not the same format as sent by the Device? Also, my device sends multiple variables, will this action only post the value of the single variable that triggers the Action?
If I use an Analysis, I can see from the console that I get the data of all the variables. But I am trying to avoid using Analysis as it does not scale well to the amount of data I expect to work with.
Action will only send the variable that triggered the event — not the full payload or batch of variables. So, if your device sends multiple variables at once and you want to forward all of them to your HTTP endpoint, you’ll need to process the incoming data using a decoder.
The decoder can bundle all values into a single variable and include the rest of the details inside the metadata field. This way, the Action can forward everything as part of one payload.
From our tests, the “Post data to HTTP End-Point” Action appears to send the full payload with all variables, including data such as metadata, group ID, bucket ID, created_at, etc., to our external endpoint, even when it is configured with a single variable to trigger the event (when “temperature” is “anything”).
This doesn’t match what you mentioned. Can we continue to rely on the behavior we’re observing?
You’re absolutely right, and thanks for testing that out. zsu[@user:10061942044]zsu got confused in his response there.
The “Post data to HTTP End-Point” Action does send the full payload with all variables to your endpoint, not just the triggering variable. This is the expected behavior. The data format follows TagoIO’s standard structure.
So yes, you can rely on what you’re observing.
I’ve also created a note for our team to update the Action documentation to be more specific about this behavior.