HubSpot

The HubSpot connection helps sales teams act on qualified lead activity and helps analysts understand which campaigns and journeys are associated with CRM outcomes. HubSpot remains the system of record for CRM-owned fields.

The existing HubSpot connection completed its production authorization, field discovery, delivery, duplicate-prevention, and disconnect canary on August 2, 2026. The customer-health extension has a separate release gate and remains a selected Business private beta. It is not generally available.

HubSpot contact sync is supported on Pro and Business. Business workspaces can also enable revenue outcome imports and an optional deal-writing recipe.

Choose the access you need

Start with the smallest permission set that supports your workflow:

Access	Plan	What leadmaps can do
Contacts	Pro and Business	Find or create a contact for a qualified, consented lead and update only the mapped leadmaps fields.
Revenue outcomes	Business	Read linked deal stage, status, value, currency, and close date for reporting.
Deal writing	Business	Create or update a linked deal only when you explicitly activate a deal recipe.
Customer health and lifecycle	Selected Business beta	Update only the mapped company health fields and reconcile explicitly mapped company or deal statuses as trusted lifecycle changes.

Contacts is the default. leadmaps does not create deals or tasks unless an owner or admin chooses and activates a recipe that requires it.

Connect HubSpot

1. Open Settings, then Integrations.
2. Select HubSpot and choose Connect.
3. Choose the access level for this connection.
4. Select the correct HubSpot account and review the requested permissions.
5. Return to leadmaps and choose fields and deal stages by their HubSpot names.
6. Preview the result with masked example data.
7. Activate the connection or rule when the preview is correct.

Only a workspace owner or admin can connect, reconnect, change mappings, or disconnect HubSpot.

Choose fields and deal stages

The mapping editor loads the writable, non-sensitive fields that are currently available in the connected HubSpot account. It also loads active deal pipelines and stages when the connection has revenue or deal-writing access. The editor shows labels from HubSpot and stores the matching provider reference only after you make a choice.

Hidden, archived, calculated, read-only, and unsupported fields are not offered. A field or stage removed in HubSpot is shown as unavailable in an existing mapping. leadmaps keeps that saved mapping unchanged and requires a replacement before a new activation.

Connections authorized before field discovery was introduced may need to use Reconnect once so HubSpot can approve schema-read access. This permission lets leadmaps list eligible field definitions. It does not grant access to contact or deal values beyond the access level you selected.

Matching and duplicate protection

leadmaps first reuses a CRM record it has already linked. If there is no link, it uses your configured external identifier or a consented email address. If a safe, unambiguous match cannot be found, the delivery stops with an explanation instead of guessing or merging records.

Retries and repeated callbacks reuse the same delivery identity. They do not create another contact or deal for the same action.

Revenue outcomes

Business workspaces can import outcome fields from linked deals. These fields can appear in campaign, journey, and revenue analysis. leadmaps describes the relationship as an association and does not claim that a page, campaign, or interaction caused the outcome.

CRM-owned fields remain authoritative. leadmaps does not overwrite unrelated HubSpot fields or change deals that are not explicitly linked to the connection.

Customer health and lifecycle

This access profile is available only to selected Business workspaces in the customer health private beta. It cannot be enabled by choosing a client-side option when the workspace is outside the beta.

An owner or admin configures:

1. A stable company property containing the same explicit customer account identifier used by leadmaps.
2. Separate company properties for the leadmaps health and lifecycle labels.
3. An optional HubSpot company or deal status property to import.
4. The exact provider status values that should become trusted lifecycle changes.

The mapping does not infer a company from a contact email domain. Missing, blank, or unmapped status values do not create a lifecycle event. Repeated provider results and retries reuse the same logical update, while older effective changes remain in history without replacing a newer account state.

Customer-health automations are configured separately in the Integration Hub. They remain opt-in and do not send session replay, page contents, or raw event properties to HubSpot. Read Customer health and churn autopsies for the evidence and lifecycle boundary.

Reconnect or disconnect

Choose Reconnect when HubSpot says Needs attention, when permissions change, or when you want to select a different access level. A successful reconnect replaces the old authorization without creating a second connection. leadmaps then removes the replaced authorization in the background.

Choose Disconnect to stop new deliveries, remove stored authorization, and release the connection slot. Existing HubSpot records are not deleted.

Temporary provider failures are retried. Delivery history shows whether an action is waiting, succeeded, needs attention, or stopped permanently.

Data and privacy

Only fields required by the active mapping are sent. Free-text page contents, session replay, visitor browsing history, payment fields, passwords, and provider secrets are never sent to HubSpot through this connection.

Before activating a mapping, confirm that you have a lawful basis for every contact field you send and that the destination’s access and retention settings match your privacy policy.