Summary
HubSpot appears to be a supported data-source path for getting audience and contact information into TruAgents. The current app suggests this is not a raw file import. It is a provider-backed workflow that creates an integration, creates a data source, authenticates against HubSpot, and then maps incoming columns before importing contacts.Who this is for
Technical admins and operators connecting external systems to TruAgents.Where it fits in the product
- Contacts → Data Sources
- contact import, mapping, and later sync review
What this page should eventually cover
- what HubSpot objects or fields are relevant to TruAgents
- how authentication is established
- how imported data should be mapped into contact fields
- what to check before using imported contacts in segments or campaigns
Practical workflow
The current flow strongly suggests this sequence:- create or reuse a HubSpot integration
- create or reuse the associated data source
- authenticate with HubSpot
- inspect detected incoming columns
- map those columns into TruAgents fields
- import contacts and verify the result
Why HubSpot is different from a file upload
HubSpot still ends up in the broader data-source workflow, but it behaves more like a connected provider path than a one-off file. That means teams should think about:- authentication state
- repeatability of the import path
- how HubSpot field names map into TruAgents contact data
Good validation habits
- confirm the HubSpot connection is authenticated before debugging mapping
- review mapped email and name fields carefully
- verify imported contacts before building segments or campaigns on top of them
- remember that the data-source path is only as good as the source data coming from HubSpot
Common mistakes
- assuming provider authentication removes the need for mapping review
- treating the imported audience as campaign-ready without checking sample records
- blaming segmentation before checking HubSpot field mapping