> ## Documentation Index
> Fetch the complete documentation index at: https://docs.threetone.in/llms.txt
> Use this file to discover all available pages before exploring further.

# HubSpot

> Prepare CRM context lookup and reviewed property updates with account-specific authorization and record matching.

Begin a HubSpot design with contact or company lookup, then propose a small property update for human review. Keep the exact CRM record and account visible throughout the action.

<Note>
  HubSpot is not a current native Threetone connector. The workflow below prepares an external integration. Neither saved credentials nor an authored tool enable CRM execution.
</Note>

## Prepare CRM access

You need a HubSpot administrator, a test account or approved test records, and a list of allowed objects and properties.

<Steps>
  <Step title="Choose an authentication model" id="hubspot-auth-model">
    HubSpot's [authentication overview](https://developers.hubspot.com/docs/apps/developer-platform/build-apps/authentication/overview) distinguishes OAuth from static authentication for a single authorized account. Choose the supported model for your distribution and request only required object access. Client-credentials tokens for app configuration do not substitute for user-account authorization.
  </Step>

  <Step title="Resolve the record before reading" id="hubspot-record-match">
    Require a confirmed record ID or a reviewed match. A company name alone can be ambiguous. Return only allowed properties and relevant associations. Keep each account's credentials and identifiers separate.
  </Step>

  <Step title="Review the proposed change" id="hubspot-update-review">
    Show the account, record, existing value, and replacement value. Confirm association changes separately from property updates. Re-read stale records and reconcile uncertain writes before retrying. Treat permission and rate-limit failures as incomplete actions.
  </Step>
</Steps>

Use [auth connections](/agents-platform/configure/authentication/auth-connections) only for compatible manually managed credentials. An external service must own any interactive OAuth lifecycle. [Tool configuration](/agents-platform/configure/tools/overview) can describe the reviewed lookup and update as separate actions.

## Frequently asked questions

<AccordionGroup>
  <Accordion title="Can a single-account token connect every customer's account?" id="faq-hubspot-account-token">No. Select the provider-supported authorization and distribution model for each intended account. Do not reuse one customer's credential for another.</Accordion>
  <Accordion title="Does a provider-hosted MCP service make this native?" id="faq-hubspot-mcp">No. An external MCP service still needs compatible authentication and transport. Threetone's [MCP discovery and execution limits](/agents-platform/configure/integrations/mcp-servers) remain applicable.</Accordion>
</AccordionGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.