Connect HubSpot
Authorizing the portal Auron reads from and writes to, and what that authorization covers.
A sync needs a HubSpot connection to run through, and the push step needs one to write through. Both use the same connection, made once by an owner or admin.
Connect the portal
From Settings under Integrations, choose Connect on HubSpot. You are sent to HubSpot to pick a portal and grant access, then returned to Auron. The connection is listed with the portal's domain so it is clear which HubSpot account it points at.
Auron asks for read and write access to contacts, companies and deals, and read access to their property definitions — the last of these is what lets the mapping screen list your real HubSpot fields, including custom ones, instead of asking you to type property names.
If this organization connected HubSpot before contacts were in the catalog, Disconnect and Connect again so HubSpot re-issues a token with the contact scopes. Existing connections keep working for companies and deals, but contact syncs and writes fail until that reconnect.
A HubSpot connection covers the whole portal
Unlike a storage connection, which is scoped to what one person can see, a HubSpot token authorizes the entire portal. Whoever connects grants Auron access to every contact, company and deal in it, not only the ones they own. Connect from an account you are comfortable delegating that access from.
What keeps working, and what breaks it
Access refreshes automatically, so a connection made once keeps working without anyone signing in again.
Syncs and push steps are bound to the specific connection they were created with. If that connection is removed, or access is revoked in HubSpot, its syncs pause with an error explaining why and stop running until the connection is restored. This is a visible failure by design: a sync silently returning nothing would look identical to a quiet CRM.
Before you create a sync
Two things are worth checking in HubSpot first.
The properties you want should already exist. Auron maps onto properties, it does not create them, so a custom field has to be created in HubSpot before it can be mapped.
A unique property, if you intend to push back to HubSpot for records that did not come from HubSpot. Writing needs a way to identify the object — Auron uses the HubSpot object id when a record came from a sync, but for anything else it needs a property marked unique in HubSpot, such as a company's domain.
Where this is managed
Connections live under Settings as Integrations. Once HubSpot is connected, continue to Create a sync.