Salesforce sync field mapping documentation

Question

I'm looking for comprehensive documentation on the FieldPulse-Salesforce integration field mappings, specifically: 
 
 The canonical mapping of FieldPulse work order fields to Salesforce objects (Opportunity, Case, or custom object). 
 Data type mappings and any transformation logic applied (e.g., timestamp formats, enum values). 
 Bidirectional vs. unidirectional field synchronization — i.e., which fields are master in each system. 
 Conflict resolution behavior when the same record is modified in both systems within the sync window. 
 Failure modes and rollback semantics for partial sync failures. 
 
 The existing Connecting FieldPulse to Salesforce article covers initial setup but lacks the technical depth needed for implementation verification. I.e., I need to validate our data governance policies against the actual field-level mapping specification. 
 Is there an RFC or technical specification document available? Alternatively, can someone confirm whether the webhook payload structure at qa-063 reflects the field naming conventions used in the Salesforce mapping layer?

Priya Nair (Staff) · Accepted Answer

Hi Omar, 
 Great question — happy to help clarify the official mapping behavior. 
 Standard Field Mapping 
 The FieldPulse-to-Salesforce integration maps as follows: 
 
 FieldPulse Object.Field Salesforce Object.Field Direction 
 WorkOrder.id Opportunity.FieldPulse_ID__c FP → SF 
 WorkOrder.status Opportunity.StageName FP → SF 
 WorkOrder.customer.id Account.FieldPulse_Customer_ID__c FP → SF 
 WorkOrder.customer.name Account.Name FP → SF 
 WorkOrder.location.address Opportunity.FieldPulse_Location__c FP → SF 
 WorkOrder.description Opportunity.Description FP → SF 
 WorkOrder.scheduled_start Opportunity.CloseDate FP → SF 
 WorkOrder.total_value Opportunity.Amount FP → SF 
 WorkOrder.assigned_to.name Opportunity.FieldPulse_Technician__c FP → SF 
 
 Custom Fields 
 Custom fields defined in Settings → Custom Fields with the "Sync to Salesforce" option enabled map to FieldPulse_cf_[sanitized_field_name] on the Opportunity object. Sanitization removes spaces and special characters. 
 Conflict Resolution 
 FieldPulse is the system of record for all mapped fields. Updates in Salesforce are overwritten on next sync unless you enable Settings → Integrations → Salesforce → Allow Reverse Sync for Custom Fields . This applies to custom fields only. 
 Documentation 
 I've generated a signed specification document for your account: check your email for a link valid 72 hours. For implementation details, see Connecting FieldPulse to Salesforce and Salesforce Integration Not Updating Opportunity Status for troubleshooting. 
 Let me know if you need the webhook-to-SF mapping correlation clarified.

Carlos Vega · Answer

Not official docs, but here's what I've observed from packet capture: 
 FieldPulse WorkOrder -> Salesforce Opportunity
- work_order.id -> Opportunity.FieldPulse_ID__c (external ID)
- status -> Opportunity.StageName (mapped: 'Scheduled'->'Prospecting', 'In Progress'->'Qualification', 'Completed'->'Closed Won', 'Cancelled'->'Closed Lost')
- customer.name -> Opportunity.AccountId (lookup/upsert)
- address.full -> Opportunity.FieldPulse_Location__c
- description -> Opportunity.Description
- scheduled_start -> Opportunity.CloseDate (closest business day)
- estimated_value -> Opportunity.Amount 
 Custom fields prefixed with cf_ in FP map to FieldPulse_cf_<field_name> in SF. 
 Can you share what you see in your webhook payloads? Want to confirm if the field naming is consistent.

Eli Torres (Staff) · Answer

yeah this one tripped me up too when I first looked at it — the official docs are... let's say optimistically scoped 
 what carlos posted matches what I've seen, but there's a gotcha with datetime fields. FieldPulse sends ISO 8601 with timezone (e.g., 2025-11-28T09:30:00-05:00 ) but the Salesforce API expects either UTC or the user's configured timezone depending on how you auth. if you're using a connected app with a service user, check that user's timezone setting because it'll eat the time portion silently and you'll wonder why everything's showing up at midnight 
 also worth noting: the sync is effectively push-from-FP, pull-to-SF for standard fields. bidirectional on custom fields only works if you enable the "allow Salesforce to update FieldPulse" toggle in settings, which last I checked was labeled "Enable Reverse Sync" — but that's a UI label, not the actual config key, so your API calls to verify might not match 
 if you want the actual mapping spec, I'd open a ticket and ask for the integration's OpenAPI schema. they don't publish it but support can generate a signed URL that's valid for 72 hours. learned that the hard way