Flow Editor documentation

Flow Editor is the workspace for designing a strategy as a graph of nodes and connections. A node can start an evaluation, provide data, decide or act. A control connection answers what can run next; a data connection answers which value is needed. Drawing a graph, saving it and running a Backtest are different steps. Keep these articles open while you work.

Start here

1. Read Getting started to locate the canvas, palette, Inspector, validation and save state. Choose Tactical for supported market events or Portfolio for scheduled allocation; the mode stays fixed after creation.
2. Follow Build an RSI Momentum Alert. You will create a Starter copy, identify five nodes, change a threshold, validate, save and confirm the saved result after reopening.
3. Use Create a strategy when you want a different available Starter or a blank graph.

The RSI exercise needs no trading experience. A bar summarizes market data over one interval; RSI is a numerical indicator calculated from bars. The glossary explains those and the editor terms as you encounter them.

Choose a route

Complete a task

The guides follow actions in the editor. For a typical change, configure a node, connect its active ports, fix validation issues, then save and verify the result. Before experimenting, create a checkpoint. Reset flow has its own backup and recovery procedure.

A saved strategy is not automatically tested. Run a Backtest from a ready graph, then inspect runs and results in Backtest Center.

Understand the model

Start with nodes, parameters, outcomes and ports. In the RSI example, Event Trigger reaches Condition through control, while Indicator supplies the RSI number to Condition through data. Condition.Match can reach Alert; its Boolean Result is a different, data output. Canvas position alone sets no execution order. The concepts explain modes, activations, validation, versions and availability; the examples show how the rules combine.

Browse and troubleshoot

Search the node reference when an Inspector field or port is unclear. A reference lists possible configurations; a conditional field or port appears only when its setting makes it active. If a connection fails, an action is locked or a run lacks the expected event, choose the matching symptom in Troubleshooting.

Backtests are simulations under their data and cost assumptions. Read Backtests and responsible use before interpreting results as evidence about a strategy.