Connecting Deeto to HubSpot brings your reference program directly into your sales team’s existing environment. This document covers how the integration works technically — what data syncs, how sync is triggered, what Deeto writes back to HubSpot, and answers to common technical questions. For setup instructions, see the HubSpot Integration Setup guide.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.
Authentication
The integration uses OAuth. During installation, the installer is prompted to authorize an evergreen OAuth connection between Deeto and HubSpot. More about HubSpot OAuth: https://developers.hubspot.com/docs/api/oauth-quickstart-guide License key: Contact support@deeto.ai to obtain your license key.HubSpot objects Deeto integrates with
CRM- Contact & Company Details
- Data Sync by HubSpot
- Deals
- Tickets
How data sync works
Deeto reads from the Contact, Deal, and Company objects in HubSpot. When any of these objects are updated in HubSpot, a trigger is sent to Deeto. Deeto then checks whether that object is relevant to it — for example, a contact that is a reference in Deeto, a prospect linked to a Deeto deal, or a lead generated through Deeto. If the record is relevant and the updated field is mapped to Deeto, the value is updated in Deeto. Sync schedule:- Most events are handled on demand — when a user opens the Deeto tab in HubSpot or when a mapped field changes in HubSpot
- One scheduled job runs daily to read data from HubSpot and ensure full sync
What Deeto writes back to HubSpot
Deeto treats HubSpot as the source of truth for contact, company, and deal data. It only writes to dedicated Deeto fields — it does not update names, emails, or other standard fields.| 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 record to the Contact table |
| A prospect and reference are connected | Updates Deeto Id on the Deal record |
| A prospect and reference are connected | Creates a Ticket object with Deeto_Id, Deeto_Status, and Deeto_type (the type of interaction — meeting, user story shared, video testimonial shared, etc.) |
Custom field mappings
You can create your own custom field mappings or modify the defaults in HubSpot Operations Hub (Starter or Professional plans required for custom field mapping).Frequently asked questions
What objects does Deeto read from HubSpot?
What objects does Deeto read from HubSpot?
Deeto reads from the Contact, Deal, and Company objects.
What objects does Deeto write to in HubSpot?
What objects does Deeto write to in HubSpot?
Deeto writes to the Ticket object and updates dedicated custom fields on Contact, Company, and Deal records. It does not modify any other HubSpot fields.
Is this a real-time sync or a scheduled job?
Is this a real-time sync or a scheduled job?
Most events are handled on demand when a user opens the Deeto tab in HubSpot or a mapped field changes. A scheduled job also runs once daily to ensure full data consistency.
How many records are synced per transaction?
How many records are synced per transaction?
One record at a time, triggered by a user action.
Why is Deeto requesting permission to delete objects?
Why is Deeto requesting permission to delete objects?
HubSpot does not distinguish between write, update, and delete permissions. When Deeto requests write access, HubSpot automatically includes delete and update options in the OAuth scope. Deeto does not delete HubSpot records — this is a HubSpot platform limitation, not a Deeto behavior.
Is the Deeto app certified by HubSpot?
Is the Deeto app certified by HubSpot?
Deeto is in the process of HubSpot Marketplace certification. In the meantime, Deeto has implemented the same security standards required by Salesforce for their certification process.