Follow

Salesforce

ActiveProspect integrates with Salesforce to offer the Add/Upsert a Contact/Lead actions of their API directly through LeadConduit.

Finding What You Need

The Salesforce integration requires you to enter a Salesforce username and password. Confirm the user credentials you'll authenticate with have Salesforce API Enabled permission, found in the Salesforce user profile:

SFAPIPermission.JPG

 

Our Best Practice Recommendation is to have your Salesforce Administrator create a user login and profile specifically for this use case.

Using Salesforce

Begin by adding a Salesforce Recipient step to your flow.

You may already have a named recipient (e.g. ActiveProspect's Salesforce in the screenshot), or you may need to choose Salesforce from the Integrations section and name a Recipient if you haven't done that before.

screencapture-next-leadconduit-flows-5ab1367f288e0d859aa23cb6-edit-steps-2018-04-24-13_55_59.png

The first time you configure a Salesforce recipient you will be prompted to authorize LeadConduit to connect with Salesforce:

screencapture-next-leadconduit-flows-new-steps-2018-08-06-10_11_28.png

On any subsequent connections, or if LeadConduit was previously connected to Salesforce, you are provided the option to use an existing connection or add a different one: 

credentials.png

 

For a new Salesforce account login, you will be directed to the Salesforce Login page. Enter the credentials to be used there:

SFLogin.JPG

Once the user has logged in to Salesforce, LeadConduit will establish its connection with Salesforce and will prompt you to choose the desired action from the list provided.

For Upsert actions, you will be prompted to select an External ID field and connect the appropriate data to it to make Upsert work properly. You can think of the External ID as a unique reference key since you won't know the Salesforce ID needed to Update the record.

When Salesforce is added to your flow, LeadConduit will automatically add all the Salesforce Standard fields to your flow:

FieldsAfterAutoAdded.JPG

The following tables list which Salesforce Standard Fields are automatically mapped and which standard fields must be set manually (*).

Common Fields
Salesforce LeadConduit
Salutation salutation
FirstName first_name
LastName last_name
Title title
Email email
MobilePhone phone_1
Phone phone_2 / phone_3
Fax fax
LeadSource LeadConduit Source Name
Description Description*

 

Lead Specific Fields
Salesforce LeadConduit
Street address_1
City city
State state
PostalCode postal_code
Country country
Company company.name
AnnualRevenue company.annual_sales
NumberOfEmployees company.number_employees
Industry company.industry
Website website
Name Name*
Latitude Latitude*
Longitude Longitude*
GeocodeAccuracy GeocodeAccuracy*
Address Address*
PhotoUrl PhotoUrl*
Status Status*
Rating Rating*

 

Contact Specific Fields
Salesforce LeadConduit
MiddleName middle_name
Suffix name_suffix
MailingStreet address_1
MailingCity city
MailingState state
MailingPostalCode postal_code
MailingCountry country
Birthdate dob
AssistantName AssistantName*
AssistantPhone AssistantPhone*
Department Department*
HomePhone HomePhone*
MailingLatitude MailingLatitude*
MailingLongitude MailingLongitude*
OtherAddress OtherAddress*
OtherLatitude OtherLatitude*
OtherLongitude OtherLongitude*
OtherPhone OtherPhone*
OtherStreet OtherStreet*

* Manually set Standard Salesforce field.

In addition to the basic Salesforce fields automatically added to your flow, you may want to provide for additional Salesforce fields that are part of your Contact or Lead profile. Here, for example, is a custom field in Salesforce named Source. Note that its Salesforce field name is Source__c. 

SFCustomField.JPG

As a final step in configuring the Salesforce step, the UI will provide a list of all Manually Mapped data plus any Custom Fields you have created.

Screen_Shot_2018-12-11_at_4.09.12_PM.png

That's all there is to it!

//--// 

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments

You must be logged in to comment.