Skip to main content

List Filter

Runs on: Shared — pure logic, runs on the Community backend or inside a chatbox overlay.

The List Filter node splits a list into two based on a condition. Items that match the condition go to the Matching output; everything else goes to Not Matching. Both outputs are the same kind of list as the input, so you can keep working with either one — chain another list node onto them, count them with List Length, or send them on to List Sort / List Take.

For lists of plain strings, numbers or booleans, the condition compares the value directly. For lists of custom or built-in objects, pick a Field to compare that field on each object instead of the whole object — or wire the field input to choose it at runtime.

The Condition select offers different operations depending on what's being compared: Equals / Not Equals always, plus Is Greater Than / Is At Least / Is Less Than / Is At Most for numbers, or Contains / Does Not Contain / Starts With / Ends With for text.

Inputs​

NameTypeDescription
listlistThe list to filter.
valueanyThe value to compare against. When Field is set, this is compared to that field on each object.
fieldstringOptional. Wire this to choose the field to compare at runtime instead of picking it in the node.

Outputs​

NameTypeDescription
resultlistThe items that matched the condition, same item type and order as the input.
restlistThe items that did NOT match, same item type and order as the input.

Configuration​

  • Condition: the comparison to run. Defaults to Equals.
  • Case Sensitive: shown for text comparisons. Off by default on new nodes.
  • Field: for lists of custom or built-in objects, pick which field to compare. Leave it as "Whole Item" to compare entire objects.

Example​

You keep a raffle entry list of objects with username and tickets fields. Use List Filter with Field set to tickets, Condition set to Is Greater Than, and 0 as the value, to drop anyone who spent all their tickets before the draw — wire Matching into List Random Item to pick a winner. "Remove entries where tickets is 0" is the exact same node — just wire Not Matching onward instead.