This article outlines the requirements, permissions, supported field types, and other considerations for using the Cognism HubSpot integration.
Before You Begin
Before connecting HubSpot to Cognism, ensure that:
- You have a HubSpot account.
- You have permission to authorise third-party applications.
- You have the required CRM permissions.
- A Cognism Admin will configure the integration before users begin exporting records.
Supported HubSpot Editions
The Cognism integration supports all HubSpot editions, including:
- Free
- Starter
- Professional
- Enterprise
There are no edition-based restrictions for connecting the HubSpot integration.
User Permissions
To use the HubSpot integration, users require the following HubSpot permissions.
| Permission | Required Access |
|---|---|
| App Marketplace | Required |
| Contacts | View and Edit (Everything) |
| Companies | View and Edit (Everything) |
| Deals | View and Edit (Everything) |
| Tickets | View and Edit (Everything) |
| Tasks | View and Edit (Everything) |
| Import / Export Tools | Enabled |
These permissions allow users to authorise the integration and export records successfully.
Super Admin Requirement
In some cases, HubSpot requires the user connecting the integration to have Super Admin permissions.
This is a HubSpot security requirement and not a Cognism limitation.
The requirement only affects the initial authorisation of the integration.
Once the connection has been established successfully, Super Admin permissions can usually be removed without affecting day-to-day use of the integration.
HubSpot Sandbox Accounts
HubSpot Sandbox and staging environments are supported.
You can connect a Sandbox account in the same way as a production account.
There are no additional Cognism configuration requirements when using a HubSpot Sandbox.
Supported Field Types
The following HubSpot property types can be mapped in Cognism:
- Text
- Number
- Date
- Date & Time
- Single Select (Enumeration)
- Boolean
Unsupported Field Types
The following property types cannot be mapped:
- Calculated properties
- Multi-checkbox properties
- Custom objects that are not available through the HubSpot API
- Other unsupported API field types
Unsupported properties do not appear when configuring field mappings.
Best Practices
For the best experience:
- Configure field mappings before allowing users to export records.
- Create any required custom HubSpot properties before configuring mappings.
- Review user permissions if exports fail unexpectedly.
- If the initial connection fails, temporarily assign Super Admin permissions and retry the connection.