Filter
Category: Transform
Node id: filter
Filters an array of objects based on configurable conditions with AND/OR logic
What it does
- 20+ comparison operators including regex and type checks
- AND/OR logic for combining multiple conditions
- Detailed filter statistics: original, filtered, and removed counts
- Nested field access for complex object filtering
Use cases
- Filter patient records by age range or diagnosis code
- Select FHIR resources matching specific criteria
- Remove invalid or incomplete records from a dataset
Runtime
- Performance tier:
fast
Input ports
| Name | Type | Required | Description |
|---|---|---|---|
data | json | Yes | Array of objects to filter |
Output ports
| Name | Type | Required | Description |
|---|---|---|---|
result | json | No | Filter result: filtered_data array plus original_count, filtered_count, and removed_count |
success | boolean | No | Whether the filter operation completed without error |
Settings
Basic
| Setting | Name | Type | Required | Default | Allowed values | Description |
|---|---|---|---|---|---|---|
| Conditions | conditions | array | Yes | Array of filter conditions; each has field, operator, and value | ||
| Logic | logic | enum | No | AND | AND, OR | How to combine multiple conditions |
Errors
| Code | Description |
|---|---|
INVALID_CONDITIONS | Conditions configuration is missing or not a valid array |
INVALID_DATA | Input data is not a valid array |
Runtime notes
- The filtered items are in result.filtered_data (an array), NOT at result top level. Downstream nodes must read result.filtered_data to get the array.
- Filter KEEPS matching items (include semantics), it does not drop them. Items that fail conditions are removed.
- Non-object items in the input array are silently skipped — only map/object items are evaluated.
- Operators have aliases: eq/==/equals, gt/>/ greater_than, etc. Use the long form for readability.
See Build any workflow for how to put nodes together and Ports, types and data flow for how port types connect.
Quelque chose n'est pas clair ? Envoyez vos commentaires sur la documentation par courriel.