Thanks so much for the explanation.
I have two routes for you.
If the purpose of the workflow you’re building is to just accept values over MQTT, rebuild the payload, and forward to AWS for more processing, would it be possible to just send directly to AWS? It’s very common for our customers leveraging Lamda or other AWS services to integrate them into Losant in this manner.
If you don’t want to report this value as device state, it should be possible to reassemble your payload in a workflow to send to AWS. More below.
Reassembling a Payload in a Workflow
There are two things to consider here:
We don’t guarantee the order of execution for the Workflow Engine. So, you’ll have to keep an index to organize your chunks (and possibly order if that’s important).
"chunk": "[ DATA ]",
Then you can use Workflow Storage to store the chunks or retrieve stored chunks.
You can use the Function Node to resemble the chunks.
You may have to use the Loop Node to support ordering.