Connect a production HubSpot account with Embrasure OAuth and verify the first warehouse sync.
Connect HubSpot in about five minutes. Embrasure uses its existing OAuth app, so you do not create a private app, copy an access token, or find Embrasure in the HubSpot Marketplace.
No private app is required
Embrasure uses HubSpot OAuth for customer installations. HubSpot may show an unverified-app warning while the app is not listed in its Marketplace. Confirm the app is Embrasure Warehouse Ingestion, review the requested read access, then follow HubSpot's confirmation steps. A Marketplace listing is not required for this OAuth connection to work.
You need:
The HubSpot user is needed only to approve the connection. Embrasure does not store that user's password.
Open Warehouse → Ingestion. Select Connect warehouse source for the first source, or New sync if the workspace already has ingestion syncs. Find HubSpot and select Connect.
HubSpot lists the accounts the signed-in user can access. Select the production account, then select Choose Account. If the account is missing, sign in as a HubSpot Super Admin or ask an admin to grant HubSpot Marketplace Access and the required CRM permissions.
Embrasure requires read access to contacts, companies, and deals. It also requests optional read access for data such as tickets, owners, products, line items, quotes, and custom objects. HubSpot leaves out optional access that the account's plan or the installing user cannot grant.
If HubSpot shows an unverified-app warning, confirm the app is Embrasure Warehouse Ingestion and the permissions are read access described above. Then select Connect app.
HubSpot returns you to Embrasure and catalog discovery begins. Start with contacts, companies, and deals. Keep the suggested columns selected, choose the destination database, run validation, and select Start sync.
Optional tables appear only when HubSpot granted their access. This does not block the three core tables.
Setup is complete when:
Embrasure then continues from its saved HubSpot cursor. Archived HubSpot records are kept as deletion markers in the warehouse.
| Access | Data |
|---|---|
| Required | Contacts, companies, and deals |
| Optional | Tickets, owners, products, line items, quotes, and custom objects |
| Discovered automatically | Available activities, pipelines, stages, and associations between accessible CRM objects |
Optional data depends on the HubSpot plan and the permissions granted during connection. Reconnect HubSpot after an admin adds access so Embrasure can request the new permissions.
| Symptom | What to do |
|---|---|
| The production account is not listed | Sign in to the correct HubSpot user. Use a Super Admin, or grant the user HubSpot Marketplace Access and the requested CRM permissions. |
| HubSpot shows an unverified-app warning | Confirm the app is Embrasure Warehouse Ingestion and the requested permissions match this guide, then select Connect app. Do not continue for a different app name or unexpected write access. |
| Contacts, companies, or deals are missing | Reconnect with a user who can grant read access to all three core object types. |
| An optional table is missing | Confirm the HubSpot account has that product and the installing user can grant its read permission, then reconnect. |
| Authorization returns to Embrasure but no tables appear | Retry catalog discovery. If it still fails, reconnect HubSpot and confirm the core permissions were granted. |
| A working sync fails after HubSpot permissions change | Reconnect HubSpot, run catalog discovery again, and retry the sync. |
HubSpot documents the same installation permissions and OAuth behavior in Working with OAuth and Manage apps in HubSpot.
Embrasure stores encrypted OAuth access and refresh tokens, the HubSpot account ID, and the granted permission list. It does not store a HubSpot password or a customer-created private-app token. The connector reads CRM data and does not request write access to change HubSpot records.