Search blocks by description or jump to a page.
Source CRM fields on the left mapped to destination fields on the right, with transform badges, one unmapped row flagged, and a save footer.
The source for every Application block is included with Pro and Team. Start a plan to copy the code.
Already on a plan? Log in
Field Mapping Panel is the sync configuration view for a Salesforce to People integration: source fields on the left (First Name, Email, Account Name, Phone, Lead Source) each with a mono API path, an arrow across to a select style destination control on the right, transform badges where a value is reshaped (Lowercase, E.164 format), and one unmapped row (Lead Source) flagged with a note on what happens to dropped values. The footer carries Discard and Save mappings buttons and a line on when changes apply.
Mappings are one const array with sourceLabel, sourceApi, destination, transform, and mapped fields. The unmapped warning is the honest detail: rather than hide the gap it states that Lead Source values are dropped on every sync until mapped, so nothing goes missing without a word.
Reach for this block on an integration setup or edit page, wired to your field schema and mapping API. Show it after a user connects a source so they can confirm which fields flow through before the first sync runs.
A natural flow around it on an Application Pro page:
Before
After
One strong use is the CRM contact field mapping. Other mapping panels:
Tip: always name what happens to unmapped values; a dropped field that fails silently becomes a data quality ticket weeks later.