This is a valid JSON string / OBJ. You can extract the values within the external moustache and it parses without error. However, when I attempt to parse this within Flow (within a function), I receive the dreaded: "Unexpected token o" message.
UPDATED by OP: Okay, so Flow maintains the JSON Object format. I resolved by NOT parsing into an JSON object. Problem solved. But...still have recommendation on the header and footer areas of the Flow workspace. Please either remove the text or provide a hide button. Thanks!
By the way, just to check, I can run this msg.payload from my Node-Red instance (running within an IoT device) back into a local Node-Red function to parse it out (same msg.payload I'm sending to AT&T Flow) and parsing is successful.
Please contact me to discuss if needed.
Also....Is there anyway to remove the very large header area in the Flow designer screen as well as the very lard footer area? This is a huge PITA when trying to develop with AT&T Flow. Node-Red has a very (very) minimal header and basically no footer because they realized that the developer does not want to have to manage multiple scrolling elements when trying to write and debug flows.