Event Trigger
Starts a strategy from a supported market event.
Starts a strategy from a supported market event.
When to use
Use it when the strategy must respond to a bar close, quote tick, or trade tick for a configured symbol.
Example
Start a control path on each one-minute BTC/USD bar close, then send the connected bar data to a decision.
Follow two bar closes
Set the event to On Bar Close, choose supported BTCUSD and a one-minute timeframe, and connect On Event to Condition. Each eligible closed bar starts a new Tactical activation. If the first bar yields RSI 58 and the next yields 62, a Greater-than-60 Condition takes No Match for the first and Match for the second. The event is a start signal; the RSI number still comes from the separate Data Source and Indicator chain.
The Event output and event-specific Bar, Quote Tick or Trade Tick outputs carry data appropriate to the selected event. Timeframe settings apply to bar-close events and may not be active for tick events. Use the Inspector's active ports rather than assuming all payloads exist at once. Changing the event type changes when the graph starts and which event fields are meaningful. A new Data Source does not create another primary activation.
Custom Event is listed in the node options but reserved and disabled in the editor. Choose a supported market event instead.
Common problems
A Data Source does not replace this activation. If the graph never starts, confirm the event and the single primary activation.
Next steps
Review the generated Parameters, Outcomes, and Data Ports on this page, then open the related guides for the complete workflow.
Related documentation
- How a strategy starts and continuesUnderstand primary activation, control outcomes, and why data alone does not execute an action.
- Build Tactical strategiesDesign an event-driven graph with one primary trigger, explicit control branches, and typed market data.
- Build an RSI Momentum AlertCreate the Starter strategy, change its threshold, validate it, save it, and reopen it.