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. /Get started with the Flow Editor
BeginnerLast verified Sep 30, 2026

Get started with the Flow Editor

Understand strategy modes, workspace areas, validation, and the save lifecycle before building.

First strategy · Step 3 of 10

On this page
  1. Prerequisites
  2. Before you create a strategy
  3. Create from a starting point
  4. Know the workspace
    1. Read one graph from left to right
  5. Save and verify
  6. Next step

Use the Flow Editor to arrange strategy logic as nodes connected on a canvas. This page explains the decisions and workspace areas you will meet first.

Prerequisites

You can read these docs without an account. To follow the product steps, sign in to a Screebits account with Flow Editor access and permission to create or edit a strategy. Modes, starting points, and nodes can vary by plan and account availability.

Before you create a strategy

Choose the mode carefully:

  • Tactical strategies respond to market events and can evaluate signals, submit orders, monitor positions, or send alerts.
  • Portfolio strategies run primarily on a schedule, can include a bounded auxiliary safety guard, and work with universes, rankings, weights, constraints, and rebalancing.

The mode cannot be changed after creation. If you choose the wrong mode, create another strategy in the correct mode.

Availability can depend on your plan. A locked choice is not a validation error.

Create from a starting point

From Strategies → New strategy, choose a mode and name. Description and tags are optional. For a prepared copy, open Blueprints, inspect a template and choose Use Blueprint: the form inherits its mode and release. The graph is editable; author explanations are optional. Creation guide.

Know the workspace

  • The toolbar contains Save strategy, Save checkpoint, Undo, Redo, Auto-layout, Preferences, editor commands, and Backtest actions when available.
  • The palette lists nodes you can add in the current mode.
  • The canvas holds nodes and control or data connections.
  • The Inspector configures the selection and shows Parameters, Outcomes, and Data Ports.
  • The validation area reports problems that prevent a ready graph.
  • Variables is available from its workspace control. Open Preferences, then choose Settings, for strategy settings.

On compact screens, workspace panels open over the canvas and only one panel stays open at a time.

Try it here

Read the graph

Explore the two paths in the RSI example: control and data.

Exercise steps
  1. Follow Event Trigger → Condition → Alert to identify the control path.
  2. Follow Data Source → Indicator → Condition for data. Select a node to inspect its properties.
Event TriggerData SourceIndicatorConditionAlert
Graph preview — a diagram of the example

Read one graph from left to right

The RSI Blueprint gives you a concrete way to read the canvas. Event Trigger → Condition → Alert is the control route: a closed bar starts an evaluation, Condition chooses Match or No Match, and Alert runs only from the connected Match outcome. Data Source → Indicator → Condition is a separate data route: bars feed RSI(14), and its numeric value fills Condition's Left input. A data connection does not activate a node by itself.

SelectLook for in the InspectorWhat it tells you
Event TriggerMarket event, symbol and timeframeWhen a new evaluation begins.
IndicatorRSI, period 14, Close input and output portWhich value is computed from the bars.
ConditionGreater-than, Right source: Literal, right literal 55Which comparison controls Match; changing 55 to 60 changes the rule.
AlertMessage source and Match connectionWhat the simulation records when the rule matches.

This Blueprint has no Order node. A matching alert is therefore not a trade, and saving the graph does not start it. Follow the complete five-node exercise before adding your own branch.

Save and verify

Changes become dirty before they are stored. You can choose Save strategy or press Ctrl+S on Windows and Linux or Command+S on macOS. Autosave also runs while editing. Offline, error, and conflict states need your attention.

After saving, return to the strategy list and reopen the strategy to confirm that your latest graph is available.

If the toolbar shows offline, error, or conflict, the latest local edit is not yet a confirmed saved version. Keep the editor open and follow save and conflict recovery. A green validation result and a saved version answer different questions: validation checks the graph, while save confirms persistence.

Next step

Build the RSI Momentum Alert to practice both control and data connections.

Related documentation

  • Create a strategyCreate from scratch or from a Blueprint using one contextual form.
  • Build an RSI Momentum AlertCreate the Starter strategy, change its threshold, validate it, save it, and reopen it.
  • Tactical and Portfolio strategiesChoose the strategy mode that matches the decisions your graph needs to make.
PreviousYour first steps in ScreebitsNextBuild an RSI Momentum Alert

On this page

1 / 7
  1. Prerequisites
  2. Before you create a strategy
  3. Create from a starting point
  4. Know the workspace
    1. Read one graph from left to right
  5. Save and verify
  6. Next step

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

Responsible useGlossary