Question

Updating client information in SharpSpring duplicates entries instead of updating existing contacts from Salesforce.


Hello, I am trying to automate updating clients information in SharpSpring when it is added into Salesforce. I have gotten that to happen, but with my current Zap it creates a whole new entry into SharpSpring rather than just updating the email, for example. 

So when I update a client’s email in Salesforce, I want it to update the client’s email in SharpSpring. It does this with my current zap, but it just creates a duplicate person, same name, different email address. 

Is there any way to fix this? 


6 replies

Userlevel 7
Badge +14

Hi @badusu 

Good question.

We would need to see screenshots with how your Zap steps are configured to have more context.

 

 

 

Hi @badusu 

Good question.

We would need to see screenshots with how your Zap steps are configured to have more context.

 

 

 

Userlevel 7
Badge +14

@badusu 

If the email address is changing and that is what you are searching for in SharpSpring, then that is why a new contact is being created.

You would need to store the SS Lead ID back in Salesforce to search by in SS.

@badusu

If the email address is changing and that is what you are searching for in SharpSpring, then that is why a new contact is being created.

You would need to store the SS Lead ID back in Salesforce to search by in SS.

Thank you, Troy, can you clarify a little more? I am a bit confused how I can fix this issue of duplicate people being created in SS. The email updating works besides it just creates a duplicate entry with the updated email. Does that make sense? 

Userlevel 7
Badge +14

@badusu 

EXAMPLE

Salesforce record email X > SharpSpring lead has email X

Salesforce record changes from X to Y.

Zap runs from Salesforce to SharpSpring.

In the SS action it’s configured to create or update a lead based on the email address which is a required field.

If the email being used is now Y, then SS sees that as a new email, and therefore creates a new Lead.

 

So the ShareSpring API would likely have to be used to do the find/create + update logic.

Ideally, you’d save the original SS Lead ID back onto the Salesforce Person Record to then use in the Zap.

SharpSpring API: https://help.sharpspring.com/hc/en-us/articles/115001069228-Understanding-Lead-Gen-CRM-Open-API-Overview

App APIs can be used in Zaps with the Webhooks app: https://zapier.com/apps/webhook/help

If  you need help, consider hiring a Certified Zapier Expert: https://zapier.com/experts/automation-ace

 

Reply