Contact Login
Integration directory

HubSpot integration

Connect HubSpot with the scope made explicit

HubSpot is listed as a supported OAuth connector in the current Queast product. Access is tenant-enabled, while public plan availability and the exact object, field, direction, and mapping contract must be confirmed before implementation.

Talk to us about HubSpot

Current connector status

Separate product support from commercial availability

The current product catalog marks HubSpot as supported. That does not make every tenant, plan, market, direction, object, or field automatically available.

VerifiedConnector catalog
Supported in the current product UI.
VerifiedTenant access
Integrations must be enabled for the tenant.
VerifiedConnection setup
OAuth is initiated by a tenant administrator and requires configured HubSpot app credentials.
ConfirmPublic plan and market
Not approved for publication; confirm with Queast.
ConfirmMarketplace or partnership
Not established by the available evidence and not claimed.

Verified technical footing

Start from the controls that exist

The current implementation establishes a bounded connector foundation. The exact customer contract still depends on approved configuration.

Tenant-scoped OAuth

Connection and refresh handling are scoped to the enabled tenant; secrets are stored encrypted and omitted from normal management responses.

Identity review

Connector mappings are tenant- and connection-scoped, with ambiguous matches designed to enter review instead of silent linking.

Delivery state

Delivery jobs and attempts support status, retry scheduling, and operational review without claiming a public cadence or SLA.

Optional schema changes

The current product can offer opt-in custom-field provisioning for connector-defined fields; it is not a universal default.

Verified foundation is not a blanket promise. Production scope still depends on the approved tenant configuration.

Movement contract

Describe each direction at its verified status

Do not summarize the connector as bidirectional sync. Outbound handling and inbound interest have different evidence and launch states.

Implemented foundationOutbound

Outbound foundation

Current handlers recognize company, person, and published Signal events. Exact HubSpot objects, fields, creation or update behavior, export profiles, and availability remain configuration-dependent.

Default disabledOutbound

Optional Signal Notes

A Signal-to-Notes path with contract metadata exists but is disabled by default unless enabled. It is not universal behavior.

Launch unconfirmedInbound

Inbound interest

Architecture and tests cover an authenticated company-interest event that resolves identity and creates a Queast bookmark. Public launch is not confirmed.

Human controlDecision

Human workflow

Administrators approve connection scope and mappings; sellers review context and decide the next CRM action.

Identity before delivery

Hold ambiguous records for review

A wrong CRM link can damage trust. The implemented mapping model preserves the Queast-to-HubSpot relationship and a review state without publishing unapproved matching keys or thresholds.

Explore company intelligence
  1. 01

    Candidate

    A possible partner record is identified within the tenant and connection.

  2. 02

    Review

    Ambiguous or low-confidence matches can remain quarantined instead of being auto-linked.

  3. 03

    Approved mapping

    The accepted relationship records its connector-specific partner identity and provenance.

  4. 04

    Scoped delivery

    Only the approved mapping and connection contract determine where context may move.

Artifact authority

Transport context without raising its authority

The connector moves an approved artifact. It does not recompute analysis, activate intent, bypass eligibility, or create a seller decision.

  1. 01

    Evidence and analysis

    Source evidence remains distinct from the interpretation built across evidence and time.

  2. 02

    Composite Intent

    The company-level, time-aware hypothesis keeps its lifecycle, conflicts, and provenance.

  3. 03

    Actionable Signal

    Only the recommendation that passed the applicable eligibility contract carries strict Signal authority.

  4. 04

    Approved connection

    The configured mapping transports selected context and preserves contract metadata where the approved destination allows it.

  5. 05

    Human CRM action

    A seller or administrator reviews the context and decides what happens next in HubSpot.

Explore Actionable Signals See Daily Workbench

Implementation checklist

Confirm the contract before connecting

These are required implementation decisions, not claims that every HubSpot connection exposes the same behavior.

Read Tech and Security
  • 1

    Availability

    Which plan, tenant, and market can use the connector?

  • 2

    Direction

    Which outbound and inbound paths are enabled?

  • 3

    Objects and fields

    What may be created, updated, appended, or provisioned?

  • 4

    Identity

    Which keys and review thresholds govern a match?

  • 5

    Permissions

    Which HubSpot app scopes and Queast roles are required?

  • 6

    Operations

    What delivery status, retry behavior, limits, support, and audit detail apply?

Next step

Verify your HubSpot contract with Queast

Confirm availability, direction, objects, fields, identity handling, permissions, and operational scope before implementation.

Talk to us about HubSpot Explore all integrations