What connects

The connection uses a HubSpot OAuth app and requests read access to companies, contacts, and deals, contacts write access, and the oauth scope. The app needs server-configured client credentials and the IntellaOne callback URL.

An IntellaOne administrator configures the server-side app Client ID, Client Secret, redirect URL, and requested scopes.
The customer HubSpot administrator or connected user approves the OAuth request and must permit the requested CRM reads and writes.

Information used

HubSpot search is incremental by each object's last-modified timestamp. The first run is capped at 500 records per object; later runs can process up to 5,000 changed records per object in a run.

Companies: name, industry, employee count, annual revenue, domain, and website.
Contacts: name, email, job title, phone, and associated company. Department is not populated by this provider.
Deals: name, pipeline, stage, amount, close date, and stage-derived probability and closed/won state.
Companies, contacts, and deals can each be disabled in the connection's inbound sync settings.

Why it is useful

Company, contact, and deal context helps a seller understand the account and current pipeline stage while a conversation is in progress. The same resolved contact or deal can be associated with an approved outcome.

How the workflow behaves

HubSpot data refreshes automatically on the provider's 15-minute cadence. A rep can review and approve a proposed outcome, or explicitly forward notes; the provider does not automatically rewrite deal fields.

The outbound action creates a HubSpot Note associated with the resolved contact and/or deal.
When next steps exist, IntellaOne makes a best-effort NOT_STARTED follow-up Task due about 24 hours later; a task failure does not undo the Note.
The connection's outbound activity toggle can turn this write-back off.
This connection does not update deal fields or import HubSpot activity history as inbound context.

Prerequisites and limits

Before connecting, an IntellaOne administrator must configure the server-side HubSpot OAuth app, callback, client credentials, and requested scopes. The customer HubSpot administrator or connected user must then authorize the OAuth request and grant the account/user CRM permissions. Provider rate limits, scope changes, and account configuration can interrupt a sync or optional task creation.

Availability still depends on the provider account, plan, permissions, and application setup; a catalog status is not a guarantee that every account can use every provider feature.

Security and privacy boundaries

Newly saved connector credentials are encrypted before storage.

Connected tools sync server-side under the user's own credentials. Requested permissions and data flows are connector-specific.

Availability still depends on the provider account, plan, permissions, and application setup; a catalog status is not a guarantee that every account can use every provider feature.

CRM write-back requires explicit rep initiation or approval: proposal approval authorizes proposal writes, while forwarding notes occurs only after an explicit rep action.

Inbound object toggles limit which CRM objects are synced for this connection.
A successful write depends on HubSpot accepting the approved Note or Task request; provider behavior can change.