Skip to main content

Hubspot Feedback Integration

Written by Vaishnavi [Enterpret]

Connect HubSpot to Enterpret to analyze feedback stored in HubSpot CRM records, including tickets, deals, leads, feedback submissions, activities, and supported custom objects.

Before you begin

You will need:

  • Access to an Enterpret account with permission to manage integrations

  • A HubSpot account with permission to approve OAuth access

  • Access in HubSpot to the objects and fields you want Enterpret to ingest

  • A clear idea of which HubSpot object should be the primary feedback source

Some HubSpot objects and fields require specific HubSpot permissions, product access, or plan access. If an object is missing during setup, confirm that the HubSpot account used for OAuth can access it.

Where to start depends on your onboarding status

If your tenant is already live, open the Integrations page from the left sidebar of your Enterpret workspace or go to https://dashboard.enterpret.com/<your-company>/settings/integrations/.

If your tenant is still in onboarding and the Integrations page is not active yet, go to https://dashboard.enterpret.com/<your-company>/onboard-tenant/add-integrations instead. This opens the Add Feedback Sources page, where you can choose HubSpot directly.

The post-onboarding /settings/integrations/ URL starts working once your tenant is active. Until then, use the onboarding URL above.

Connect HubSpot

  1. In Enterpret, open Integrations

  2. Click + New Integration.

  3. Select HubSpot. Click 'Continue'

  4. Choose Feedback Integration.

  5. Approve the HubSpot OAuth request.

  6. Choose the primary HubSpot object Enterpret should ingest.

  7. Select the HubSpot fields you want to sync.

  8. Mark which fields contain customer feedback and which fields should be used as metadata.

  9. Choose whether the feedback should be treated as a Conversation or Survey in Enterpret.

  10. Save the integration.

Enterpret starts ingestion after the HubSpot object and field mapping is saved. Authorizing HubSpot alone does not start ingestion.

If you are onboarding with the Enterpret team, you may be asked to authorize HubSpot first and then share the HubSpot objects, fields, and examples you want to ingest. Enterpret can help configure the mapping so the first sync matches your intended data shape.

Choose what to import

HubSpot setup is flexible because feedback can live in different objects for different teams.

Common setups include:

  • Tickets: support tickets and ticket fields

  • Deals: sales or lifecycle feedback stored on deal records

  • Leads: lead records and associated properties, when available in your HubSpot portal

  • Feedback submissions: structured HubSpot feedback responses such as survey-style responses

  • Notes, emails, calls, meetings, or tasks: customer interactions stored as HubSpot activity records

  • Custom objects: custom HubSpot objects your team uses to store feedback

You can also include associated objects. For example, if tickets are the primary object, you can include associated notes, emails, calls, contacts, companies, deals, or custom objects where they are available.

What gets synced

Enterpret syncs the HubSpot object and fields selected during setup.

For each synced record, Enterpret can include:

  • Selected fields from the primary HubSpot object

  • Selected fields from associated HubSpot objects

  • HubSpot record IDs

  • HubSpot record links

  • Created and updated timestamps

  • Selected metadata fields for filtering and analysis

For Conversation feedback, Enterpret creates a conversation from the fields marked as feedback. Activity records such as notes, emails, calls, meetings, and tasks can be added as conversation turns when selected.

For Survey feedback, each selected feedback field becomes a question-and-answer response.

Enterpret strips HTML formatting from rich text fields before analysis so the feedback text is easier to read and classify.

What happens after connecting

After setup is saved, Enterpret begins importing matching HubSpot records in batches. Initial sync time depends on the amount of HubSpot data, the selected primary object, and the number of selected fields or associations.

By default, Enterpret starts with recent historical data and continues syncing new and updated HubSpot records after the integration is active. If you need a longer historical backfill, contact Enterpret Support or your customer success manager.

Re-authorizing HubSpot

If HubSpot access is revoked, permissions change, or the integration shows an authentication error, reconnect HubSpot from the integration settings in Enterpret.

After re-authorization, confirm that the selected object and field mapping still matches the HubSpot data you want to ingest.


Troubleshooting

I authorized HubSpot but do not see data

HubSpot ingestion starts only after the object and field mapping is saved. Open the HubSpot integration in Enterpret and confirm that you selected a primary object, selected at least one field, and marked at least one field as feedback.

I do not see the HubSpot object I want to import

Confirm that the HubSpot account used for OAuth can access that object. Some objects, such as tickets, leads, feedback submissions, sales emails, or custom objects, may require additional HubSpot permissions, optional OAuth scopes, or plan access.

Some expected fields are missing

Confirm that the fields are active in HubSpot and available on the selected object. Archived HubSpot properties are not shown for selection.

Associated object data is missing

Confirm that the associated object type was selected during setup and that the HubSpot records are actually associated in HubSpot. If HubSpot does not return an association between two object types, Enterpret skips that association and continues syncing the primary record.

Notes, emails, calls, meetings, or tasks are missing

Activity records only sync when they are included in the integration mapping and associated with the selected primary object in HubSpot. Confirm that the activity type is selected and that the example HubSpot record has that activity attached.

I am using Notes as the primary source

Notes are best used as a primary source when the notes are not already covered by another HubSpot feedback integration. If notes are attached to deals, leads, or tickets that are already being ingested as feedback, Enterpret may capture those notes through the deal, lead, or ticket setup instead to avoid duplicate feedback.

New or updated HubSpot records are delayed

HubSpot records sync in batches based on updated timestamps. Large portals, many selected associations, or HubSpot API rate limits can make the initial sync or a large update take longer.

User or account matching looks lower than expected

Feedback ingestion and user or account matching are separate steps. Matching quality depends on the identifiers available in HubSpot, such as email, domain, company, contact, or account fields. If matching looks low, share example HubSpot records with Enterpret Support so we can check the available mapping fields.

FAQs

Does the HubSpot Feedback Integration import all HubSpot data automatically?

No. Enterpret imports the primary object, fields, and associated objects selected during setup. This keeps the integration focused on the feedback data you want analyzed.

Can I use HubSpot tickets, deals, and leads as separate feedback sources?

Yes. If your team wants to analyze tickets, deals, and leads separately, each source can be configured with its own HubSpot feedback setup and field mapping.

Can HubSpot feedback be modeled as a survey?

Yes. During setup, choose Survey when selected fields should be treated as question-and-answer responses. Choose Conversation when selected fields should be combined into a conversation-style feedback record.

Can I include custom HubSpot properties?

Yes. Enterpret can include supported custom properties that are available to the HubSpot account used for OAuth. You can mark custom properties as feedback or metadata during setup.

Why does Enterpret ask me to mark fields as feedback or metadata?

Fields marked as feedback are analyzed as customer voice. Fields marked as metadata are used for filtering, segmentation, attribution, and context.

Can I change the HubSpot mapping later?

Yes. You can update the integration mapping if the selected object, fields, or feedback type need to change. Historical reprocessing may require help from Enterpret Support.

Does HubSpot Feedback replace HubSpot user or account integrations?

No. HubSpot Feedback brings feedback records into Enterpret. HubSpot user and account data may be configured separately when your workspace needs HubSpot contacts or companies for user and account context.

Getting help

If you need help setting up or troubleshooting the HubSpot Feedback Integration, contact Enterpret Support with your workspace name, the HubSpot integration name, the primary object selected, and an example HubSpot record if available.

Did this answer your question?