Skip to documentation
Screebits Docs
Flow Editor
Open Screebits
  • Screebits
  • Flow Editor documentation
  • Blueprints
  • Your first steps in Screebits
  • Workspace, strategies and account
  • Get started with the Flow Editor
  • Build an RSI Momentum Alert
  • Flow Editor concepts
  • How a strategy starts and continues
  • Control and data connections
  • Nodes, parameters, outcomes, and ports
  • Plans and feature availability
  • Saves, versions, and checkpoints
  • Tactical and Portfolio strategies
  • Validation and readiness
  • Flow Editor mode guides
  • Build Portfolio strategies
  • Build Tactical strategies
  • Flow Editor guides
  • Add a Quant Hub metric
  • Configure a node
  • Configure Settings and visual preferences
  • Connect nodes
  • Create a strategy
  • Create checkpoints and restore versions
  • Reset a Flow safely
  • Debug and replay a Backtest
  • Fix validation issues
  • Use keyboard shortcuts
  • Manage variables
  • Run a Backtest
  • Save and resolve conflicts
  • Work on tablet and mobile
  • Use Quick add
  • Use the Inspector
  • Add, move, duplicate, and remove nodes
  • Flow Editor examples
  • Portfolio rebalance with risk limits
  • Tactical order and position monitoring
  • Use Backtest Center
  • Read a Backtest result
  • Compare and export Backtests
  • Explore Quant Hub
  • Metric parameters, charts and overlays
  • Flow Editor node reference
  • Condition
  • Flow Editor troubleshooting
  • Troubleshoot activation and validation
  • Troubleshoot Backtests and replay
  • Troubleshoot compact layouts
  • Troubleshoot connections and data types
  • Troubleshoot plans and locked features
  • Troubleshoot Quant Hub in the Flow Editor
  • Troubleshoot save, offline, and conflicts
  • Backtests and responsible use
  • Flow Editor glossary
  1. Screebits
  2. /Flow Editor documentation
  3. /Flow Editor node reference
  4. /Condition
IntermediateLast verified Sep 30, 2026

Condition

Compares values and selects Match or No Match.

On this page
  1. When to use
  2. Example
  3. Common problems
  4. Next steps

Compares values and selects Match or No Match.

When to use

Use Condition when the control path must branch according to a value comparison. It needs a control arrival from an executable path and the values required by its chosen operator. A data edge into Left alone does not start the decision. Condition works in Tactical and Portfolio; some operators, including crossAbove and crossBelow, have their own Pro requirement.

Example

In an RSI alert, connect Event Trigger.On Event → Condition for control and Indicator.RSI → Condition.Left for data. Set Operator to >, Right source to Literal, and Right literal to 60. Connect Condition.Match → Alert. The literal supplies the right-hand number inside the node, so no Right data edge is needed. In the Inspector, the Right handle is inactive for this choice.

Left RSITestControl outcomeWhat happens to an Alert on Match
5858 > 60 is falseNo MatchIt is not reached.
6060 > 60 is falseNo MatchIt is not reached.
6262 > 60 is trueMatchIt is reached.

This is a level comparison: consecutive bars above 60 can reach Match repeatedly. An operator that tests a crossing is a different choice and can require previous values and a different plan. The table is a teaching example with supplied RSI values, not a measured historical run.

To compare two changing values instead, choose Right source = Data Port and connect a compatible value to Right. The active fields and ports then change. For equality or inequality, select the literal's type where requested; for unary isTrue or isFalse, there is no right-hand comparison value. Read the generated conditions below as possible configurations, not fields to fill simultaneously.

Try it here

Explore Condition

Compares values and selects Match or No Match.

Exercise steps
  1. Change Right source from Literal to Data port.
  2. Observe the required Right input and its validation; return to Literal to fix it.
Event TriggerIndicatorData SourceCondition
Graph preview — a diagram of the example

Common problems

If Right is missing, first check whether you selected Literal or a unary operator; that can be correct. If you cannot connect Bars to Left, use a compatible scalar such as Indicator.RSI rather than a bar collection. If the node looks configured but Alert never runs, trace the control path from the primary event to Condition, inspect the active Left input, and check which outcome is connected. Result is a Boolean data output; it does not replace the Match control edge. An unused No Match branch may be intentional and can be informational rather than blocking.

Validate the whole graph, then save and reopen it before treating the configuration as persistent. A graph with Condition and Alert but no Order does not create trades. For a complete five-node walkthrough, use the RSI Momentum Alert.

Next steps

Use the generated Parameters, Outcomes, and Data Ports below to check the option and port active in your configuration. Continue with nodes, ports, and outcomes if the distinction between Match and Result is unclear, or connection troubleshooting if an edge is rejected.

Node facts

These facts come from the current Flow Editor node catalog.

Node type
Condition
Activation role
No activation role
Category
Condition
Availability
Tactical and Portfolio
Modes
Tactical and Portfolio
Required plan
None
Behavior
Makes a decision
Control inputs
1
Output data types
Yes or no

Parameters

NameInput typeRequirementDefaultOptions and constraints
OperatorSelection listRequired>Options: >, <, >=, <=, ==, !=, Crosses above (requires Pro), Crosses below (requires Pro), Is true, Is false
Right sourceSelection listRequired when showndataPortOptions: Right port, Literal; Shown when Operator is one of >, <, >=, <=, ==, !=, crossAbove, crossBelow
Literal typeSelection listRequired when shownnumberOptions: Number, String, Boolean, Date and time; Shown when Operator is one of ==, != and Right source is literal
Right literalValue type depends on the operatorRequired when shownNot setShown when Operator is one of >, <, >=, <=, ==, !=, crossAbove, crossBelow and Right source is literal

Primary parameters

  • Operator
  • Right source
  • Literal type
  • Right literal

Outcomes

  • Match
  • No Match

Data inputs

  • Leftany · Required
  • Rightany · Required when shownShown when Operator is one of >, <, >=, <=, ==, !=, crossAbove, crossBelow and Right source is dataPort

Data outputs

  • ResultYes or no

Related documentation

  • How a strategy starts and continuesUnderstand primary activation, control outcomes, and why data alone does not execute an action.
  • Build an RSI Momentum AlertCreate the Starter strategy, change its threshold, validate it, save it, and reopen it.
  • IndicatorCalculates a selected technical indicator from connected market data.

On this page

1 / 4
  1. When to use
  2. Example
  3. Common problems
  4. Next steps

Practical guidance for strategies, historical simulations and metric research in Screebits.

Responsible useGlossary