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
  • Event Trigger
  • 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. /Event Trigger
IntermediateLast verified Sep 30, 2026

Event Trigger

Starts a strategy from a supported market event.

On this page
  1. When to use
  2. Example
  3. Follow two bar closes
  4. Common problems
  5. Next steps

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.

Try it here

Explore Event Trigger

Starts a strategy from a supported market event.

Exercise steps
  1. Switch the event type from Bar close to Quote tick.
  2. Observe how Bar is replaced by Quote Tick in the data outputs.
Event Trigger
Graph preview — a diagram of the example

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.

Node facts

These facts come from the current Flow Editor node catalog.

Node type
Event Trigger
Activation role
Primary activation
Category
Trigger
Availability
Tactical only
Modes
Tactical
Required plan
None
Behavior
Trigger
Control inputs
0
Output data types
event, Text, bar, quote Tick, trade Tick

Parameters

NameInput typeRequirementDefaultOptions and constraints
Event typeSelection listRequiredonBarCloseOptions: Bar close, Quote tick, Trade tick
SymbolTextRequiredNot setNone
Timeframe amountNumberRequired when shown1Minimum: 1; Whole numbers only; Maximum depends on Timeframe unit; Shown when Event type is onBarClose
Timeframe unitSelection listRequired when showndOptions: Minutes, Hours, Days, Weeks, Months; Shown when Event type is onBarClose

Primary parameters

  • Event type
  • Symbol
  • Timeframe amount
  • Timeframe unit

Outcomes

  • On Event

Data inputs

None

Data outputs

  • EventeventShown when Event type is one of onBarClose, onQuoteTick, onTradeTick
  • SymbolTextShown when Event type is one of onBarClose, onQuoteTick, onTradeTick
  • BarbarShown when Event type is onBarClose
  • Quote Tickquote TickShown when Event type is onQuoteTick
  • Trade Ticktrade TickShown when Event type is onTradeTick

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.

On this page

1 / 5
  1. When to use
  2. Example
  3. Follow two bar closes
  4. Common problems
  5. Next steps

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

Responsible useGlossary