Nope, this new code node really doesnt want to play nice with me at all.
in “Run once for all items”
const html = $input.first().json.html;
works
const html = $input.all().json.html;
doesnt neither does
const html = $input.all();
also the documentation doesnt help either, i think there is a fundamental lack of examples are troubleshooting on there, it works completely differently to the function nodes and it just seem so much more difficult to get simple things to work. perhaps I’m missing something here, this shouldn’t be that difficult to use… hmmm
Sorry to hear that you have problems. I hope the following makes it clearer.
$input.first() is the first item of the input.
So it is an object with looks roughly like this for your example above:
{
json: {
html: '....',
}
}
$input.all().json.html are all the incoming items and is so an array of objects and looks for your above example like this:
[
{
json: {
html: '....',
}
},
{
json: {
html: '....',
}
}
]
For that reason does $input.all().json.html not work as you try to access json of an array which is undefined and then you try to access html of undefined.
I hope that helps and makes things clearer! Thanks a lot for bringing this up, will check in with the team regarding improving the docs.
ok so how do i reference in a code node to point to the “xxxx”
[
{
"html":"xxxx"
},
{
"html":"xxxx"
},
{
"html":"xxxx"
}
]
In the code node I need it to run the script against each incoming item from the previous input.
Which “xxxx” as there are 3 of them?
The first one would be:
$input.all()[0].json.html
// or
$input.first().json.html
The second one:
$input.all()[1].json.html
And the last/third one:
$input.all()[2].json.html
// or
$input.last().json.html
Or you can, for example, combine all of them into one single string with
$input.all().map(item => item.json.html).join(',')
i need to reference them all one by one for the code node to process the values etc bear in mind I don’t know how many there will be as the input
In this case you can use the example that is directly given in the Code-Node when you create a new one.
For “Run Once for All Items” it looks currently like this:
// Loop over input items and add a new field
// called 'myNewField' to the JSON of each one
for (const item of $input.all()) {
item.json.myNewField = 1;
}
return $input.all();
so for example:
for (const item of $input.all()) {
item.json.htmlWrapped = `<html>${item.json.html}</html>`;
}
return $input.all();
Or if you change it to “Rune Once for Each Item” the example is this:
// Add a new field called 'myNewField' to the
// JSON of the item
$input.item.json.myNewField = 1;
return $input.item;
so the equivalent to my above example would be:
$input.item.json.htmlWrapped = `<html>${$input.item.json.html}</html>`;
return $input.item;
If I change it to run once for each item
const html = $input.item.json.html;
I get this error:
ERROR: Unknown top-level item key: 0 [item 0]
Access the properties of an item under `.json`, e.g. `item.json`
the input from the node before is:
[
{
"html":"html is here already"
},
{
"html":"html is here already"
},
{
"html":"html is here already"
}
]
@RedPacketSec I just tried to reproduce your error and think I found your problem. Might it be that you return $input in your code node? The code node in Run once for each item mode expects you to return $input.item.
Here’s a quick workflow that I used to show this:
The error message that you get is very misleading, though. So we will see what we can do there. Thanks for bringing this up 
3 Likes
ok, so that sort of helps, now i need to massage that into my massive script. Thank you that gives me something to work with, much appreciated.
i gave up in the end and bodged it, i really do not like the new code node its 10x more difficult to understand how to wrangle the data.
I just kept it as:
and then just split it in batches of 1 so each one will be the first
Hi @RedPacketSec I’m also (still) struggling with the new code node. I had this simple FunctionItem that would convert the following with just return item.fieldData
I still haven’t found out how to achieve this in the Code node …
In run once for all items:
// Loop over input items and add a new field
// called 'myNewField' to the JSON of each one
for (const item of $input.all()) {
item.json = item.json.fieldData;
}
return $input.all();
in Run once for each item:
$input.item.json = $input.item.json.fieldData;
return $input.item;
2 Likes
@Bram Thanks! … keep wondering why it’s more complicated with the new Code node than with the old Function(Item) nodes … at least to me …
1 Like
It’s just a bit different. I was very annoyed by it as well in the beginning, but you’ll get used to it.
Atleast it does make sense and it more or less the same for each mode now. 
i really dont get along with it at all, i avoid using it as much as possible now, its just overly complicated whereas the older way as complex but worked pretty well.
Thing is (at least for me) that it’s hard to build a workflow without the Code node. I decided to totally forget the old Function nodes, and study the Code node. For this, I re-read the docs and put together a workflow with a few samples that hopefully illustrate the basics. I’m going to share this, together with a little write-up/explanation in the coming days …
1 Like
yeah same for me alot of my flow use custom code in the code node, which means i end up spending more time data wrangling and troubleshooting javascript when really the whole point of using n8n was to cut my time down. so i spend intense periods getting stuff to work and then try to not use it as much as possible except where i can only do it with code.
It’d be really handy if there was a python node etc.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.