HubSpot Destination
Overview
This page guides you through the process of setting up the HubSpot destination connector.
Prerequisites
- HubSpot Account
Setup guide
Step 1: Set up the HubSpot connector in Airbyte
-
Log into your Airbyte account.
-
Click Destination and then click + New destination.
-
On the Set up the destination page, select HubSpot from the Destination tiles.
-
Enter a name for the HubSpot connector.
-
From the Authentication dropdown, OAuth authentication is available so click Authenticate your HubSpot account to sign in with HubSpot and authorize your account.
HubSpot Authentication issuesYou may encounter an error during the authentication process in the popup window with the message
An invalid scope name was provided
. To resolve this, close the window and retry authentication. -
Click Set up destination and wait for the tests to complete.
Supported Objects
The HubSpot source connector supports the following streams:
- Companies: Upsert on unique field
- Contacts: Upsert on email
- Deals: Upsert on unique field
- Custom Objects: Upsert on unique field
Limitations & Troubleshooting
Rate limiting
The connector is restricted by normal HubSpot rate limitations.
App Verification
In order to verify our HubSpot application, HubSpot expects some usage i.e. more than 60 installations. Hence, when installing the app, you might see the message "You're connecting to an unverified app". This is expected for our first users. Once we have enough traffic on the application, we will be able to verify the app which will remove this warning.
Scopes for Unsupported Streams
During app the app installation, you might see scopes related to objects we don't support. This is expected as changing scopes might require the users to re-authenticate which is quite disruptive. In order to prevent that, we added scopes on objects we intend to support given user demands.
403 Forbidden Error
Hubspot has scopes for each API call. Each stream is tied to a scope and will need access to that scope to sync data. Review the Hubspot OAuth scope documentation here.