Skip to main content
Clustr’s native Salesforce integration surfaces your network intelligence directly inside Salesforce through Lightning components on opportunity, contact, and account records.

​
Connect Salesforce

  1. Go to Integrations in the Clustr dashboard and select Salesforce.
  2. Click Connect Salesforce. You’ll be redirected to Salesforce to authorize access.
  3. Once authorized, you’ll be returned to Clustr with your org connected.
Only one CRM can be active at a time. If HubSpot is already connected, disconnect it before connecting Salesforce.

​
Install the Clustr app

The cards come in the Clustr app for Salesforce, a managed package you install once in your org. Connecting Salesforce does not install it: the connected app you approve when connecting only covers sign-in. You need a Salesforce admin for these steps.
1

Install the package

In Clustr, open Integrations, select Salesforce, and click Install next to Install Clustr App in Salesforce. This always opens the latest version, on the sandbox login page if your org is a sandbox. When Salesforce asks who to install it for, choose Install for All Users.
2

Give your team access

The package adds a permission set called Clustr User. Salesforce does not assign it on its own, so assign it to everyone who should see the cards: in Setup, open Permission Sets, select Clustr User, and click Manage Assignments.
If Salesforce offers to downgrade the Clustr app, cancel. It means the link names an older version than the one you already have, and the version you have is fine.

​
Enable the Cards

Once the app is installed, add the Clustr components to your Salesforce page layouts. This is a one-time setup per record type; repeat for opportunities, contacts, and accounts. Each card is listed only on its own record type’s page, so the opportunity card will not appear when you edit a contact page.
1

Open the page editor

Open any opportunity (or contact, or account) in Salesforce. Click the gear icon (⚙️) in the top-right corner, then select Edit Page.
Salesforce setup menu showing the Edit Page option
2

Find Clustr in the component panel

The Lightning App Builder opens. In the left panel, type Clustr in the component search box. The Clustr card appears under Custom components.
Lightning App Builder component search showing Clustr Network Insights
3

Drag the component onto the page

Drag the Clustr component from the left panel onto the desired section of the page layout on the right.
4

Save and activate

Click Save. If prompted to activate the page, click Activate and assign it as the Org Default so it appears for all users.
Component names to look for:

​
How It Works

Contacts and accounts in Salesforce are automatically matched to your Clustr network via domain and LinkedIn URL. Their latest CRM activity is shown alongside relationship data. Each card shows:
  • A confidence score for each referral path
  • The connector who can make the introduction
  • Shared work history and recent engagement activity (calls, emails, meetings)
  • An In CRM flag for prospects already in Salesforce, with a direct link to their record
  • Links to each prospect’s LinkedIn profile and Clustr page
From any card you can Import to Salesforce to push prospects into your CRM, or See all in Clustr to explore the full list.

​
The Cards

Every card has two tabs. The first tab shows how to reach people (your paths in). The second tab shows what you can leverage (who can be introduced through them).
Clustr Network Insights component on a Salesforce Contact record
  • At : prospects reachable through your network
  • From : who opportunity contacts can introduce you to
Closed opportunities default to the “From” tab.
  • From: who they can introduce you to
  • To : who can introduce you to them
If the contact isn’t in Clustr yet, you’ll see an import prompt.
  • At : prospects reachable through your network
  • From : your contacts who can intro elsewhere

​
Settings

Once connected, you can configure write permissions and field mappings from the Salesforce integration settings page.

​
Write to Salesforce

​
Field Mappings

Clustr maps its internal data model to your Salesforce field API names. The defaults match Salesforce’s standard schema. Change them only if your org uses custom fields. Contacts Accounts Opportunities

​
Owner sync

Clustr’s Owner column can stay in step with a Salesforce owner field, per record type. By default Clustr reads and writes OwnerId — on the Account for an account’s owner, and on the Contact for a connector’s. To use a different field, such as an “Account Executive” lookup, open Integrations ▸ Salesforce ▸ Field mappings and set the Owner row on the Accounts and Contacts tabs. The picker lists lookup fields that point at User; “Show all fields” escapes that filter. Only admins can save a mapping. The Owner column’s gear on each table opens the same row and shows everyone else a read-only line. Each record type gets its own direction: “Also update in Salesforce” starts unticked, every time. Leave it unticked and the new owner is saved in Clustr only; the cell then says it differs from Salesforce, and a later sync does not overwrite it. Over the API the same choice is push_to_crm on Set Account State, Bulk Set Account State and Set Connector Owner, and the response’s crmPush says what happened. Things worth knowing:
  • A record that is not in Salesforce has nothing to write to. The push is refused with record_not_matched, and the owner is still saved in Clustr.
  • Clearing an owner is never pushed.
  • A queue is not an owner. A record owned by a queue (an id starting 00G) reads as unowned.
  • Inactive users stay in the directory, flagged. Assigning them in Clustr works; pushing to them is refused.
  • Someone who owns records in Salesforce but has no Clustr login still appears in your owner directory. List Owners reports a crmSeat per owner, so you can tell in advance whether a push can name them.
  • Warm intros are never synced. No CRM has an object for an intro.
  • Turning a mapping on offers a one-time reconciliation: take Salesforce’s owners, push Clustr’s, or leave the two different.
Salesforce changes reach Clustr on the sync, not instantly. There is no webhook here, so an owner or tier changed in Salesforce lands on the next sync pass.

​
Tier sync

An account’s tier can be mapped to one Salesforce Account picklist. Salesforce has no standard field for it — the usual answer is a custom “ABM Tier” picklist. Rating (Hot / Warm / Cold) is heat, not tier. Set it up in Settings ▸ Tiers, under the tier list, or from the Tier column’s gear on Accounts. Match each tier to one picklist value, leaving “Not in your CRM” on any tier that should stay out, then choose the direction: Clustr sets the value, Your CRM sets the value, or Paused. Two tiers cannot share one value.
  • Clustr sets the value: the tier is written on each sync, not on every edit. An account with no tier, and a tier with no value, are skipped rather than cleared. A field that has become read-only, multi-select or deleted is refused at sync time.
  • Your CRM sets the value: the field is read off every matched Account. An unchanged value does nothing, so a tier edited in Clustr survives; a changed one sets the Clustr tier when it maps to a tier you have. Empty and unmapped values leave the Clustr tier alone.

​
Sync

Click Sync Now to trigger a manual sync between Salesforce and Clustr. The integration also syncs automatically in the background.

​
Mark clients from Salesforce

Tell Clustr which Salesforce accounts are your clients, and it fills your client companies list from them. In the app, open Targeting > Clients and set either or both of:
  • an account field and the values that mean “client”
  • Has a won deal: an opportunity marked Won
With both, choose whether either is enough or both are needed. This list is how every part of Clustr tells your clients apart. Matching Salesforce accounts are added with a Salesforce badge. The list updates nightly, or when you press Sync now. This is set up in the app only; the API and MCP server can read these companies and mark them not a client, but not change the rule.