Allow ItemList to Extract a path from Object

[luizeof]

The idea is:

Given a nested JavaScript object, the goal is to extract the object from a certain depth (path), without having to use the function node (a low-code way).

My use case:

For example, node Webhook always returns data like this:

If we only want to use the body, we have to use the node function (which is a problem for non-devs).

If using ItemList to extract the body, it actually throws an exception:

This simple pull-request allows the ItemList to extract data from the given path of both arrays and objects:

I think it would be beneficial to add this because:

Any resources to support this?

Allow ItemList to Extract a path from Object

Are you willing to work on this?

Allow ItemList to Extract a path from Object

[RedPacketSec]

+1 for my vote, but dont have any spare, but I logged a post about this literally 2 mins ago

[Improvement] Item Lists Node

For some JSON results, we get back nested arrays, some come back as nested objects etc For the results that are not an array, it would be handy for the items list node to detect this and allow it to continue processing and splitting the data otherwise we get this: [image] And then need to whip out a function node to get the job done. Would be nicer if this node was a bit more robust with the data handling.

[RicardoE105]

@luizeof

If we only want to use the body, we have to use the node function (which is a problem for non-devs).

You can do that with the set node.

Example workflow

@luizeof

This simple pull-request allows the ItemList to extract data from the given path of both arrays and objects:

Not sure if the split item operation it’s the place for that.

@sirdavidoff

[RedPacketSec]

ideally, the list node should automagically be able to handle this

[RedPacketSec]

@RicardoE105

You can do that with the set node.

this can be an awful lot of manual work that isn’t suitable for large data sets, maybe its ok for one or two results