Skip to main content

What It Does

  • Evaluates filter rules row-by-row
  • Splits your dataset into two parts:
    • βœ… If-True: rows that meet your conditions
    • ❌ If-False: rows that don’t
  • Preserves all columns in both outputs
  • Enables conditional routing across your play

🏁 Getting Started

If-Else node configuration screenshot
1

Add the Node

Drag in the If-Else node from the panel.
2

Define Filter Logic

Select a filtering operator (AND or OR) and add your condition(s).
3

Run the Node

The node will return:
  • βœ… If-True: rows that match your rules
  • ❌ If-False: rows that don’t

Inputs

πŸ› οΈ Required Fields

  • Condition Logic (βœ…)
    Choose AND (all rules must match) or OR (any rule matches).
    Why it matters: Defines how your filters combine.
  • At Least One Filter Condition (βœ…)
    Each condition includes:
    • Column to check
    • Rule type (e.g. is_equal_to)
    • Value (if needed)
      Why it matters: This logic controls how your rows get routed.

Output

Two outputs:
  • βœ… If-True: All rows that satisfy your filter logic
  • ❌ If-False: All rows that do not
Both outputs retain the full dataset schema β€” nothing is dropped.
If-Else output panel screenshot

🧠 Available Conditions

ConditionDescription
is_equal_toExact match
is_not_equal_toNot equal to
is_greater_thanGreater than (numeric only)
is_less_thanLess than (numeric only)
is_emptyField is blank or null
is_not_emptyField contains data
is_trueBoolean is true
is_falseBoolean is false
containsField contains a specific string
does_not_containField does not contain string

πŸš€ Example Use Cases

ScenarioSetup Example
Segment Nrev AI contactscompany is_equal_to Nrev AI
Route high-value dealsdeal_size is_greater_than 10000
Flag incomplete rowsemail is_empty
Identify non-closed oppsstage is_not_equal_to closed-won
Separate Sayanta’s accountsowner_email is_equal_to sayanta@nrev.ai

✨ Pro Tips

Use AND to get surgical (e.g., country = India AND tier = Strategic); use OR to cast a wider net (e.g., score > 90 OR requested_demo = true).
Connect both outputs to different downstream steps β€” like enrichment for one, and cleanup for the other.

⚠️ Important Considerations

One output empty? Totally normal β€” just means no rows met (or missed) the filter. Tweak logic if needed.
All columns are preserved. Only row selection changes β€” your schema stays the same.
Make sure your rule matches the data type β€” like using numbers for is_greater_than, not text.

πŸ›  Troubleshooting

SymptomLikely CauseFix
Both outputs are emptyNo input or no conditions setAdd valid input and logic
One output is emptyAll rows match one pathAdjust conditions for better split
β€œInvalid value” errorType mismatchEnsure values match column types

πŸ“ FAQ

Yes β€” add as many as needed, and select AND or OR to control how they combine.
Yep β€” use is_empty or is_not_empty to route those rows.
Yep β€” every row in both outputs keeps the full schema. Nothing gets dropped, just split.
Filter keeps only the rows you match. If-Else gives you both sides of the story β€” in two clean outputs.

πŸ’° Pricing

The If-Else node is free β€” no credits required.

Branch your play with precision β€” split records into two smart streams and route them like a pro. πŸ”€