Home → Integrations → Data mapping
Integrations · Mapping
Route /integrations/mapping Flag mappingEnabled

Data Mapping

Field contracts from vendor payloads onto Employee, Project, PurchaseOrder, Task, and time — the map is not the data.

Scroll to Flowcharts. Scenario: Map vendor fields onto canonical entities.

Contracts

Vendor field in, canonical field out

Data mapping is the contract between a payload and Employee, Project, purchase contract, Task, or time. The map is not a spreadsheet of customers.

Integrations → Data mapping Route /integrations/mapping Org flag mappingEnabled Integration admin

The job of this console

Edit the profile, save, test one payload, open the product row. If the row is wrong, fix the map or the vendor — not a shadow table.

Seat at the table

Integration admins with mappingEnabled.

The working rhythm

Map, test, monitor, revise when the vendor schema changes.

Moments that bring you here

First install. A new required field. Duplicate projects from a bad id. Payroll export column change.

ⓘ
Map ≠ data
Application Config is flags. This page is field contracts. No isolated mapping warehouse of business truth.

Flowcharts

1 — Map then prove a row

Edit the profile, test, open the entity in product.

flowchart TD
  A[Open Data mapping] --> B[Select profile]
  B --> C[Map fields]
  C --> D[Save]
  D --> E[Test sync]
  E --> F[Open canonical row]
  1. 1
    OpenIntegrations → Data mapping.
  2. 2
    ProfilePer connector.
  3. 3
    MapOnto canonical fields.
  4. 4
    ProveA real row in product.

Overview

Mapping profiles are contracts. They must target existing entities. Do not design a map that creates an isolated table. Sensitive fields follow persona masking on read-back and AI.

How to use

1. Stable external id
Required for idempotent import.
2. Leave types
Must align with leave policies, not invent balances.
3. Timesheet export scope
Least privilege org/project.

Related pages

Connector adaptersRuntime. ConnectionsInstances. Application ConfigOrg flags, not maps.