Flow Editor node reference

Use the searchable catalog below to find nodes that can be added to a current Flow graph. Each node page pairs a practical example with facts generated from the product's current node definitions. If you are learning the editor, read nodes, ports and outcomes first.

Find a node

Search by visible name or filter by category, Tactical or Portfolio mode, and availability. A node can exist in the product but be unavailable in your current mode or plan. The catalog covers adding nodes; an older imported graph can contain an item intentionally absent from today's palette.

Choose by job

• Start an evaluation: Event Trigger in Tactical or Schedule Trigger in Portfolio. Safety Trigger is a bounded auxiliary guard, not another general primary.
• Supply a value: Data Source provides bars, Indicator calculates an indicator, and Bar Field extracts a value.
• Decide or wait: Condition compares data, Gate combines control arrivals, and Delay resumes an existing path later.
• Work with orders: Order submits a request, Await Order Event observes later events, and Cancel Orders requests cancellation.
• Build allocations: Universe, Weight Calculator, Portfolio Constraint and Rebalancer have distinct roles.
• Inspect state: Read Variable reads declared Flow state; Read Engine State reads supported engine values. Neither starts a control path.

Read a node page

Begin with When to use and the worked example. Then check generated facts for mode, tier, defaults, option availability, outcomes and data ports. The table describes possible configurations, not fields to fill simultaneously. A parameter marked required can be required only when its visibility condition is met; an option can be reserved or require a higher plan.

For example, Condition can use a literal right-hand value. Its Right data port is active only for a compatible operator with a data-port source. Match moves control while Result carries a Boolean value. Order exposes different price inputs for its configured type and source. After changing a selector in the Inspector, confirm the active ports on the canvas.

When a port is missing

Check the selected variant, mode and plan first. A hidden port often means a parameter supplies the value or the selected role does not expose it. For a rejected visible edge, use connections and data types. For a Quant Hub metric, QHM Metric Value describes the node shape; the picker decides which versions and values are actually available.

Debug nodes

Breakpoint, Assert and Log Snapshot support eligible recorded debug and replay workflows. They do not replace validation, risk branches or actual run results. Start with debug and replay to learn when their evidence is available.