Skip to content
Merulan

HubSpot setup

What an operator supplies to connect the HubSpot Source, and the verification the provider requires.

Connecting HubSpot redirects the operator to the provider and returns with a grant. Merulan holds the credential directly. An operator who holds the material below connects in one pass.

Prerequisites

HubSpot refuses the connection until every item holds.

  • A HubSpot account, and a user who may approve a connected application.
  • A HubSpot subscription that exposes the CRM objects a Pipeline reads.

Credentials

HubSpot stores the credential under the direct custody the registry declares, so Merulan never shows the secret again once the connection is saved.

  • No secret is typed into Merulan. The browser grant returns an access token and a refresh token, and Merulan seals both.

Scopes

HubSpot requests the scopes the registry declares, and a grant missing one of them fails the first collection read.

  • crm.objects.deals.read
  • crm.objects.companies.read
  • crm.objects.contacts.read

Every HubSpot scope is read-only, and the consent screen shows no write scope because none is asked for.

Verification

Provider app review governs the HubSpot connection. HubSpot reviews a public application before it may be installed outside the developer account.

  • Connect and map a Source runs the connect ceremony and binds collections once the credential is in hand.
  • Integrations lists every Source that carries a setup page, with its ceremony and verification posture.