Filter
Keep your pipelines clean by dropping irrelevant data instantly. Unlike the If node which branches execution, the Filter node acts as a stark gatekeeper. Any incoming item that fails your configured condition is silently dropped, streamlining downstream actions.
What can you do with Filter?
Instant Stream Sanitization
Aggressively bin empty objects, null values, or irrelevant Webhook pings early in the chain before they consume precious downstream workflow processing power.
Multi-Rule Constraint Logic
Combine strict conditions using AND/OR parameters. For example: Only allow items where "Subscription Status = Active" AND "Total Price > $100" to pass through.
Advanced Regex Compatibility
Harness the raw analytical power of Regular Expressions (Regex) to ruthlessly filter unstructured data streams based on incredibly complex text string patterns.
Detailed Usage & Configuration
The Filter node acts as a stark gatekeeper in your workflow. Unlike the If/Else node which acts as a router branching logic into true/false silos, the Filter node is designed purely to sanitize and drop incoming items abruptly.
1. Purging Bad Data
If you're processing a Webhook payload containing an array of 50 newly created customer accounts, you only want to process the ones where {{ $json.email }} strictly Is Not Empty. Attach a Filter node. It will meticulously iterate the array, keeping the 40 valid records and brutally discarding the 10 malformed blanks before they crash your downstream database integrations.
2. Multi-Rule Constraints
Construct a complex constraint matrix using AND/OR rules. You can filter users by enforcing they must be Status = Active AND Plan = Premium AND Balance > 50, entirely avoiding writing custom logic code for array reduction operations.