Connect nodes

Start from the source handle that represents the outcome or value you want to use.

Goal: wire the five-node RSI alert so a new bar can reach Condition and the RSI value can be compared with 60. You need an editable Tactical strategy containing Event Trigger, Data Source, Indicator, Condition, and Alert. The RSI starter already contains these nodes; duplicate it before experimenting with broken connections.

Create a control connection

1. Identify the source outcome, such as Match or Submitted.
2. Drag from that control handle to the target node’s control input.
3. Release only when the target is shown as compatible.
4. Select the connection and confirm its source outcome.

A control connection determines what can run next.

For the example, connect Event Trigger.On Event → Condition and Condition.Match → Alert. Do not connect Data Source to Condition's control input: Data Source provides data and has no control outcome. The unused No Match branch simply ends this path when the comparison is false.

Try it here

Complete the control path

Connect the Match outcome to the Alert control input.

Exercise steps

1. Connect Condition.Match to the Alert control input.
2. Observe the completed control path. The data connections remain unchanged.

Start lesson

Create a data connection

1. Identify the typed data output.
2. Drag it to a compatible input on another node.
3. If no target is offered, check the active port and data type.
4. Open Data Ports on both nodes to verify the relationship.

A data connection supplies a value and does not execute its target.

Complete Data Source.Bars → Indicator.Bars → Condition.Left. Set Condition's operator to >, its Right source to Literal, and its literal value to 60. The Right port disappears in this configuration because the value is stored in the node. If you select a data-port source instead, Right becomes an active required input and needs another compatible value.

Insert and verify

Dropping a suitable node on an existing connection can insert it when both resulting relationships are valid. Review both new edges. The graph rejects cycles and incompatible types, but validation can still reveal missing required paths or values.

Open Validation and follow any blocking issue to its node or port. For the five-node alert, inspect both paths from their sources; a valid data chain alone is insufficient. Save and wait for confirmation, then reopen the strategy to verify the edges remained. If a target handle is missing, inspect the node's current parameters and mode before searching for another node. If an edge is rejected, correct its type rather than converting a control path into a data path. Connection troubleshooting covers the remaining cases.