Skip to main content
Support Articles
Feature Requests Documentation Status Dashboard

HubSpot Release Notes

  • Updated
Fivetran System User Fivetranner

July 2021link

We have added a new primary key column, _fivetran_id, to the EMAIL_SUBSCRIPTION_CHANGE table. Be sure to update your queries.

June 2021link

We have added the following new tables, to support HubSpot’s Marketing Email API:

  • MARKETING_EMAIL
  • MARKETING_EMAIL_CAMPAIGN
  • MARKETING_EMAIL_CONTACT
  • MARKETING_EMAIL_CONTACT_LIST

May 2021link

We now support incremental updates for the CONTACT_LIST_MEMBER table.

April 2021link

We have added two new metadata tables, PROPERTY and PROPERTY_OPTION, to sync the properties associated with the following objects:

  • company
  • contact
  • deal
  • line_item
  • product
  • ticket

March 2021link

We now re-sync the TICKET table if we find that the table hasn’t been synced in the last 24 hours because of the Tickets API limitations. We re-sync the table to ensure data integrity.

We have added two new tables, TICKET_PIPELINE and TICKET_PIPELINE_STAGE to support HubSpot’s pipelines object.

February 2021link

We have added a new column, meeting_outcome, to the ENGAGEMENT_MEETING table.

We have added a new column, is_merged, to the DEAL table to track merged deals. If you’d like to sync historical data for this column, re-sync the DEAL table.

January 2021link

We have added a new table, DEAL_STAGE which stores the dealstage properties data. Previously, we synced the dealstage data to the DEAL_PROPERTY_HISTORY table. The HubSpot API returns only the date_entered value. Use the date_entered and date_exited values to calculate the time_in value.

December 2020link

We have added a new child table, CALENDAR_TOPIC, to the CALENDAR_EVENT table.

We have added the following new columns to the OWNER table:

  • is_active
  • active_user_id
  • user_id_including_inactive

November 2020link

We have added the following new tables to support Hubspot’s Tickets API:

  • TICKET
  • TICKET_COMPANY
  • TICKET_CONTACT
  • TICKET_DEAL
  • TICKET_ENGAGEMENT
  • TICKET_PROPERTY_HISTORY

See our Service Hub schema for more information.

October 2020link

We now support future timestamp values in the ENGAGEMENT_MEETING table. If you previously synced future timestamp values, re-sync the table to ensure data integrity.

September 2020link

We have added a new sub-table, CALENDAR_USER, to the CALENDAR_EVENT table.

August 2020link

We have released a pre-built dbt package for HubSpot. Find the package in Fivetran’s dbt hub. Learn more about our dbt integration in our dbt Transformations documentation.

We now use webhooks to capture deletes for the COMPANY, CONTACT, and DEAL tables. We are gradually rolling out this new feature to all existing customers. If you’d like to enable this feature on your connector, contact our support team.

July 2020link

We have added a warning to your Fivetran dashboard that asks you to increase your sync frequency if your COMPANY and COMPANY_PROPERTY_HISTORY tables have huge recurring updates. Previously, if these tables had more than 9900 updates, we initiated a complete re-sync to prevent data integrity issues. The re-sync caused high MAR (monthly active rows) consumption. You can prevent these re-syncs and avoid impact on your MAR by increasing your sync frequency.

May 2020link

You can now configure your HubSpot connector using the Fivetran REST API. This feature is in BETA and is available only for Standard and Enterprise accounts.

April 2020link

We now support future timestamp values in the following tables:

  • CALENDAR_EVENT
  • COMPANY_PROPERTY_HISTORY
  • CONTACT_FORM_SUBMISSION
  • CONTACT_PROPERTY_HISTORY
  • DEAL_PROPERTY_HISTORY
  • EMAIL_SUBSCRIPTION_CHANGE
  • ENGAGEMENT
  • LINE_ITEM_PROPERTY_HISTORY
  • IDENTITY_PROFILE_IDENTITY

If you have previously synced future timestamp values, re-sync the tables to ensure data integrity.

March 2020link

We have added three new fields to the CONTACT table:

  • canonical_vid
  • merged_vids
  • profile_url

We have added three new tables:

  • CONTACT_MERGE_AUDIT
  • CONTACT_IDENTITY_PROFILE
  • IDENTITY_PROFILE_IDENTITY

August 2019link

  • We have added the column activityType to the ENGAGEMENT table.

July 2019link

We have added the table blocking feature to all HubSpot tables. You can now choose which tables you’d like to sync or omit from syncing. To select or deselect tables, go to the schema page of your Fivetran dashboard.

If you wish to sync a child table, you must also sync its parent table.

February 2019link

New fields in ENGAGEMENT_* tables will be synced automatically.

January 2019link

  • We have added the new column web_conference_meeting_id to the ENGAGEMENT_MEETING table.
    • We have also added the new column unknown_visitor_conversation to the ENGAGEMENT_CALL table.

September 2018link

We have added a new field, transcription_id, to the ENGAGEMENT_CALL table.

The HubSpot connector can now sync e-commerce data for your Sales Hub, including products and line items. We have added the following tables to support this feature:

  • PRODUCT
  • PRODUCT_PROPERTY_HISTORY
  • LINE_ITEM
  • LINE_ITEM_PROPERTY_HISTORY

August 2018link

We have added two new columns, attachedVideoOpened and attachedVideoWatched, to the ENGAGEMENT_EMAIL table.

July 2018link

We have added the media_processing_status column to the ENGAGEMENT_EMAIL table.

May 2018link

We have added two new fields, callee_object_type and callee_object_id, to the ENGAGEMENT_CALL table.

April 2018link

We will now re-sync the entire ENGAGEMENTS table when there are more than 10,000 changed records, because HubSpot can no longer complete incremental queries to the engagements endpoint when there are so many changed records.

Some HubSpot records have very old timestamps (for example,Jan 1 1970). These values no longer cause our syncs to fail.

We have added the following columns to the tables below:

TABLE COLUMN
ENGAGEMENT_META_EMAIL post_send_status
ENGAGEMENT_EMAIL recipient_drop_reasons

Related articles

Didn’t find what you need?

Contact support