Overview
Keeping HubSpot contacts, companies and deals in step with Auron entity records, in both directions.
The HubSpot integration keeps your CRM and Auron describing the same thing. Contacts, companies and deals flow into entity records on a schedule, and what Auron works out from meetings, calls and documents can be written back to HubSpot — with a person approving every write.
This is how a contact that was just added in HubSpot can be called by an agent, and how the summary of that call ends up on the contact instead of in someone's notes.
Two directions, treated differently
Inbound is a sync. You pick an object type, pick an entity, and say which HubSpot property fills which column. Auron copies the values across on a schedule. It is a direct copy with no interpretation, so it runs on its own and costs no credits.
Outbound is a step in an automation. It never runs on a schedule of its own, and it never runs unreviewed: the step pauses, shows an approver the exact fields and values it is about to send, and only writes if they approve.
The asymmetry is deliberate. Reading from HubSpot changes nothing outside Auron. Writing to HubSpot changes the system your revenue team runs on.
What a sync does
Each sync is bound to one connection, one HubSpot object type, and one entity. The first run reads the whole object type; every run after that asks HubSpot only for what changed since the last one, so a portal with fifty thousand companies is read in full once rather than every day.
Two rules shape the result. One HubSpot object produces one record, and a later run updates rather than duplicates: Auron remembers which record came from which HubSpot object, so the second time it sees a company it revises the record it made the first time, even if the company was renamed in between.
Records the sync creates carry a banner naming the sync and linking straight to the object in HubSpot, so it is always clear where a value came from.
Getting there
Connect HubSpot
An owner or admin connects the portal once for the organization. See Connect HubSpot.
Create a sync
Choose contacts, companies or deals, map properties onto entity columns, and set how often it runs. See Create a sync.
Push back to HubSpot
Add the push step to an automation and choose who approves its writes. See Push back to HubSpot.
Where this is managed
Syncs live in the console under HubSpot. The connection they run on is managed under Settings as Integrations, and the push step is configured inside an automation. Schedules, statuses, limits and permissions are collected in the Reference.
Early access
HubSpot is enabled per organization rather than being available to everyone by default. If you do not see it in your integrations list, ask your Auron contact to turn it on.
Contacts scopes
Syncing contacts needs extra HubSpot scopes (crm.objects.contacts and crm.schemas.contacts). Connections made before those scopes were added must Disconnect and Connect again, or HubSpot will refuse contact reads and writes.
To dogfood the contact outbound-call automation: create a contacts sync onto an entity that has Phone, Call summary and Call outcome columns, then enable the Call new HubSpot contacts template. The first run of a contacts sync is a backfill of existing contacts and does not place outbound calls; only contacts first seen after that backfill trigger the automation.