Event Field

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.

Start lesson

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.