A
Ayodeji Adeoti
Allow ingestion mappings to evaluate an entity’s existing Port properties and apply conditional logic before updating a mapped property.
Today, mappings can transform incoming data, but the mapping does not appear to have access to the entity’s current state. This makes it difficult to control whether a value should overwrite, append to, or leave an existing property unchanged based on what is already stored on the entity.
The mapping context should expose existing entity property values—similar to the
before
/
after
context available in workflows—and support conditional expressions (for example, through JQ). Based on the condition, users should be able to return a mapped value, append a value, preserve the current value, or skip the update.
PRACTICAL USE CASE
An entity has an
owners
array that can be populated by multiple integrations.
  • Integration A has already added
    "A"
    to
    owners
    .
  • Integration B ingests related owner data.
  • During Integration B’s mapping, check whether
    owners
    already contains
    "A"
    .
  • If it does, skip the update from Integration B.
  • If it does not, map or append Integration B’s incoming owner value.
This would prevent unwanted updates and let users define precedence or conflict-handling rules directly in ingestion mappings.