Maniuplating a msg:string so I can make it a msg.payload?

Hi @WalterWhite, see the other topic, it's caused by a bug in the node. I added a patch there. The issue however isn't so simply fixed throughout the flow, so you're better off patching the code yourself. What is happening is that rather than an object is outputted by the node, with a property "payload" set in that object containing the actual payload, the payload is outputting. This also causes other properties to be missing. As Node-RED requires messages to be objects, this means it can't be fixed through the "usual solutions" like utilising the change node to move the properties around. After all, there are no properties on a string.

For future reference, your code can't be imported. The forum software changes the empty [] brackets to a single square unicode character. See the explanation topic on how to export code and post it on the forums so that others can import it: How to share code or flow json