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 Field
  • 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 Field
IntermediateLast verified Sep 30, 2026

Event Field

Extracts one scalar value from an event payload.

On this page
  1. When to use
  2. Example
  3. Inspect one activation
  4. Common problems
  5. Next steps

Extracts one scalar value from an event payload.

When to use

Use it when Event Trigger provides a complete event but a downstream node needs only one available field.

Example

Extract a value from the triggering event and compare it with a threshold.

Try it here

Explore Event Field

Extracts one scalar value from an event payload.

Exercise steps
  1. Choose a different field in Inspector.
  2. Observe how the active output and its type change; the connected input keeps its structured value.
Event TriggerEvent Field
Graph preview — a diagram of the example

Inspect one activation

Connect Event Trigger: Event to Event Field and choose Symbol, Timestamp, or Event Kind. On an illustrative BTCUSD bar-close activation, Symbol identifies the instrument and Event Kind identifies the event family; Timestamp identifies when that event occurred. These are separate typed outputs, so connect the selected one to a consumer that accepts its type. Event Field extracts data from an existing event and cannot start a second activation. If a consumer needs a Bar or Tick payload, use the event-specific port or the relevant field extractor instead.

Common problems

The selected field must exist for the configured event. Review Data Ports after changing the event type.

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 Field
Activation role
No activation role
Category
Field
Availability
Tactical only
Modes
Tactical
Required plan
None
Behavior
Transforms a value
Control inputs
0
Output data types
Text, datetime

Parameters

NameInput typeRequirementDefaultOptions and constraints
Event fieldSelection listRequiredsymbolOptions: Symbol, Timestamp, Event kind

Primary parameters

  • Event field

Outcomes

None

Data inputs

  • Eventevent · Required

Data outputs

  • SymbolTextShown when Event field is symbol
  • TimestampdatetimeShown when Event field is timestamp
  • Event KindTextShown when Event field is eventKind

Related documentation

  • Nodes, parameters, outcomes, and portsRead the parts of a node and understand what to configure or connect.
  • Event TriggerStarts a strategy from a supported market event.
  • ConditionCompares values and selects Match or No Match.

On this page

1 / 5
  1. When to use
  2. Example
  3. Inspect one activation
  4. Common problems
  5. Next steps

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

Responsible useGlossary