HubSpot integration — two-way contact, company and deal sync

The HubSpot integration exists for teams that run HubSpot alongside Oneop — during a migration, or permanently with different teams in each tool — and need the two to agree about who a customer is.

What it does

Record sync. Contacts, companies and deals sync between Oneop and HubSpot in both directions, so a record updated in either system is reflected in the other.

Chatbot lookups. The chatbot builder includes HubSpot lookup blocks, so a bot conversation can pull a visitor’s HubSpot record mid-flow and branch on what it finds — useful when the system of record for an existing book of business is still HubSpot.

Widget package. A downloadable widget package is available for embedding Oneop chat where HubSpot-managed sites need it.

What syncs, in which direction

• Bi-directional: contacts, companies, deals.
• Read, from chat: record lookups inside chatbot flows.
• Not synced: tickets, invoices, tasks, marketing objects, custom HubSpot pipelines’ automation. The sync scope is the three core CRM objects.

Setup

Connect per workspace from the integrations settings with your HubSpot credentials. Credentials are stored per-tenant in Oneop’s integrations table, encrypted with AES-256-GCM — never in shared configuration.

What it does not do

• It is not a migration tool with field-mapping UI — for a one-time move, Oneop’s CSV import (22 record types, validation report, 30-minute rollback) is the better path.
• It does not sync HubSpot workflows, email marketing or reporting objects.

Related module and plan notes

Works with the CRM module, available on every plan. If you are evaluating replacing HubSpot outright rather than syncing with it, read the honest comparison: Oneop vs HubSpot.