Hi @Ruqaiyah Giletwala ,

You can use OOTB connector job-’lead sync job’ to sync leads created in GS with SFDC. This is the job where you map fields.

Also in lead admin , you need to select -Sync with salesforce.

If you still have questions, feel free to connect with me over mail    -rjindal@gainsight.com

cc @MayurGhiya 

@Ruqaiyah Giletwala - did you successfully sync with Salesforce? I have tried syncing to both Leads and Opportunities and in both cases ran into obstacles.  This may be because of how we have SFDC configured (rules, hubspot, CPQ), but i’m hoping someone has cracked the code on this.  

Thanks, 

Amy

We’re in the middle of deploying CSQLs to Salesforce as leads just now.

how the CSQLs generated in Gainsight can be synced back to Salesforce and map to correct fields?

As far as I can tell there is currently no ability in Gainsight to set custom field mapping, only what GS has OOTB.  For example, the description field in GS will map to Lead.Description.

I have tried syncing to both Leads and Opportunities and in both cases ran into obstacles.  This may be because of how we have SFDC configured (rules, hubspot, CPQ), but i’m hoping someone has cracked the code on this.

We found the errors in our initial test sync were due to permission errors of the user GS is attempting to use to sync the CSQL to SFDC with.  For ease of troubleshooting, I’d select sync with the Integration User, then ensure in SFDC that an appropriate permission set is applied to the integration user allowing read/write access to all of the fields the lead is trying to write to (this includes the Lead Source); a good way of checking what fields are contained in the CSQL is to create a CSQL with chrome dev tools open, under the network tab select the record named leads and check the payload - this shows what GS is sending from your browser back to the GS API.  If successful, the API call should have a Status Code = 200 in the headers section.