System Overview

Mixbound Microservice: Salesforce SPoT ABM

Purpose

SPoT (Single Point of Truth) designates Salesforce as the authoritative system for Account records. HubSpot operates as the ABM discovery and engagement layer. Account authority resolves deterministically to Salesforce.

What SPoT ABM Constitutes

Identity Resolution Engine

Deterministic matching of HubSpot Companies to Salesforce Accounts using domain, external ID, and heuristic identity

Account Matching System

Hierarchical match evaluation with domain-first, external-ID, and normalized name strategies

Controlled Account Creation

Governed creation of Salesforce Accounts when no match exists, subject to eligibility rules

Duplicate Prevention Guard

Prevents uncontrolled duplication by resolving identity before any Account creation occurs

Cross-System Authority Alignment

Ensures HubSpot Companies and Salesforce Accounts are bidirectionally linked with stable identifiers

Governance Compliance

Operates through supported APIs and structured governance logic; does not override native sync rules

Target Audience

RevOps / SalesOps / GTM Engineering teams operating HubSpot as a primary ABM surface with Salesforce as the authoritative Account registry.

Technology

Node.js 18+ HubSpot API v3/v4 Salesforce REST API Salesforce Metadata API

Note

SPoT ABM does not override native HubSpot-Salesforce sync rules. It operates alongside the existing integration to resolve identity gaps and prevent duplication that native sync cannot address.

Resulting Alignment

HubSpot remains the operational ABM surface
Salesforce remains the authoritative Account registry
Identity resolution occurs before duplication
Sales teams see the same strategic Accounts that marketing and SDR teams activate
Sync behavior becomes predictable rather than conditional on contact timing