Integrating Salesforce with third-party tools like Lusha can sometimes lead to various error messages, each with distinct causes and solutions.

By understanding these common errors and their solutions, users can ensure a smoother integration between HubSpot and Lusha.

💡Note: Most of the issues below can only be solved by a SF admin and a Lusha admin. In many cases, it is the same person.

Error meaning: Admins can limit the team's API daily usage which means that Lusha will use fewer API calls but also give less information while prospecting.

It will look like this:

How to solve this?

Since only the admin can see the limit, this needs to be checked with the SF admin who has permission to change the API daily limit. The admin can also increase the daily API limit by going to the integrations page >> Salesforce >> hit the API request limit.

Another option is waiting until the next day in order to save, as the limit is reset every 24 hours.

Error meaning: If you can’t save a Lead to SF due to a restriction order of a certain lead or if the saved lead is assigned to another person automatically, the issue is most likely related to the “Lead Assignment Rules” on SF.

What are Lead Lead Assignment Rules?

Assignment rules are a Salesforce feature that can help automate the organization's lead generation and support processes. Assignment rules dictate to whom a lead or case is assigned based on criteria specified within Salesforce. Typically, the organization will have one rule for each overall purpose.

How to solve this?

Resolving this issue will occur when the existing lead assignment rules are bypassed. This will require the SF admin to add a new rule.

On the SF setup page, the SF admin should search for Lead Assignment Rules.

Under the relevant process, add the following rule: Sort order - No. 1 of with the rule of when "Lead Source" - equals "Lusha", then "Do Not Reassign Owner"

Error meaning: The value that Lusha is trying to push to the restricted picklist field doesn’t match one of the values on the list.

It will look like this:

For example: In the screenshot above you can see that the issue occurs with the Region field on SF and the bad value is California.

How to solve this?

The saved value from Lusha has to be matched to the value on SF. This is important due to the restricted picklist situation. It may be due to case sensitivity or a small difference in how the values are written on SF to the way Lusha provides the information.

A common example can be with the country field: Russia → Russian Federation, China → People's Republic of China, etc.

Error meaning: The value must be entered in order to save to contact/lead on SF. This happens because the SF admin sets the field as a required field when saving a new prospect.

It will look like this:

For example, in this case, a Billing City is required.

How to solve this?

In the case above, the Billing City is a required field and therefore must be mapped in the field mapping setting of the SF integration.

Error meaning: These kinds of issues can be very diverse but the syntax is quite similar. Pay attention to the phrase “No such column ‘______’, (in this case LeadSource field is the issue) on entity ‘____’.

It will look like this:

For example, in this case, the Lead field is the issue, the entity could also be Contact or Account.

How to solve this?

In the case above, the Lead Source field doesn't exist on Salesforce.

Fixing the issue will require the SF admin to add that field or delete the field from the Lusha/SF integration field mapping.

The best practice would be to add the Lead Source field on SF in order to have visibility on the leads and contacts driven by the Lusha integration.

Error meaning: If you are trying to connect the SF integration and you get the error of “Something went wrong” it is most likely because SF is blocking the connection with the Lusha app.

Every third-party app on SF needs authorization in order to be connected to the SF account. Some of the accounts block all the new third-party apps by default.

It will look like this:

How to solve this?

The SF admin needs to go to the Setup page on SF and under the “Connected Apps OAuth Usage” unblock the Lusha Push to Salesforce app.

Error meaning: You are part of a Salesforce edition that doesn’t support API integrations with other applications such as Lusha.

It will look like this:

How to solve this?

The issue is coming from your Salesforce license which doesn't include the Web Services API.

In order to save contacts from Lusha to Salesforce, you will need to have this feature in Salesforce.

To find out more about which versions have API access please check this link.

Error meaning: The users do not have access/permissions to the specific Record Type on their Salesforce account.

It will look like this:

How to solve this?

There are 2 options in this case:

1. Speak to your SF account admin, and have them grant you access to the relevant Record Types.

2. Ask the Lusha admin to turn off the Record Type default, or choose a record type that everyone has access to.

Error meaning: This occurs when there is an attempt to export a Lead that has already been converted into a Contact, Account, or Opportunity. (Meaning, this lead is already in your records).

It will look like this:

How to solve this?

Consider checking your SF if this lead or opportunity does exist.