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

# HubSpot Integration: Technical Reference

> Technical details of the Deeto HubSpot integration — OAuth authentication, data sync, object mapping, write-back behavior, and answers to common technical and security questions.

This guide covers the technical details of how the Deeto HubSpot integration works — what data is synced, how sync is triggered, what Deeto writes back to HubSpot, and answers to common questions from IT and security teams.

For instructions on how your sales team uses Deeto inside HubSpot, see the [HubSpot Integration: Using Deeto in HubSpot](/integrations/hubspot-integration-setup) guide.

***

## Authentication

The integration uses OAuth. During installation, the installer is prompted to authorize an evergreen OAuth connection between Deeto and HubSpot. This connection remains active without requiring periodic re-authentication.

* **OAuth documentation:** [HubSpot OAuth Quickstart Guide](https://developers.hubspot.com/docs/api/oauth-quickstart-guide)
* **License key:** Contact [support@deeto.ai](mailto:support@deeto.ai) to obtain your license key.

***

## How data sync works

When a tracked HubSpot object changes, a trigger is sent to Deeto. Deeto evaluates whether that object is relevant — for example, a contact who is a reference, a prospect in an active deal, or a lead from Deeto. If the record is relevant and the updated field is mapped, Deeto updates its own records accordingly.

**Sync schedule:**

* Most events are handled **on demand** — when a user opens the Deeto tab in HubSpot, or when a mapped field changes
* One **scheduled job** runs daily to read data from HubSpot and ensure full sync accuracy

**Transaction volume:** One record at a time, triggered by a user action or a field change.

***

## Objects synced

### Deeto reads from

| Object    | Fields used                                             |
| --------- | ------------------------------------------------------- |
| Contacts  | Name, email, company, industry, and other mapped fields |
| Deals     | Stage, amount, close date, associated contacts          |
| Companies | Name, industry, size, and other mapped fields           |

### Deeto writes to

| Event                                       | What Deeto writes                                                                                                                                                            |
| ------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| A HubSpot contact becomes a Deeto reference | Updates `Deeto Id` on the **Contact** record                                                                                                                                 |
| A HubSpot contact becomes a Deeto reference | Updates `Deeto Id` on the associated **Company** record                                                                                                                      |
| A lead is created in Deeto                  | Adds a new record to the **Contacts** table                                                                                                                                  |
| A prospect and reference are connected      | Updates `Deeto Id` on the **Deal** record                                                                                                                                    |
| A prospect and reference are connected      | Creates/updates a **Ticket** object with `Deeto_Id`, `Deeto_Status`, and `Deeto_type` (the type of interaction — meeting, user story shared, video testimonial shared, etc.) |

<Note>
  Deeto treats HubSpot as the source of truth. Fields like first name, last name, and other standard properties are **read-only** from Deeto's perspective and are never overwritten.
</Note>

***

## Custom field mappings

You can create custom field mappings or modify the defaults using HubSpot Operations Hub (Starter or Professional plan required for custom field mapping).

***

## HubSpot objects Deeto integrates with

**CRM features used:**

* Contact & Company Details
* Data Sync by HubSpot
* Deals
* Tickets

**Other Deeto integrations:** Salesforce, Zoom, SendGrid

***

## Frequently asked questions

<AccordionGroup>
  <Accordion title="How do I get a license key?">
    Contact [support@deeto.ai](mailto:support@deeto.ai) to obtain your license key.
  </Accordion>

  <Accordion title="What is the authentication flow?">
    During installation, the installer approves an evergreen OAuth authorization. The connection remains active without periodic re-authentication.

    More detail: [HubSpot OAuth Quickstart Guide](https://developers.hubspot.com/docs/api/oauth-quickstart-guide)
  </Accordion>

  <Accordion title="Which objects does Deeto read from HubSpot?">
    Deeto reads from the **Contact**, **Deal**, and **Company** objects.
  </Accordion>

  <Accordion title="Which objects does Deeto write to in HubSpot?">
    Deeto writes to the **Ticket** object and updates the dedicated `Deeto Id` custom field on the **Company**, **Contact**, and **Deal** objects. All other fields are read-only.
  </Accordion>

  <Accordion title="Is it a real-time sync or a scheduled job?">
    Most events are handled on demand — when a user opens the Deeto tab or a mapped field changes. One scheduled job runs per day to ensure full sync accuracy.
  </Accordion>

  <Accordion title="How many records are synced per transaction?">
    One record at a time, triggered by a user action.
  </Accordion>

  <Accordion title="Why is the app asking for delete permissions?">
    HubSpot does not distinguish between write, update, and delete permissions. When an app requests write access, HubSpot automatically includes update and delete in the same OAuth scope. Deeto has confirmed this limitation directly with HubSpot and with an independent consultant — there is no way to request write access without these permissions being included. Deeto does not delete or modify any records outside of the Deeto-specific fields listed in this guide.
  </Accordion>

  <Accordion title="Is the Deeto app certified by HubSpot?">
    The integration is in the process of being submitted to the HubSpot marketplace. It has been carefully built to meet the highest security standards — the same measures required for Salesforce certification have been implemented.
  </Accordion>

  <Accordion title="What is the HubSpot installation process?">
    The HubSpot integration is set up by Deeto's team. Contact your Customer Success Manager or email [support@deeto.ai](mailto:support@deeto.ai) to initiate setup. A full installation guide is available from your CSM.
  </Accordion>
</AccordionGroup>

***

## Need help?

Contact your Deeto Customer Success Manager or email [support@deeto.ai](mailto:support@deeto.ai).