Name inputs to filter node

Would it be possible to name inputs for the filter node? Gets confusing at times when using the outputs from this node as they’re just “output list 1” “output list 2” and so on

Hey @Jamesp – Definitely makes sense and it is on the roadmap, its just quite a bit of lift as this would affect other aspects of the platform as well. Router node in such cases should work well, it has all the same condition types as the filter node and preservers the input names.

This topic was automatically closed 20 days after the last reply. New replies are no longer allowed.