The idea is:
Being able to filter the output of a node right after execution without adding a filter node behind it to reduce the overhead of transmitted fields within the n8n builder for better visibility
My use case:
Large workflows tend to have many input nodes with a high number of data being output from all those nodes. The longer the list gets, the more messy all this data looks like. If I add a filter node behind the output node, the output of the former node will still be displayed in the list hence offering no advantage.
I think it would be beneficial to add this because:
Large workflows are becoming hard to maintain because of the high number of unused values.
Any resources to support this?
/
Are you willing to work on this?
I am not a developer but I would be happy to help however possible.
It would be best if we had a switch (Filter Output) within each nodes properties which can be enabled. Afterwards you can Drag-and-Drop output fields from a test run into the filter to add these fields as output.
Test output should always return ALL fields so that the filter mustnt be disabled before testing the run. Only when executing previous nodes, all “unfiltered” values should be omitted from the output.