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
  • 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
All levelsLast verified Sep 30, 2026

Flow Editor node reference

Browse every node currently available to add, with generated facts and practical guidance.

On this page
  1. Find a node
  2. Choose by job
  3. Read a node page
  4. When a port is missing
  5. Debug nodes

Use the searchable catalog below to find nodes that can be added to a current Flow graph. Each node page pairs a practical example with facts generated from the product's current node definitions. If you are learning the editor, read nodes, ports and outcomes first.

Find a node

Search by visible name or filter by category, Tactical or Portfolio mode, and availability. A node can exist in the product but be unavailable in your current mode or plan. The catalog covers adding nodes; an older imported graph can contain an item intentionally absent from today's palette.

Choose by job

  • Start an evaluation: Event Trigger in Tactical or Schedule Trigger in Portfolio. Safety Trigger is a bounded auxiliary guard, not another general primary.
  • Supply a value: Data Source provides bars, Indicator calculates an indicator, and Bar Field extracts a value.
  • Decide or wait: Condition compares data, Gate combines control arrivals, and Delay resumes an existing path later.
  • Work with orders: Order submits a request, Await Order Event observes later events, and Cancel Orders requests cancellation.
  • Build allocations: Universe, Weight Calculator, Portfolio Constraint and Rebalancer have distinct roles.
  • Inspect state: Read Variable reads declared Flow state; Read Engine State reads supported engine values. Neither starts a control path.

Read a node page

Begin with When to use and the worked example. Then check generated facts for mode, tier, defaults, option availability, outcomes and data ports. The table describes possible configurations, not fields to fill simultaneously. A parameter marked required can be required only when its visibility condition is met; an option can be reserved or require a higher plan.

For example, Condition can use a literal right-hand value. Its Right data port is active only for a compatible operator with a data-port source. Match moves control while Result carries a Boolean value. Order exposes different price inputs for its configured type and source. After changing a selector in the Inspector, confirm the active ports on the canvas.

When a port is missing

Check the selected variant, mode and plan first. A hidden port often means a parameter supplies the value or the selected role does not expose it. For a rejected visible edge, use connections and data types. For a Quant Hub metric, QHM Metric Value describes the node shape; the picker decides which versions and values are actually available.

Debug nodes

Breakpoint, Assert and Log Snapshot support eligible recorded debug and replay workflows. They do not replace validation, risk branches or actual run results. Start with debug and replay to learn when their evidence is available.

Available nodes

47 nodes

  • AlertAction·Tactical, Portfolio·Tactical and Portfolio
  • Await Order EventOrder·Tactical·Tactical only
  • Bar FieldField·Tactical·Tactical only
  • Cancel OrdersAction·Tactical·Tactical only
  • Cancel Result FieldField·Tactical·Tactical only
  • CommentMeta·Tactical, Portfolio·Tactical and Portfolio
  • Composite ScorePortfolio·Portfolio·Portfolio only
  • ConditionCondition·Tactical, Portfolio·Tactical and Portfolio
  • Data SourceData·Tactical·Tactical only
  • DelayAction·Tactical, Portfolio·Tactical and Portfolio
  • Event FieldField·Tactical·Tactical only
  • Event TriggerTrigger·Tactical·Tactical only
  • ExpressionData·Tactical, Portfolio·Tactical and Portfolio
  • GateCondition·Tactical, Portfolio·Tactical and Portfolio
  • HaltFlow·Tactical, Portfolio·Tactical and Portfolio
  • IndicatorData·Tactical·Tactical only
  • Join / Data MergeFlow·Tactical, Portfolio·Tactical and Portfolio
  • Leverage ConstraintPortfolio·Portfolio·Portfolio only·Pro
  • Leverage Metrics FieldField·Portfolio·Portfolio only
  • Leverage MonitorTrigger·Tactical·Tactical only·Pro
  • Margin CheckAction·Tactical·Tactical only·Pro
  • Margin Estimate FieldField·Tactical·Tactical only
  • Margin State FieldField·Tactical·Tactical only
  • OrderOrder·Tactical·Tactical only
  • Order Result FieldField·Tactical·Tactical only
  • Order Ticket FieldField·Tactical·Tactical only
  • Period FieldField·Portfolio·Portfolio only
  • Portfolio ConstraintPortfolio·Portfolio·Portfolio only
  • Position MonitorAction·Tactical·Tactical only
  • Position SizerAction·Tactical·Tactical only
  • QHM Metric ValueData·Tactical, Portfolio·Multiple modes
  • RankingPortfolio·Portfolio·Portfolio only
  • Read Engine StateData·Tactical, Portfolio·Tactical and Portfolio
  • Read VariableData·Tactical, Portfolio·Tactical and Portfolio
  • Rebalance Result FieldField·Portfolio·Portfolio only
  • RebalancerPortfolio·Portfolio·Portfolio only
  • Safety TriggerTrigger·Portfolio·Portfolio only
  • Schedule TriggerTrigger·Portfolio·Portfolio only
  • Screen FilterPortfolio·Portfolio·Portfolio only
  • Set VariableAction·Tactical, Portfolio·Tactical and Portfolio
  • String TemplateData·Tactical, Portfolio·Tactical and Portfolio
  • Tick FieldField·Tactical·Tactical only
  • UniversePortfolio·Portfolio·Portfolio only
  • Weight CalculatorPortfolio·Portfolio·Portfolio only

Debug nodes

  • AssertMeta·Tactical, Portfolio·Tactical and Portfolio
  • BreakpointMeta·Tactical, Portfolio·Tactical and Portfolio
  • Log SnapshotMeta·Tactical, Portfolio·Tactical and Portfolio

Related documentation

  • Nodes, parameters, outcomes, and portsRead the parts of a node and understand what to configure or connect.
  • Add, move, duplicate, and remove nodesUse the palette and canvas to organize the graph without losing the meaning of its paths.
  • Troubleshoot connections and data typesRecover when a target is unavailable, a connection is rejected, or a node has data but does not run.

On this page

1 / 5
  1. Find a node
  2. Choose by job
  3. Read a node page
  4. When a port is missing
  5. Debug nodes

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

Responsible useGlossary