Skip to main content

Import HubSpot emails

Quick start​

Connect HubSpot in NEXT, enable the Teamspace subscription for HubSpot emails, and let the scheduled sync import new CRM emails into NEXT as Highlights.

Why integrate with HubSpot emails?​

HubSpot emails often contain the written commercial context around a customer relationship: follow-ups, pricing discussions, rollout coordination, and objection handling. Importing those emails into NEXT makes that context searchable and analyzable next to surveys, reviews, support tickets, and call transcripts.

  • It surfaces CRM email conversations in the same workspace as direct customer feedback.
  • It helps teams compare what was discussed over email with what customers later say in support, research, and surveys.
  • It enriches imported highlights with related HubSpot deal metadata for filtering and explainability.

What gets imported​

  • Object in NEXT: Highlights
  • Source object: HubSpot emails
  • Sync model: Incremental daily import of newly recorded emails

For each imported email, NEXT stores the email subject and body as highlight text. When a related deal can be resolved, NEXT also adds these metadata tags from the first matching deal:

  • Deal phase
  • Pipeline
  • Deal size
  • Article

Authentication​

OAuth 2.0 through the HubSpot app connection in NEXT.

Connection notes​

  • Connect HubSpot in Settings -> Integrations and authorize the HubSpot account that contains the emails you want to analyze.
  • Create or update the Teamspace subscription for the HubSpot emails import.
  • The import also reads related deal data, associations, and owner team information so NEXT can resolve account IDs and support LIQE filtering.

Configuration notes​

  • The import fetches emails by hs_timestamp and only imports emails newer than the subscription import timestamp.
  • NEXT prefers the first direct HubSpot email -> company association to resolve the account ID.
  • If no direct company association exists, NEXT falls back to the first email -> deal -> associatedCompanyId path that can be resolved.
  • Emails without a resolvable account ID are still imported, but without account_id.

Filtering​

HubSpot Emails subscriptions support LIQE filters. For the syntax reference, see Use LIQE filters.

HubSpot Emails filters run against:

  • Top-level email fields such as id, createdAt, updatedAt, and archived
  • Every field in the HubSpot email properties payload, such as hs_timestamp, hs_email_subject, hs_email_text, hs_email_html, hs_email_direction, hs_email_message_id, and hubspot_owner_id
  • A derived numeric field: hs_email_body_plain_length
  • Association arrays exposed as associations.deal, associations.company, associations.contact, and associations.ticket
  • The resolved account company ID exposed as accountCompanyId
  • Related deal fields exposed as deal.*, including deal.id, deal.dealname, deal.dealstage, deal.amount, deal.closedate, deal.pipeline, deal.article, deal.hs_lastmodifieddate, and deal.associatedCompanyId
  • Related owner fields exposed as owner.*, including owner.id, owner.email, owner.firstName, owner.lastName, and owner.primaryTeam

For deal.pipeline, NEXT exposes the HubSpot pipeline label, for example Enterprise Pipeline, rather than the internal pipeline ID.

Examples:

  • hs_email_direction:INCOMING_EMAIL
  • hs_email_subject:"pricing"
  • hs_email_body_plain_length:>=200
  • associations.company:352660291804
  • hs_email_direction:EMAIL AND deal.pipeline:"Enterprise Pipeline"
  • owner.primaryTeam:"Enterprise Sales" AND deal.article:SKU-42

Limitations​

  • Emails without a direct or fallback account-company mapping are still imported without account_id.
  • If multiple direct company associations exist for an email, NEXT uses the first one returned by HubSpot.
  • Deal metadata tags come from the first related deal returned by HubSpot that NEXT can resolve.
  • hs_email_html is only used when hs_email_text is absent.
  • hs_email_direction is available for LIQE filtering but is not imported as a tag.
  • Owner-based filter fields may be unavailable if the authorized HubSpot app does not grant owner read scope.
  • NEXT uses the HubSpot email object ID as the stable highlight identifier.

Troubleshooting​

  • Reconnect the integration if HubSpot access has expired or the authorized portal changed.
  • Check that the authorized HubSpot app still has access to emails, deals, associations, and owners.
  • If expected emails are missing, verify that the email timestamp is newer than the subscription import timestamp and that the LIQE filter does not exclude it.

FAQ​

What is created in NEXT?​

NEXT creates Highlights, one per imported HubSpot email.

Is the email subject included?​

Yes. NEXT puts the subject above the email body in the imported highlight text.

What happens when HubSpot only returns HTML?​

NEXT converts hs_email_html to plain text and uses that when hs_email_text is missing.

Can I filter which emails are imported?​

Yes. Use the subscription LIQE filter to narrow imports by email metadata, direction, related deal data, or owner fields. See the Filtering section above for supported fields and examples.