Skip to main content
Writes a single resolved value into an assign. Think of it as the small cousin of Flow Compose: Compose builds a whole struct; Assign pulls out or computes one value and names it. Good for staging a scalar you want to reuse in several downstream nodes, or for renaming an assign so a step can find it under a different key.

​
Configuration

  • Output assign — the name to write under.
  • Nested path — optional. A dot-separated path inside the target assign (e.g. address.city). When set, the value is written into a nested map, creating intermediate maps if needed. Leave empty for a plain top-level write. This is also how you set one field on a struct a Flow Compose built earlier: point Output assign at the composed assign and give the field name as the path (e.g. city). The segment must be a real field on that struct — a typo is an error naming the struct, not a silently ignored write. Writing into a nested struct field works the same way (email_information.email_address_to) as long as that field already holds a struct; if it is still nil, compose it first.
  • Source — where the value comes from. Same vocabulary as Flow Compose:
    • Assign — copy the raw value of another assign.
    • Extract — traverse into a map/struct at a path (get_in-style).
    • Dated property — read a dated property through its canonical facade (supports an optional as-of date).
    • Literal — a fixed value of a type you pick: text, number, boolean, date, date range, empty list or empty map. A date range takes two bounds, either of which may be left blank to leave that end open; leave both blank and the spec resolves to nothing.

​
Tips

  • The Settings pane lets you control which assigns are snapshotted to the run record — untick short-lived staging assigns to keep the flow_runs table small.

​
Ports