Connect Salesforce to Hublead

Connecting Salesforce to Hublead takes two steps, in this order: a Salesforce administrator installs Hublead in your org once, then each user connects their own Salesforce account from the extension. If your connection fails on the first try, the org install is almost always the missing piece.

The two steps, in order

Once per org, by an administrator: Hublead has to be installed as a connected app in your Salesforce org.
Once per user: each person clicks Connect Salesforce in the extension, logs in, and authorizes the connection.

Salesforce blocks standard users from authorizing a connected app that has not been installed in their org. Administrators are exempt from that rule, so an admin connecting successfully is not proof that your org is set up. Test with a sales user.

Connect your own Salesforce account

Install the Hublead Chrome extension: go to hublead.io, click Try for free, then Download our extension, then Add to Chrome. Chrome opens LinkedIn for you.
On LinkedIn, open the Hublead panel.
Click Connect Salesforce.
Log in to Salesforce and authorize the connection.
You land back in Hublead. Open any LinkedIn profile and the panel now shows your Salesforce data. It works on LinkedIn Sales Navigator too.

If you get an error page instead, your admin needs to complete the org install below.

Install Hublead in your Salesforce org (administrator)

These steps are done once per org, by a Salesforce administrator, and take about five minutes. Sales users cannot do them, they do not have the required permission.

Step 1 – Trigger one connection attempt

Hublead only appears in the Salesforce setup screens after someone has tried to authorize it at least once. This first attempt is expected to fail.

In the Hublead extension, click Connect Salesforce and complete the Salesforce login.
You land on an OAuth error page. That is normal, the attempt has registered the app in your org.

Step 2 – Install Hublead in the org

In Salesforce, open Setup.
In the Quick Find box, type OAuth and select Connected Apps OAuth Usage.
Find Hublead in the list.
Click Install on that row, then confirm.

Two pages look alike and are easy to confuse. Connected Apps OAuth Usage lists the apps users have attempted to use. Manage Connected Apps lists the apps that are actually installed. To check the install worked, open Manage Connected Apps, Hublead must appear there.

Step 3 – Give your users access

When installing, Salesforce asks how users are allowed to use the app. Pick the option that matches your security policy.

Option A – Admin approved users are pre-authorized (more controlled). Only the profiles and permission sets you designate can connect.

Setup → Quick Find → Manage Connected Apps.
Click Hublead, then Manage.
Use Manage Profiles or Manage Permission Sets to add the profiles of your sales users.

Users whose profile is not listed will get an OAUTH_APPROVAL_ERROR_GENERIC error.

Option B – All users may self-authorize (simpler). Anyone in the org can connect Hublead on their own, with no per-profile assignment. You set this on the same Manage screen.

Step 4 – Reconnect

Ask the user to click Connect Salesforce again in the extension. The connection now completes and lands back in Hublead.

What the error message tells you

Error on screen or in the URL	What it means	What to do
`invalid_client` – `app must be installed into org`	Hublead is not installed in this org, and the user is not allowed to approve an uninstalled app.	Steps 1 and 2 above.
`OAUTH_APPROVAL_ERROR_GENERIC`	Hublead is installed, but this user's profile has not been granted access to it.	Step 3 above.

One thing worth doing right after connecting

Hublead matches a LinkedIn profile to your Salesforce records using a LinkedIn URL field, and most orgs already have their own. Go to hublead.app, then Settings → Field mapping, and select the Salesforce field where you already store LinkedIn URLs. You can map other LinkedIn information to your own custom fields there as well. Two minutes here is what makes the matching accurate from day one.