Skip to main content
Property mapping controls which HubSpot Contact and Company properties FirstTouch can update.

​
Mapping Direction

FirstTouch field mappings write FirstTouch-held or enriched values into HubSpot properties. Mapping a field does not import arbitrary HubSpot values into FirstTouch variables. When HubSpot is connected and the Flow Plan’s CRM integration is enabled, supported mapped values write back to matched HubSpot records automatically. This includes standard fields such as a contact’s LinkedIn URL. A separate CRM Enrichment step is not required for these updates. Use that step only to copy a value into a specific custom HubSpot property. See CRM Enrichment.

​
Contact And Company Mappings

HubSpot Variables are separate from FirstTouch Variables saved on a Flow Enrollment. Mapping a property does not automatically copy its value into a FirstTouch variable. The HubSpot settings page can include:
  • Contact field mapping
  • Company field mapping
  • locked identity rows used for matching and required updates
  • editable rows for optional enrichment fields
  • LinkedIn CRM State Rollups: message and reply counts and dates, Connection Requests, accepted connections, and first/latest LinkedIn Connection User

​
Locked Rows

The following identity mappings are locked to their standard HubSpot properties because FirstTouch relies on them for matching and required updates:
  • Contact: email, first name, last name, phone, and LinkedIn URL
  • Company: name, domain, and LinkedIn company page

​
Overwrite Behavior

Changing a mapping chooses the destination property; it does not add a per-mapping overwrite setting. Normal mapped updates follow a fixed server-side overwrite policy. A Flow Plan CRM action can separately copy FirstTouch properties to CRM properties and expose an overwrite choice for that action. That choice applies only to the property-copy action. It does not change the server policy for normal mapped updates, and the action does not create or enrich a CRM record.

​
Primary Company Association

Some Contact-based HubSpot operations use the Contact’s Primary Company Association when they need one Company context. This is not a universal rule for every integration path; operations that already carry a specific HubSpot Company ID use that supplied context.

​
Troubleshooting

If a property did not update, check:
  • HubSpot connection status
  • Contact or Company matching
  • field mapping
  • locked or disabled mapping state
  • the fixed server overwrite policy, or the CRM property-copy action’s overwrite choice when that action performed the write
  • HubSpot property permissions
  • whether the value exists in FirstTouch