Login

Condition

The Condition node

Lede. Routes the upstream value down a Success or Fail branch based on a predicate.

Group: Condition · Available in: all text-bearing workspaces · Central node: No

Purpose

  • Show different content for "active" vs. "inactive" records.
  • Pick one of two style branches based on a column value.
  • Skip certain downstream nodes by routing them to the Fail branch.

Where to find it

Add Node ▸ Condition ▸ Condition

How it works

Configure a predicate against record columns (e.g. Stock greater than 0). On evaluation the predicate runs against the current record; if it matches, the upstream value is emitted on Success, otherwise on Fail. The branch that doesn’t fire propagates an invalid path signal downstream, so unused nodes don’t produce output.

The Data input is optional. When wired, the value passes through to whichever output fires. With nothing wired, the node still routes downstream connections; the predicate alone decides which branch is alive.

Sockets

Direction Name What it does What you can connect
Input Data Optional value to forward to the chosen branch. Any text-producing node.
Output Success Fires when the predicate matches. Anything downstream.
Output Fail Fires when the predicate does not match. Anything downstream.

Settings

Setting What it does
Predicate The condition (e.g. Stock > 0, Category == 'New'). Edited via the predicate panel.
Enable condition Toggles whether the predicate is evaluated. When off, the node passes through unchanged on both branches.

Example (end-to-end)

Scenario. Bold-red headline for sale items, normal otherwise.

Wiring.

[Data Text: Name] → [Placeholder.Content]
[Condition: SaleFlag == "yes"]
       ├ Success → [Style Text: "BoldRed"] → [Placeholder.Style]
       └ Fail    → [Style Text: "Normal"]  → [Placeholder.Style]

Empty / error behaviour

  • Predicate evaluation error: the node logs the error and falls through to Fail.
  • Both branches eventually connect to the same modifier socket on the placeholder; only one fires per record.

Limitations

  • Two-way branching only. For more branches use Dynamic Condition.
  • Predicate runs against the current record’s master row by default; inside a Table or Repeater it runs against the secondary-sheet iteration row.

Common pitfalls

  • Both branches show output. Both Success and Fail connect to non-modifier sockets that consume both; if both are wired into the placeholder’s Content, only one fires per record but it still chains values – check that the predicate routes the way you expect with a preview row.
  • Quoting column values. Use quotes in the predicate panel for string literals ('yes'), not for column names.
  • Dynamic Condition – many branches instead of two.
  • Any of the Style and Data nodes – common consumers of Success / Fail.

Screenshots

📷 Screenshot [NEU]: Condition predicate editor 📷 Screenshot [NEU]: Two-branch wiring example

Not found what you're looking for?

Node Reference · Last updated 3 weeks ago

Comparison
Documentation
Copyright ToolboxCode UG