I’m creating a new workflow and using the new Code node and this is the first time I’m using after the update.
I’ve ran into some issues that I didn’t have before with the FunctionItem node. Here is an example of code working on FunctionItem but failing to work on Code Node.
Hi @domantis, yes, the code node is a bit stricter than its predecessors and that is by design I think. Unnamed values like you’d get from a return true; don’t really fit in the n8n data structure.
Sorry if this causes any trouble . You should still be able to use the existing Function Item nodes in your workflows though.