Key fields

The key field is how Boost.space decides whether incoming data is a new record or an update to an existing one. It powers data consolidation: records that share the same key value merge into one. Each space can have its own key field.

Key field vs. primary label. The key field matches records for merging. The primary label is what a record is titled by wherever it's shown — a separate setting on a field. A space can use different fields for each.

How it works

When data arrives — from an import, a scenario, or the API — Boost.space compares the key field:

• if a record with that key already exists, the incoming data updates it;
• if not, a new record is created.

This keeps one unified record per real-world entity instead of duplicates piling up on every sync.

Set a key field

Choose the key field when creating a space (in the space wizard), or later by editing the space.

Example

Set Email as the key field for a Companies space. When data arrives for jane@example.com:

• if that email already exists, its record is updated with the new data;
• if it doesn't, a new contact is created.

The result: no duplicates, one record per person — whether the data comes from a person, an import, or an automation. When several sources set the same field, API token prioritization decides which one wins.