Fluxyn Docs
Guides

Expressions and Variables

Learn when to use $, $eventData, $input, and $consent inside Fluxyn nodes.

Expressions let you reference live values inside supported node fields.

They are intentionally limited. Normal expression fields are not arbitrary JavaScript.

The most important variables

$

$ is the merged page-state snapshot for the current execution step.

Use it when you want the latest known value, even if it came from an earlier event or a Set Properties node.

$eventData

$eventData is the raw current event only.

Use it when you need the exact payload that triggered the flow.

$input

$input is the output of the immediately previous node.

It is especially useful inside custom nodes, but it is not limited to them.

$outputs is an alias for the same value.

$consent is the latest consent snapshot known to Fluxyn.

Other supported values

You can also use:

  • $('Node Name') to read a previous node output by name
  • $window for browser globals when available
  • $id for the generated event id
  • $receivedAt for the event timestamp
  • $now for the current Date
  • $timestamp for Date.now()
  • env for the runtime environment marker

What expressions support

Supported patterns:

  • direct expressions like {{ $.orderId }}
  • interpolated strings like https://example.com?id={{ $.orderId }}
  • node output references like {{ $('HTTP').output.data }}
  • simple math with +, -, *, /
  • strings, numbers, booleans, null, and undefined

What expressions do not support

Normal expression fields do not support:

  • arbitrary JavaScript
  • ternaries
  • multiline statements
  • semicolons
  • general function calls

If you need real JavaScript, use Custom Function or Custom Script.

Rule of thumb

  • use $ for the current working state
  • use $eventData for the original triggering event
  • use $input for the previous node output
  • use $consent when logic depends on consent

On this page