Skip to main content
Reads a property stored on the organization — a value that is the same for every employee, schedule or time report you process — and emits its dated history. Organization properties are free-form: a flow writes whatever key it likes with an Organization Property Put, and you read it back here or edit it under Organization settings → Data → Organization Properties. Each key keeps a timeline, so a value that changed on 1 July still knows what it was in March.

​
Configuration

  • Property key — the key to read. In a flow it supports {assign_key} interpolation (same syntax as Flow Log) and takes precedence over the assign below.
  • Property key assign — alternatively, name an assign whose raw value is the key. Flows only.
  • Value type — the type the output should be treated as. Set it to match what’s stored so downstream nodes type-check.
  • Output assign — flows only: where the current value lands. Leave blank in a property mapping.

​
Optional inputs

  • At Date — wire a date (or list of dates) to keep only the values active at those points in time. Without it the whole timeline comes through.

​
Tips

  • In a property mapping, wire this straight into an Insert to map an org-level value onto every entity.
  • An unknown key is not an error — it emits an empty timeline, and in a flow writes nil to the output assign.

​
Ports