Skip to main content
Node type: filter · Version: 1 · Category: Logic Keep or remove collection items using strict rules. This node is not marked with the catalogue’s generic side-effect flag. That classification is not a guarantee that every configured operation is read-only; review the concrete action and its destination.

​
When to use this node

  • Keep or remove records from an explicit workflow collection.
  • Inspect rejected items without turning a collection decision into workflow-level branching.

​
Example: Keep active API records

Split an API result array, then retain only records whose active field is the boolean true.
Example settings
This shows the important settings, not a complete exported node.
  1. HTTP Request → Split Out → Filter.
  2. Use the Rejected output only when removed records need downstream handling.
  3. Inspect retained and rejected counts in execution history.

​
Configuration

​
Workflow JSON

The editor stores this node with the following implemented default configuration:
Default node configuration
Values may be entered literally or mapped from an earlier compatible output when the inspector exposes a mapping control. See Variables and data mapping.

​
Inputs

​
Outputs

​
Execution behavior

  • Rules use strict types: number 200 does not equal string 200.
  • Missing, null, empty strings, empty arrays, empty objects, and filtered items remain distinct.
  • The editor catalogue declares output (array), rejected (array) for mapping. The execution inspector can contain additional evidence fields; inspect a real result before selecting nested paths from object or any outputs.

​
Common issues

  • Use Condition for one workflow-level true/false decision.
  • Invalid regular expressions fail validation and runtime evaluation.

​
Where it can run

  • Desktop local runner
  • Paired self-hosted runner
  • Hosted runner

​
Test and inspect

Use Test node in the editor to preview this step with the current configuration. A full run records resolved inputs, outputs, logs, duration, and any artifacts in the execution inspector. Side-effecting or destructive nodes can require an additional confirmation or approved workflow permission.