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 guides
  4. /Configure a node
BeginnerLast verified Sep 30, 2026

Configure a node

Edit required and optional parameters, then review any ports or connections affected by the change.

First strategy · Step 7 of 10

On this page
  1. Open the configuration
  2. Complete the parameters
  3. Work through a conditional parameter
  4. Review the graph

A node’s parameters determine what it reads, calculates, decides, or does.

Open the configuration

Select the node, then open Parameters in the Inspector. You can also use the configure action from the node or command palette when it is available.

Complete the parameters

  1. Read the parameter help before choosing a value you do not recognize.
  2. Complete every required field.
  3. Choose a literal or connected value source where the node supports both.
  4. Apply an edit when the control requires confirmation.

Some fields appear only after another choice. For example, an indicator type can reveal its own period settings.

Work through a conditional parameter

Open Condition in the RSI Starter. Its Left value comes from the Indicator output; set the operator to Greater than and Right source to Literal. The Right literal field is then available: set it to 60. With RSI 58, the comparison follows No Match; with RSI 62, it follows Match. This is a strict comparison, so 60 itself does not match.

If you change Right source to a data port, the literal field is no longer the active right input. Connect a compatible numeric output to Right instead. Return to Literal if you intend to compare against a fixed number. The Inspector and the Condition reference show which inputs exist for the current setting; do not rely on a connection that was valid before you changed the source.

Different nodes use the same pattern. Choosing an Indicator type can reveal type-specific settings, while a Portfolio method can constrain which options are authorable. A value listed as reserved or unavailable in source specifications is not an option to enter manually.

Try it here

Inspect the signal

Edit required and optional parameters, then review any ports or connections affected by the change.

Exercise steps
  1. Switch Right source from Literal to Data port.
  2. Inspect the newly required Right input, then return to Literal to resolve it.
Event TriggerData SourceIndicatorConditionAlert
Graph preview — a diagram of the example

Review the graph

A parameter change can add, remove, or change active data ports. Open Data Ports and inspect existing connections. Then open validation and resolve any new issue.

Check the result in three places: the node now displays the intended setting, the connection still terminates at an active compatible port, and the validation area has no new blocking issue. Save only after you have reviewed those consequences. Saving a changed parameter does not prove the graph is ready to simulate.

You cannot edit a node during historical preview or full replay. Return to the current editable version first.

Related documentation

  • Use the InspectorConfigure the current selection and understand its parameters, outcomes, data ports, and quick actions.
  • Nodes, parameters, outcomes, and portsRead the parts of a node and understand what to configure or connect.
  • Fix validation issuesUse the validation area to locate a blocking problem, correct it, and confirm that it is resolved.
PreviousNodes, parameters, outcomes, and portsNextFix validation issues

On this page

1 / 4
  1. Open the configuration
  2. Complete the parameters
  3. Work through a conditional parameter
  4. Review the graph

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

Responsible useGlossary