Does Unify Read HubSpot Data in Real Time or Sync a Copy?
Unify syncs supported HubSpot data into corresponding records in your Unify workspace. Chat can also request information directly from the connected CRM. These are different access paths. After initial synchronization, incoming record changes are checked approximately every 15 minutes; record associations are refreshed daily. Neither cadence guarantees that every value appears immediately.
For ownership, open deals, and exclusions, identify which path supplied the answer before judging freshness. A directly requested HubSpot result and a stored Unify attribute can differ while synchronization or mapping reprocessing is still underway.
What does Unify bring into the workspace?
The HubSpot sync documentation describes incoming companies, contacts, and deals updating corresponding Unify records. Deals appear as opportunities, with company or person relationships when the corresponding HubSpot associations exist. Field mappings determine which HubSpot properties populate which Unify attributes and how existing values are handled. This is supported synchronization, not a complete replica of every HubSpot object.
Importing existing CRM information into Unify is separate from creating company records inside HubSpot. Outgoing creation depends on the relevant rule or explicit action. Seeing a HubSpot-derived company in Unify does not establish that a duplicate company was created in HubSpot.
How fresh is each access path?
The following table summarizes documented behavior, not measured test results or a delivery SLA. Large batches and background reprocessing can delay when changed values become visible.
| Path | Documented timing or behavior | What to check |
|---|---|---|
| Initial incoming sync | Can take several hours; exceptionally large CRMs can take a couple of days. | Whether initial processing has finished. |
| New or updated HubSpot records | Checked approximately every 15 minutes after initial sync. | Source change time, mapping, and pending processing. |
| Record associations | Refreshed by a daily sync. | The relationship as well as the individual records. |
| Direct CRM request in chat | Requests information from the connected CRM; no universal real-time latency is promised. | Requested source, intended record, and selected connection. |
A contact attribute and its company relationship need separate checks. The contact can reflect a change before an association catches up. Do not extend the record-check cadence into a promise that every relationship, exclusion, or downstream action updates within the same interval.
When does chat read directly from HubSpot?
The CRM chat guide says to name the CRM when requesting information directly from it. Specify HubSpot and identify the intended account or contact with enough detail to resolve ambiguity. Review the returned record rather than assuming a familiar company name identifies the correct destination.
Your connection preferences determine whether chat uses the workspace connection or a personal connection. Incoming HubSpot synchronization uses the workspace connection. Access to data already synchronized into Unify follows Unify workspace permissions. Requiring a personal HubSpot connection does not automatically restrict all stored Unify data to that person’s CRM visibility.
HubSpot authorization also needs careful interpretation: app access follows granted OAuth scopes and can extend beyond the connecting user’s record permissions. Personal authorization alone is therefore not evidence that the app can see only records that user owns. Review the authorized access and workspace permissions together.
Which plan and permissions apply?
The documentation identifies bidirectional syncs as Business-only and CRM work in chat as available on Pro and Business. The plan comparison separately labels Pro CRM access read-only and Business read/write. Do not treat chat access as proof that full background bidirectional synchronization or every write operation is enabled. Administrators must allow CRM writes in chat, and the authorized connection must support the requested operation.
What should you check when values differ?
- Connection: Follow the HubSpot integration setup to confirm the correct workspace account, active authorization, and enabled bidirectional syncs for that path.
- Identity: Check the source record and incoming mapping. A company needs a valid domain; a person needs a valid email. Confirm access to required fields.
- Read behavior: Do nothing leaves the Unify attribute unchanged. Fill if empty preserves an existing Unify value. A difference can therefore reflect the configured mapping.
- Processing: Allow initial sync, large batches, and mapping reprocessing to finish. Check associations separately from field changes.
If the discrepancy persists after processing catches up, retain the CRM record ID, field name, expected value, and change time for support. Compare one relevant source property with its mapped Unify attribute before changing several settings at once.
Why freshness matters for outreach
For inbound lead routing, review ownership and open-deal context before relying on an automated handoff. Sequence exclusions depend on applicable data reaching Unify; a CRM change cannot affect an exclusion before that synchronization occurs.
When Plays act on CRM-derived criteria, synchronization and trigger evaluation are separate stages. The trigger documentation describes recurring evaluation. Checking HubSpot directly in chat does not establish that a pending play or enrollment has already received the same change. Verify the state used by the workflow that will take action.
Frequently asked questions
Does Unify store HubSpot information in its workspace?
Yes. Supported HubSpot companies, contacts, and deals synchronize into corresponding Unify records according to mappings. That does not establish a full replica of every CRM object.
Are HubSpot updates guaranteed to appear within 15 minutes?
No. Approximately 15 minutes describes ongoing record checks. Large batches can take longer, and associations refresh daily.
Can chat request information directly from HubSpot?
Yes. Name HubSpot and identify the record clearly. The configured connection and its authorized access govern the request; no universal instantaneous response guarantee is documented.
Does a personal connection enforce my exact HubSpot record visibility?
Not necessarily. HubSpot OAuth app scopes can provide broader access than the connecting user’s record permissions. Already-synced data follows Unify workspace permissions.
Does a different value always mean synchronization failed?
No. Read mappings can preserve existing Unify values, and processing or association refreshes may still be pending. Check the mapped field, source record, connection, and timing first.
