We have added a warning to your Fivetran dashboard that asks you to increase your sync frequency if your
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.
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.
We now support future timestamp values in the following tables:
If you have previously synced future timestamp values, re-sync the tables to ensure data integrity.
We have added three new fields to the
We have added three new tables:
We are gradually rolling out a new feature to capture deletes via webhooks for the following tables:
To take advantage of the new feature, you will need to reconnect the connector and provide additional information in the required new fields in the setup form.
- We have added the column
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.
New fields in
ENGAGEMENT_* tables will be synced automatically.
- We have added the new column
- We have also added the new column
We have added a new field,
transcription_id, to the
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:
We have added two new columns,
attachedVideoWatched, to the
We have added the
media_processing_status column to the
We have added two new fields,
callee_object_id, to the
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: