Skip to main content
Stores an org-wide mapping from an entity’s external id to a value — for example “source employee A123 exists in the target system as 99001”. Any flow in the org can read it back later with an Entity Mapping Lookup.

​
Configuration

  • Domain — the entity kind the mapping belongs to.
  • Namespace — optional label that keeps several independent mapping sets apart within one domain (e.g. target-id vs cost-centre). Leave blank if the domain only has one mapping set.
  • External ID — the mapping key, with {assign_key} interpolation (same syntax as Flow Log). Takes precedence over the assign below.
  • External ID assign — alternatively, name an assign whose raw value is the key.
  • Value — the value to store, with {assign_key} interpolation. Takes precedence over the assign below.
  • Value assign — alternatively, name an assign whose raw value is stored (e.g. the id returned by an upstream Flow Action).
  • Metadata assign — optional; an assign holding a flat map of scalars (build it with Build Map) stored alongside the value — breadcrumbs like the source row’s date, so reconciliation flows can filter mappings without refetching history. Capped at 2 KB; leave unset to keep any previously stored metadata untouched.

​
Tips

  • Last write wins — re-running the branch refreshes the stored value.
  • Place this node after the work that produces the value, and pair it with an Entity Mapping Lookup (same domain + namespace) wherever the mapping is consumed.
  • Blank domain, external ID, or value logs a warning and no-ops.

​
Ports