Connecting HubSpot

A HubSpot connector pulls contacts in and keeps chosen properties in step.

The token

Create a private app token at https://app.hubspot.com/private-apps and give it the contact scopes it needs and no more. The token is stored encrypted and is never returned by this API, not even truncated -- if you lose it, issue a new one rather than looking for it here.

Choosing what comes across

Pull a list rather than the whole portal where you can. A sync scoped to a list is faster, easier to reason about, and much easier to undo.

Property mapping is explicit. Anything unmapped is left alone in both directions, which is the safe default when two systems disagree about what a field means.

Consent is not a property to copy

HubSpot's subscription state and this product's consent records answer different questions. Consent here is stored as one row per decision -- who, when, which group, from what source, reacting to which identity -- because a flag that was flipped cannot tell you when somebody opted out or from what.

So a sync will not relax deliverability state. Bounces, complaints and unsubscribes recorded here stand, whatever an inbound property says. A contact can be made less mailable by a sync and never more.

Unsubscribes flow outward

An unsubscribe recorded here is pushed back where the mapping allows it, so the CRM does not go on believing somebody is subscribed. It is the one direction where overwriting is the right behaviour: a person said no, and both systems should know.