🏢
Companies in context
Import HubSpot companies into Supportbench with active-record controls, filters, and mapped properties.
Connect HubSpot CRM and Supportbench so support teams can work with synchronized company and contact context, export cases as HubSpot Tickets, and bring associated HubSpot notes back into the customer timeline.
Each synchronization direction is explicit. Administrators control private-app access, modes, filters, mappings, ticket stages, custom tables, and recovery actions per Supportbench tenant.
Keep CRM context and support execution connected without replacing either team’s system of record or adding a third-party synchronization service.
Import HubSpot companies into Supportbench with active-record controls, filters, and mapped properties.
Import contacts, update existing contacts, or optionally create and update HubSpot contacts.
Export eligible Supportbench cases into the selected HubSpot pipeline and open or closed stage.
Import notes from synchronized HubSpot Tickets into Supportbench as deduplicated activities.
Create a HubSpot private app for Supportbench and grant only the scopes required by the synchronization areas you plan to enable. In Supportbench, configure the connection while signed in to the correct tenant with permission to edit integrations.
Company synchronization should be configured before dependent contacts or ticket exports so HubSpot associations resolve to the correct Supportbench records.
Start with a least-privilege private app, validate the token, and then enable only the synchronization directions your teams need.
In HubSpot, create a private app for Supportbench and enable access to the CRM objects, properties, schemas, and associations you will synchronize.
Copy the private app token and store it securely. You will enter it once in the tenant-specific Supportbench connection settings.
Sign in to Supportbench and open Settings › Integrations › HubSpot.
Enter the private app token, save the configuration, then select Test Connection and confirm the expected HubSpot portal.
Select company, contact, and ticket modes; add filters and mappings; configure ticket stages; and assign any custom-object table slots.
Refresh schema choices, run the initial synchronization, review counters and connection health, and use failure notifications for repeated problems.
Contacts and ticket exports depend on an already-synchronized company. Validate company matching and representative field mappings before expanding the production dataset.
Each object has its own direction, eligibility rules, filters, mappings, and operational controls.
HubSpot companies import into Supportbench and retain their provider source identity. Administrators can synchronize active records only, apply property filters before import, map standard fields, and populate Supportbench company custom fields from HubSpot properties.
Choose import with create and update, import that updates existing contacts only, or import plus create and update in HubSpot. HubSpot associations resolve contacts to an already-synchronized company, and mapped custom properties can populate Supportbench contact fields.
Unsynchronized Supportbench cases within the configured lookback window can export after their related company is synchronized. Select the HubSpot ticket pipeline, open and closed stages, and map standard or custom case fields into the HubSpot ticket properties your CRM team uses.
Notes linked to synchronized HubSpot Tickets import into Supportbench activities. The shared synchronization identity prevents the same provider note from creating duplicate timeline activity during retries or later synchronization passes.
Use HubSpot properties, relationship order, and object-specific modes to keep each synchronized dataset intentional.
Apply filters before a company, contact, or custom-object record imports.
Provide multiple accepted values within one property-filter row.
Start from suggested HubSpot properties for common Supportbench fields.
Map company, contact, case, or Data Table fields to the HubSpot properties your teams maintain.
Synchronize company identity before dependent records.
Use connection health and targeted checks before a full resynchronization.
Configure up to six independent custom-object slots. Each slot selects one HubSpot schema and one authorized Supportbench Data Table, then defines whether rows associate through a company or contact.
The modern Supportbench settings experience encrypts the saved HubSpot private app token and does not return it to the browser. Configuration is tenant-specific and restricted to users who can edit integrations.
Open your HubSpot integration settings to configure the private app connection, or see how native integrations keep CRM and support workflows connected without plug-in sprawl.