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
  • Join / Data Merge
  • 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. /Join / Data Merge
IntermediateLast verified Sep 30, 2026

Join / Data Merge

Converges control branches as a Join or combines compatible data inputs as a Data Merge.

On this page
  1. When to use
  2. Example
  3. Choose the right kind of merge
  4. Common problems
  5. Next steps

Converges control branches as a Join or combines compatible data inputs as a Data Merge.

When to use

Use Join when forward control branches must converge; use Data Merge when homogeneous data values need one combined output.

Example

Join two completed control branches before one Alert, or merge compatible data inputs for a downstream consumer.

Try it here

Explore Join / Data Merge

Converges control branches as a Join or combines compatible data inputs as a Data Merge.

Exercise steps
  1. Switch the role from Join to Data merge.
  2. Compare control arrivals with the data inputs and inspect validation.
Event TriggerJoin / Data Merge
Graph preview — a diagram of the example

Choose the right kind of merge

In Join role, bring two control branches into the node and continue from Merged after the configured join behavior. This answers “when may execution continue?” In Data Merge role, connect compatible data values to Inputs and consume the Merged Data collection. This answers “what values are grouped?” A Data Merge does not replace an Event Trigger, and a Join does not turn two unlike values into a single number. Choose Role before wiring ports, then inspect the active control and data connections because changing Role changes the meaning of the node.

Common problems

Choose the intended Role (Join or Data Merge) and connect homogeneous inputs. It cannot make incompatible types or graph cycles valid.

Next steps

Review the generated Parameters, Outcomes, and Data Ports on this page, then open the related guides for the complete workflow.

Node facts

These facts come from the current Flow Editor node catalog.

Node type
Join / Data Merge
Activation role
No activation role
Category
Flow
Availability
Tactical and Portfolio
Modes
Tactical and Portfolio
Required plan
None
Behavior
Makes a decision
Control inputs
4
Output data types
collection

Parameters

NameInput typeRequirementDefaultOptions and constraints
Merge typeSelection listRequiredjoinOptions: Join, Data Merge

Primary parameters

  • Merge type

Outcomes

  • MergedShown when Merge type is join

Data inputs

  • Inputsany · Required when shownShown when Merge type is dataMerge

Data outputs

  • Merged DatacollectionShown when Merge type is dataMerge

Related documentation

  • GateCombines control arrivals according to a configured pass rule.
  • Control and data connectionsUse control connections to continue execution and data connections to pass compatible values.
  • 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. When to use
  2. Example
  3. Choose the right kind of merge
  4. Common problems
  5. Next steps

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

Responsible useGlossary