DataLane HubSpot Integration Setup Guide
Last updated: July 17, 2026
Questions? Contact [email protected]
This document is your complete guide for connecting your HubSpot portal to DataLane as a Destination for CRM matching and/or sync.
1 What is the DataLane HubSpot Integration
1.1 What DataLane Does in Your HubSpot Portal
DataLane connects to HubSpot via OAuth and the HubSpot CRM APIs to perform entity resolution and data enrichment / syncing on your Company and Contact records.
What DataLane does:
Reads Company and Contact records to match them against DataLane's data
Writes entity resolution results back to HubSpot properties (for example, matched DataLane IDs and match timestamps)
Creates new Company and Contact records when configured for insert syncs
Updates existing Company and Contact records when configured for update syncs
Reads Deal associations for Contact update guards when those protections are enabled
What DataLane does not do:
Install a managed package, custom code, UI extension, workflow, or serverless function in HubSpot
Delete records from your HubSpot portal
Store your HubSpot username or password
1.2 What Gets Created or Managed
During setup, DataLane uses OAuth plus HubSpot property APIs to verify that the required DataLane-managed properties exist. If they do not exist, the DataLane setup flow can create them automatically.
Property group
DataLane creates or uses a HubSpot property group named "datalane" for DataLane-managed properties.
Required properties on Company:
Field (internal name) | Purpose |
datalane_account_id | Links the HubSpot Company to a DataLane account ID |
datalane_location_id | Links the HubSpot Company to a DataLane location ID |
datalane_attempted_match_date | Timestamp of the last matching attempt |
datalane_last_enriched_date | Timestamp of the last enrichment run |
Optional DataLane-managed Company property:
Field (internal name) | Purpose |
datalane_franchise_brand | Franchise brand name, when franchise enrichment is configured |
Required properties on Contact:
Field (internal name) | Purpose |
datalane_contact_id | Links the HubSpot Contact to a DataLane contact ID |
If a required property is already present, DataLane will not create a duplicate. If a required property is present but has the wrong type or is not writable, the setup screen will tell you which property needs to be fixed.
1.3 OAuth Scopes and Data Access
The HubSpot app requests the following scopes:
Scope | Purpose |
oauth | Standard OAuth authorization flow |
crm.objects.contacts.read / .write | Read, create, and update Contacts |
crm.objects.companies.read / .write | Read, create, and update Companies |
crm.objects.deals.read | Read Deal associations used by HubSpot Contact update guards |
crm.schemas.contacts.read / .write | Inspect and create DataLane-managed Contact properties |
crm.schemas.companies.read / .write | Inspect and create DataLane-managed Company properties |
crm.import | Bulk create/update records through HubSpot imports |
crm.export | Bulk export records for matching and validation workflows |
These permissions allow DataLane to:
Inspect Company and Contact schemas during setup
Search, read, create, and update Company and Contact records
Create the datalane property group and missing DataLane-managed properties when needed
Read Contact-to-Deal associations when Contact update protections are enabled
Run bulk import/export workflows for CRM matching and syncs
The OAuth connection runs with the permissions of the HubSpot user who authorizes it. You can revoke DataLane's access at any time by disconnecting the destination in DataLane or revoking the app authorization in HubSpot.
2 Installation & Configuration
2.1 Verify Prerequisites
Before connecting HubSpot, please confirm:
You know which HubSpot portal should be connected to DataLane
You can sign in to that portal as a HubSpot Super Admin, or as an admin who can install apps and manage CRM properties
Browser popups are allowed for the DataLane / Nango OAuth window
Recommended authorizing user
We recommend that a HubSpot Super Admin complete the one-time OAuth authorization. If you use a non-Super Admin, confirm the user has permission to:
Install and authorize apps
Read and write Companies
Read and write Contacts
Read Deals
Import records
Export records
Create and edit Company and Contact properties
Important: The HubSpot connection runs with the permissions of whichever user authorizes it. Use an admin account that should own the ongoing integration connection.
2.2 Start the Destination Setup in DataLane
Log in to DataLane.
In the left sidebar, click Setup → Destinations.
Click Add Destination.
Select HubSpot.
DataLane will open the HubSpot destination setup page.
2.3 Complete OAuth Authorization
On the Authorization step, click Connect to HubSpot.
A HubSpot OAuth window will open.
Sign in to HubSpot as the admin user you want to authorize the integration.
Choose the correct HubSpot portal.
Review and approve the requested scopes.
Wait for DataLane to show Successfully connected to HubSpot.
Click Continue to Configuration.
Important:
If you have access to multiple HubSpot portals, verify that you select the correct portal during OAuth.
If the OAuth window does not open, allow popups for DataLane / Nango and retry.
2.4 Verify or Create Required HubSpot Properties
DataLane will check that the required HubSpot properties exist and are writable.
Review the required fields check for the companies Object and contacts Object.
If every object shows Ready, click Continue.
If fields are missing, click Create Missing Fields.
Wait for DataLane to create the missing properties in HubSpot.
Click Re-check Fields.
Continue only after all required objects show Ready.
If field creation fails, the authorizing HubSpot user likely does not have permission to create or edit CRM properties. Retry with a HubSpot Super Admin, or create/fix the properties manually in HubSpot and then click Re-check Fields.
2.5 Verify the Installation
After setup is complete, verify the following:
DataLane → Setup → Destinations shows the HubSpot destination as connected
HubSpot Settings → Properties shows a datalane property group on Companies and Contacts
Company properties exist: datalane_account_id, datalane_attempted_match_date, datalane_last_enriched_date
Contact property exists: datalane_contact_id
3 Troubleshooting
Problem | Likely cause | What to do |
HubSpot does not appear in Add Destination | HubSpot destination is not enabled for your DataLane workspace | Contact your DataLane representative to enable HubSpot |
OAuth popup does not open | Browser popup blocker | Allow popups for DataLane / Nango and retry |
Wrong HubSpot portal was connected | Wrong portal selected during OAuth | Disconnect the destination and reconnect HubSpot using the correct portal |
Authorization succeeds but DataLane does not finish setup | Provisioning delay or expired browser session | Refresh DataLane and retry the connection |
Required field creation fails | Authorizing HubSpot user cannot create or edit properties | Retry with a HubSpot Super Admin, or manually create/fix the properties and click Re-check Fields |
Required field check says a property is missing | Property does not exist on the HubSpot object | Click Create Missing Fields or create it manually in HubSpot |
Required field check says a property has the wrong type | Property was created manually with an incompatible type | Fix the property in HubSpot, then click Re-check Fields |
Required field check says a property is not writable | Property permissions or HubSpot restrictions prevent writes | Check the property settings and authorizing user's permissions |
Default mappings do not match your HubSpot setup | Your team uses custom HubSpot properties for matching fields | Select the correct custom properties before clicking Create Config |
Existing Contacts are not updating | HubSpot Contact update guards are enabled | Review deal-association and lifecycle stage / lead status guard settings |
Connection stops working later | HubSpot app authorization was revoked or the authorizing user lost access | Reconnect the HubSpot destination in DataLane |
4 Quick Reference
Item | Value |
Provider | HubSpot |
Standard setup model | Companies + Contacts |
Connection method | OAuth |
Package installation required | No |
HubSpot property group | datalane |
Required Company properties | datalane_account_id, datalane_attempted_match_date, datalane_last_enriched_date |
Required Contact properties | datalane_contact_id |
Default matching schedule | Every 12 hours |
Primary DataLane UI path | Setup → Destinations → Add Destination → HubSpot |