Connecting Deeto to HubSpot creates a seamless bridge between your CRM and your customer reference program. This guide covers the technical details of how the integration works, what data is synced, and how to answer common questions from your IT or security team.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.
Integration overview
The Deeto HubSpot integration provides:- Two-way data sync — contact, company, and deal data flows between HubSpot and Deeto
- Embedded Deeto experience — sales reps access references directly inside HubSpot
- Automated campaign triggering — enroll contacts in Deeto campaigns based on HubSpot lifecycle events
- Reference activity tracking — Deeto writes back engagement data to HubSpot records
Authentication
The integration uses OAuth for authentication. During installation, the installer is asked to approve an evergreen OAuth authorization. This means the connection remains active without requiring periodic re-authentication. More about HubSpot OAuth: HubSpot OAuth Quickstart GuideHow data sync works
When a tracked object changes in HubSpot, a trigger is sent to Deeto. Deeto evaluates whether the object is relevant — for example, a contact who is a reference, a prospect in an active deal, or a lead from Deeto. If the updated record is relevant and the updated field is mapped, Deeto updates its own records accordingly. Sync schedule: Most events are handled on-demand — triggered when a user opens the Deeto tab or a mapped field changes. One scheduled job per day reads data from HubSpot to ensure ongoing sync accuracy. Transaction volume: One record at a time, triggered by a user action.Objects synced
Deeto reads data from the following HubSpot objects:- Contacts — name, email, company, industry, and other mapped fields
- Deals — stage, amount, close date, and associated contacts
- Companies — name, industry, size, and other mapped fields
- Contacts — when a HubSpot contact becomes a reference in Deeto, the
Deeto Idfield is updated on the contact record - Companies — the
Deeto Idfield is updated on the company record to maintain the link between HubSpot and Deeto - Contacts (leads) — at the time of lead creation, a new record is added to the contacts table
- Deals — when a prospect and reference are connected, the
Deeto Idfield is updated on the deal record - Tickets — when a prospect and reference are connected, Deeto creates or updates a ticket object to record the activity. The ticket includes:
Deeto_Id,Deeto_Status, andDeeto_type(the type of interaction — meeting, user story, video testimonial, etc.)
Permissions
Why does the app request 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 scope. Deeto has confirmed this limitation with HubSpot and with an independent consultant — there is no way to grant write permissions without including update and delete in the scope. Deeto does not delete or modify records outside of the fields listed above.App certification
Deeto is in the process of submitting the app to the HubSpot marketplace for certification. The same security measures required for Salesforce certification have been implemented in the HubSpot integration.Frequently asked questions
How do I get a license key? Contact support@deeto.ai to obtain your API key. What is the authentication flow? During installation, the installer approves an evergreen OAuth authorization. The connection remains active without requiring periodic re-authentication. See the HubSpot OAuth documentation for more details. Which objects does Deeto read from HubSpot? Deeto reads from the Contact, Deal, and Company objects. Which objects does Deeto write to in HubSpot? Deeto writes to the Ticket object and updates dedicated custom fields (Deeto Id) on the Company, Contact, and Deal objects. All other fields are read-only.
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.
How many records are synced per transaction? One record at a time, triggered by a user action.
Why is the app asking for delete permissions? HubSpot bundles write, update, and delete into the same permission scope. Deeto cannot request write access without this being included. Deeto does not delete or modify records outside of the Deeto-specific fields listed in this guide.
Is the app certified by HubSpot? Deeto is in the process of submitting the app to the HubSpot marketplace. The same security standards required for Salesforce certification have been applied to the HubSpot integration.