Hi @Jeremy_Bepoix, I suppose this depends a bit on how your stdout looks like.
The new Code node would require a valid n8n data structure, while the older Function/Function Item nodes were more lenient about this. The basic logic should still work though once you add the item structure.
Here is a quick example of a workflow similar to the one on your screenshot using the code node. I tried this in a Linux docker container, so if you’re using Windows you might need to use a different command on the Execute Workflow node to return valid JSON.
Here I am first applying the magic of JSON.parse() to the stdout field of the first input item. $input.first() would reference the incoming JSON/table data of the first item (listed here), .json would reference an item’s JSON data (the kind of data you see in the table or JSON view of n8n) and .stdout finally points to the stdout field.
Last thing I do is use .map() to move each of the items of our array coming from stdout under a json key as per n8n’s data structure.