You can now configure your Help Scout connector using the Fivetran REST API. This feature is in BETA and is available only for Standard and Enterprise accounts.
We now store all conversation events that occur between our data syncs. Previously, each sync only fetched the latest event for each conversation.
We do not receive the
customerWaitingSince object from webhooks. All
CONVERSATION_HISTORY records synced via webhooks will not have the following fields:
The Help Scout connector now supports priority-first sync. Priority-first syncs fetch your most recent data first so that it’s quickly ready for you to use. Help Scout’s priority-first syncs fetch the most recent 15 days of data from the
CONVERSATION_HISTORY tables and their subtables.
To learn more, see our priority-first sync documentation.
Version 1.0 of the Help Scout API is now deprecated. Version 2.0 of the Help Scout API has caused major changes in the schema. The new schema contains the following tables:
HAPPINESS_RATING, all tables have become history tables and have the word
HISTORY appended to indicate that.
Each history table has an
updated_at field which is a part of the primary key. When a record is updated, its
updated_at changes, and so does its primary key. Thus, the older record remains preserved as history.
We have temporarily removed two tables. Help Scout didn’t include an endpoint for these two tables in version 2.0 of their API. Once they add the endpoint, we will sync these two tables again:
We have increased the Help Scout API rate limit, allowing us to easily retry our API connections when failures occur.
CONVERSATION table, the custom field type
dropdown now contains the label value.
You can now view the list of your tables that are available for sync in your Fivetran dashboard.