Salesforce Integration: Field Mapping, Record Updates, and Reply Classifications
Last updated: April 27, 2026
Unify's Salesforce integration provides powerful capabilities for syncing prospect data and tracking engagement. This article covers field mapping behavior, record updates, and how to leverage reply classifications for advanced automation.
Reply Classifications
When a sequence enrollment reaches 'Completed: Replied' status, Unify provides detailed reply classifications to help categorize prospect responses:
Positive
Willing to meet
Needs more info
Bad Timing
Has solution
Neutral
Left Job
Updated contact info
Referral
Negative
NSFW
Opt out
OOO
Soft Bounce
Hard Bounce
Automated
Field Mapping Behavior
Existing Records
When syncing data to existing Salesforce records, Unify follows specific rules:
Integration fields: Unify will only write to mapped fields if they are currently blank - existing values will not be overwritten. This applies to both standard field mappings and enriched data (such as phone numbers enriched in Plays).
Unify-specific fields: Fields like "Most Recent Play" will automatically update for existing contacts
Overwrite settings: There is currently no field-specific overwrite setting - the behavior applies globally
New Records
For new Salesforce records created through Unify:
All mapped fields will auto-populate if Unify has values available
Standard fields typically include email, first name, last name, title, and LinkedIn URL
Custom Field Configuration
Custom fields require additional setup:
Set default values in either the Salesforce integration settings under "Default Values" or in individual Sync to Salesforce nodes
Unify cannot automatically infer values for custom fields like Lead Source
Configure additional field writebacks in Salesforce settings or directly in Sync to Salesforce nodes
Advanced Mapping with Play Logic
For complex scenarios where multiple Unify status and classification combinations need to map to single Salesforce values, use Play logic with 'Sync to Salesforce' actions instead of direct field mapping.
Example Configuration
Set up conditional logic branches such as:
Completed: Replied + Willing to meet → Salesforce Status = "Replied"
Completed: Replied + Bad Timing → Salesforce Status = "Nurturing"
Enrollment (Queued/Engaged) → Salesforce Status = "Contacted"
Auto-Updates on Enrollment
To automatically update Salesforce when prospects are enrolled in sequences:
Add a 'Sync to Salesforce' action at the enrollment stage
Set the target Salesforce Status to "Contacted" or your preferred value
Setup Instructions
Map 'Unify Most Recent Sequence Status' to a Salesforce field (custom field recommended)
Enable write permissions for the mapped field
Create Play branches based on status and reply classification combinations
Configure each branch to write the appropriate canonical Salesforce Status value
For custom fields like Lead Source, set default values in either:
Salesforce integration settings under "Default Values", or
Individual Sync to Salesforce node advanced settings
This approach provides maximum flexibility for mapping complex engagement scenarios to your Salesforce workflow while maintaining data integrity.