Skip to main content
Maps an input value against rows fetched live from a system integration’s metadata. Adding a new title or department in the source system propagates into the running flow without a re-edit.

Configuration

  • System integration — which integration’s metadata to read.
  • Source — which metadata catalogue (titles, departments, …). Source picker is filtered to the chosen integration’s system.
  • Pattern field / Value field — which canonical field of each record (value, code, readable_name, description) becomes the regex pattern, and which becomes the output value.
  • Caseless / Confined / Loose — same toggles as the static Mapping node’s paste dialog. Loose tolerates dashes, whitespace, dots, slashes, and ampersands.
  • Output type — the property type the output value is cast to.
  • On unmatched — what to do when an input doesn’t match any metadata row: emit a configured fallback value, or raise a generic Twine anomaly that surfaces in PropertyMapping reporting.
  • Nil handling — what to do when this node produces a nil value (anomaly-mode unmatch, or a fallback that casts to nil): include it, skip all such mapping-produced nils, or skip just the trailing (most-recent) ones. Upstream nils always pass through.

Ports