List Contains

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

The List Contains node checks whether a given value is present in a list. If the value is found, the data is routed to the Pass output. If it is not found, it goes to the Fail output. Either way, the searched value is forwarded so downstream nodes can continue working with it.

Primitive lists (strings, numbers, booleans) compare the value directly — case-sensitive by default, unless you turn off Case Sensitive. Lists of custom or built-in objects can match on a single Field instead of the whole object, or compare whole objects structurally (equal content matches regardless of key order).

Inputs

Name	Type	Description
list	list	The list to search through.
value	any	The value to look for. When Field is set, this is compared to that field on each object.
field	string	Optional. Wire this to choose the field to match on at runtime instead of picking it in the node.

Outputs

Name	Type	Description
pass	any	The searched value, forwarded if it was found in the list.
fail	any	The searched value, forwarded if it was not found in the list.

Configuration

• Case Sensitive: shown for text comparisons. Off by default on new nodes. Existing nodes keep strict (case-sensitive) matching until you flip it.
• 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 maintain a list of banned words for your channel. When a viewer sends a chat message, extract each word and pass it through List Contains with your banned-words list. If the word hits the Pass route, trigger a timeout or deletion action. If it hits Fail, allow the message through normally.