HubSpot Integration

Clustr’s native HubSpot integration surfaces your network intelligence directly inside HubSpot through app cards on deal, contact, and company records.

​

Connect HubSpot

1. Go to Integrations in the Clustr dashboard and select HubSpot.
2. Click Connect HubSpot. You’ll be redirected to HubSpot to authorize access.
3. Once authorized, you’ll be returned to Clustr with your portal connected.

​

Enable the Cards

After connecting, you need to add the Clustr cards to your HubSpot record layouts. This is a one-time setup; repeat for deals, contacts, and companies. Card names to look for:

​

How It Works

Contacts and companies in HubSpot 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 HubSpot, with a direct link to their record
• Links to each prospect’s LinkedIn profile and Clustr page

From any card you can Import to HubSpot 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).

​

Settings

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

​

Write to HubSpot

​

Field Mappings

Clustr maps its internal data model to your HubSpot field names. The defaults match HubSpot’s standard schema. Change them only if your portal uses custom properties. Contacts Companies Deals

​

Owner sync

Clustr’s Owner column can stay in step with a HubSpot owner property, per record type. By default Clustr reads and writes hubspot_owner_id — on companies for an account’s owner, and on contacts for a connector’s. To use a different property, open Integrations ▸ HubSpot ▸ Field mappings and set the Owner row on the Companies and Contacts tabs. The picker lists HubSpot user properties; “Show all fields” escapes that filter if your portal keeps owners somewhere unusual. 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 HubSpot” starts unticked, every time. Writing into your CRM is a deliberate act, not a remembered habit. Leave it unticked and the new owner is saved in Clustr only; the cell then says it differs from HubSpot, and a later sync does not overwrite it. It stays that way until someone changes the owner in HubSpot. 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 HubSpot 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. Emptying a field in a customer’s CRM is not something a Clustr edit should do.
• Deactivated users. An archived HubSpot owner is kept in the directory and flagged; assigning them in Clustr works, pushing to them is refused.
• Someone who owns records in HubSpot but has no Clustr login still appears in your owner directory, so you can assign and filter on them like anyone else. List Owners reports a crmSeat per owner, which is how you tell in advance whether a push can name them.
• A multi-value owner property takes its first value.
• Warm intros are never synced. No CRM has an object for an intro, so the intro’s own owner is Clustr-only.
• Turning a mapping on offers a one-time reconciliation: take HubSpot’s owners, push Clustr’s, or leave the two different. Accounts with no owner in Clustr are filled either way.

HubSpot delivers webhooks only for hubspot_owner_id. If you map a custom owner property, changes to it reach Clustr on the regular sync rather than instantly.

​

Tier sync

An account’s tier can be mapped to one HubSpot company field. HubSpot has a built-in one: Ideal customer profile tier (hs_ideal_customer_profile). When your portal has it, Clustr offers it and can pair your tiers with its options by rank; nothing is saved until you save. Otherwise pick any single-select company property. Set it up in Settings ▸ Tiers, under the tier list, or from the Tier column’s gear on Accounts. Match each tier to one option, 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 option.

• 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 option, are skipped rather than cleared. A field that has become read-only, multi-value or deleted is refused at sync time.
• Your CRM sets the value: the field is read off every matched company. 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 HubSpot and Clustr. The integration also syncs automatically in the background.

​

Mark clients from HubSpot

Tell Clustr which HubSpot companies are your clients, and it fills your client companies list from them. In the app, open Targeting > Clients and set either or both of:

• a company property and the values that mean “client”
• Has a won deal: a deal in a Closed Won stage

With both, choose whether either is enough or both are needed. This list is how every part of Clustr tells your clients apart. Matching HubSpot companies are added with a HubSpot 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.