HubSpot support

Last updated date:

Connect, reconnect, and troubleshoot HubSpot without sharing credentials or customer content through support channels.

1. Before you start

  • Choose the HubSpot account Seedling should read and use a Super Admin to create its private app.
  • Grant the five required read scopes and the three recommended schema scopes.
  • Use a dedicated private app token and do not reuse a token shared by unrelated integrations.
  • Do not send HubSpot credentials, customer content, personal information, or private record data by email or through an ordinary support ticket.
HubSpot app authenticationHubSpot's official private-app authentication overview.

2. Connect HubSpot

  1. Create the private app in HubSpot and copy its access token from the Auth tab.
  2. In Seedling, open Connections, select HubSpot, and choose personal or workspace scope.
  3. Paste the token and optionally name the account.
  4. Connect and confirm the verified HubSpot portal before synchronization begins.

3. Authorization and connection problems

Missing required scope
Add the named read scope to the private app in HubSpot, then reconnect; Seedling reports required scopes explicitly.
Wrong account
Create or use a private app token from the intended HubSpot portal. The verified portal ID cannot be replaced with an account label.
Custom properties lack context
Add the recommended schema scopes so Seedling can read property definitions for contacts, companies, and deals.

4. Missing or delayed data

  1. Confirm the private app can read the affected object type and the record remains visible to the token owner.
  2. Confirm the affected record is not archived or outside the configured object population.
  3. Check whether custom schema, association, or pipeline changes explain the difference.
  4. Allow incremental synchronization and provider retry handling to complete. A temporary provider failure does not delete previously synchronized data.
  5. If the issue remains, contact support@tryseedling.ai with the Seedling workspace, safe timestamps, and non-sensitive provider record identifiers. Do not include credentials or record contents.

5. Rotate or replace access

Never use email or an ordinary support ticket to transfer the old or replacement credential.

  1. Rotate the private app token in HubSpot or create a replacement app with the same required read scopes.
  2. Replace the credential on the exact Seedling connection and confirm the same portal ID.
  3. Revoke the old HubSpot token after Seedling verifies the replacement.