Skipping the Lead Object?

Hey @ranmichael,

I hope all is well, below are some replies:

1. Can we skip the Lead creation – and create Contacts instead?

> Yes, Just select the proper object.

(the information posted checks if there is a Contact with this email – and updates it if so, or creates a new Contact if email not found on Contacts?

> Yes, we have a feature which will check for the primary key.

2. What would be the correct way to set this up? Any documentation?

> Yes, You can set this up using the Primary Key.

3. Assuming #1 is possible, the idea is to use a specific Contact Type to indicate those came from the Gravity form.

> Sure, you can pull any object you want from Salesforce.

how would we set the Contact Type? e.g. Contact Type = Gravity

Is that just a hidden field to post with the form?

> You need to pull the objects from Salesforce.

> You can create rules based on hidden fields if you would like.

-Sam

Thank you for your answer, Sam.

The only thing that worries me is that email is NOT the primary key for Contacts in Salesforce.

It’s a unique ContactId.

This is essential to understand.
Knowing this,

Is your answer still valid?
Do you have an environment where you can test it quickly and validate?

Thanks again!

You can set ContactID as Primary Key https://i.imgur.com/5cHEg3p.png
but how you will enter ContactID in form

Impossible to have the Salesforce ContactID for a new visitor on the website.
It’s generated in Salesforce.

I think the term “Primary Key” is misused in the screenshot you sent – it’s not the real primary key for the object.

Which API do you use to post to Salesforce?
How are you using the API to post it to Salesforce based on the selections in the UI you sent screenshot of?

That’s why I believe it requires ACTUAL TEST of three scenarios:
Select Email as “primary key”, then:
1. Simply create a contact with the plug-in. Works?
2. Try to create the exact same contact, what happens?
3. Try to use same email – and different first name, what happens?

PS
In Salesforce we can have an email set to “Unique”, but it will not be the ContactID, it will just prevent duplicates.

Thanks @crmperks

plugin uses salesforce REST API and writes everything in log https://i.imgur.com/4HHFQot.png

Awesome!

We are looking at purchasing the plug-in, or else I’d be testing myself.
Since you have the environment running already,
Could you please run these simple tests and report back please?

Select Email as “primary key”, then:
1. Simply create a contact with the plug-in. Works?
2. Try to create the exact same contact, what happens?
3. Try to use same email – and different first name, what happens?

Thanks!

we have tested this more than 1000 times , plugin will update existing contact only

@crmperks I’m even more confused.
This is the opposite of what @sbazzi wrote on this thread only 3 days ago.

When you say: “plugin will update existing contact only”
– I understand we CAN’T create a new contact with the plug-in? Samer wrote we can.
– If we can’t create a Contact, can we create a new Lead or only update existing?

Could you copy-paste the API Call the plug-in generates to Contact- so I can test myself and reach a sure conclusion?

Thanks again!

• This reply was modified 4 years, 8 months ago by ranmichael.

@ranmichael we will get back to you about this soon.

@sbazzi @crmperks – any news?

You can create new lead OR update existing lead and both are optional
Plugin uses salesforce Rest API, request samples are available in salesforce docs