Release Notes

July 2026

We have added two new tables, MESSAGE_OPEN and SERIES_DISENGAGEMENT.

We have added a new column, parent_id, to the ARTICLE_HISTORY table.

We have added a new table, ARTICLE_PARENT, to store the parent IDs associated with each article.

June 2026

We have added two new columns, url and custom_domain, to the HELP_CENTER_HISTORY table.

April 2026

We have added a new table, CONVERSATION_SOURCE_ATTACHMENT_HISTORY.

We have added a new column, statistics_adjusted_handling_time, to the CONVERSATION_HISTORY table.

March 2026

The Intercom connector now supports table re-syncs.

We have renamed the column away_mode_reassigned to away_mode_reassign in the ADMIN table to align with the Intercom API field name.

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

• applied_at
• applied_by_id
• applied_by_type
• tag_name

December 2025

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

• conversation_rating_contact_external_id
• conversation_rating_contact_id
• source_author_email
• source_author_name
• source_redacted

We have added the following columns to the CONTACT_HISTORY table:

• referrer
• utm_campaign
• utm_content
• utm_medium
• utm_source
• utm_term

These columns capture UTM marketing attribution parameters to help track campaign performance using a last-touch attribution model.

November 2025

We have added two new tables, CALL and CALL_TRANSCRIPT.

We are gradually rolling out this change to all existing connections.

We have added the Region drop-down menu to the connection setup form. You can now select one of US, EU, or AU as your Intercom region based on your Intercom app URL. For more information, see our Intercom setup guide.

October 2025

We unified each connector’s pre-built dbt Core–compatible data models into a single model. It standardizes and documents the Fivetran schemas created in your destination and outputs analytics-ready tables. Previously, most connectors used distinct source and transform models.

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

• app_package_code
• event_details_action_name
• event_details_action_result
• event_details_attribute_name
• event_details_event_result
• event_details_event_type
• event_details_value_name
• event_details_workflow_name
• state

We have added the following new tables:

• RECEIPT_RESPONSE
• SURVEY_ANSWER
• SURVEY_QUESTION

We are gradually rolling out this change to all existing connections.

We have added the email_message_metadata_subject column to the CONVERSATION_PART_HISTORY table.

We have added the child tables CONVERSATION_PART_TAG_HISTORY and EMAIL_ADDRESS_HEADER to the CONVERSATION_PART_HISTORY table.

September 2025

We have added a new column, messenger_writable, to the DATA_ATTRIBUTE table.

August 2025

We have made the following schema changes:

• Added a new table, TICKET_STATE.
• Added a new column, enabled_push_messaging, to the CONTACT_HISTORY table.
• Added a new column, app_package_code, to the TICKET_PART_HISTORY table.

July 2025

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

• ticket_state_internal_label
• ticket_state_external_label

Be sure to re-sync the connection to backfill the historical data for these columns.

October 2024

We now set the _fivetran_active column to false when you trigger a re-sync for the following tables.

• CONTACT_HISTORY
• CONVERSATION_HISTORY
• CONTACT
• CONTACT_COMPANY
• CONTACT_SEGMENT
• CONTACT_SUBSCRIPTION
• CONTACT_TAG
• CONTACT_SOCIAL_PROFILE
• CONVERSATION
• CONVERSATION_ADMIN
• CONVERSATION_CONTACT
• CONVERSATION_PART
• CONVERSATION_PART_ATTACHMENT
• CONVERSATION_TAG
• CONVERSATION_TOPIC_HISTORY

We set the _fivetran_active column to false before re-syncing the rows in these tables.

September 2024

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

• ai_agent_last_answer_type
• ai_agent_participated
• ai_agent_rating
• ai_agent_rating_remark
• ai_agent_resolution_state
• ai_agent_source_title
• ai_agent_source_type

We have added a new table, CONVERSATION_AI_AGENT_CONTENT_SOURCE with the following columns:

• content_type
• locale
• title
• url

To sync historical data, perform a connection re-sync or contact Fivetran support.

We are gradually rolling out these changes all existing connections.

October 2023

We now re-import the ARTICLE_HISTORY table in every sync due to limitations in the Intercom API. We perform a re-import to ensure data integrity.

We have upgraded our Intercom connector from Intercom API version 2.9 to 2.10. As part of the upgrade, we have made the following schema changes:

• We have added the following new tables:

  • HELP_CENTER_HISTORY
  • TICKET_CONTACT_HISTORY
  • TICKET_HISTORY
  • TICKET_LINK_HISTORY
  • TICKET_PART_ATTACHMENT_HISTORY
  • TICKET_PART_HISTORY
  • TICKET_TYPE_ATTRIBUTE_HISTORY
  • TICKET_TYPE_HISTORY

• We have deprecated the SECTION_HISTORY table.

• We have added a new column, help_center_id, to the COLLECTION_HISTORY table.

• We have deprecated the section_id column from the ARTICLE_HISTORY table.

We are gradually rolling out these changes to all existing connections.

July 2023

We have added the following new tables:

• ARTICLE_HISTORY
• COLLECTION_HISTORY
• COMPANY_SEGMENT_HISTORY
• CONTACT_DATA_EVENT
• CONTACT_SEGMENT_HISTORY
• CONTACT_SUBSCRIPTION_HISTORY
• DATA_ATTRIBUTE
• DATA_ATTRIBUTE_OPTION
• NEWS_ITEM_HISTORY
• NEWS_ITEM_LABEL_HISTORY
• NEWS_ITEM_REACTION_HISTORY
• NEWSFEED_ASSIGNMENT
• NEWSFEED_HISTORY
• SECTION_HISTORY
• SEGMENT
• SUBSCRIPTION_TYPE
• SUBSCRIPTION_TYPE_CONTENT_TYPE
• SUBSCRIPTION_TYPE_TRANSLATION

To sync the following tables, you must re-authenticate to grant Fivetran the necessary permissions:

• ARTICLE_HISTORY
• COLLECTION_HISTORY
• NEWS_ITEM_HISTORY
• NEWS_ITEM_LABEL_HISTORY
• NEWS_ITEM_REACTION_HISTORY
• NEWSFEED_ASSIGNMENT
• NEWSFEED_HISTORY
• SECTION_HISTORY

We have added the following new columns to the tables below:

• app_id column to the COMPANY table
• formatted_phone column to the CONTACT table
• statistics_* columns to the CONVERSATION table

We are gradually rolling out these changes to all existing connections.

We have made the following changes to our history tables:

• Added three new columns, _fivetran_active, _fivetran_start, and _fivetran_end
• Removed the _fivetran_deleted column

The history table changes are applicable to connections created after July 20, 2023. We will be rolling out these changes to all existing connections after October 31, 2023.

February 2023

We have upgraded our Intercom connector from Intercom API version 2.0 to 2.8. We have made the following schema changes:

• We now support the teammate object in the CONVERSATIONS table.
• We have added the title and team_assignee_id column to the CONVERSATIONS table.
• We have added the inbox_seat column to the ADMIN table.
• We now support conversation topics data.
• We have added support for custom conversation attributes.

July 2022

We have expanded the Create a connection and Update a connection endpoints of our REST API. Now you can authorize the Intercom connector by adding the auth section to payloads.

June 2022

We now re-import the COMPANY_HISTORY and COMPANY_TAG_HISTORY tables once a week. Previously, we re-imported the COMPANY_HISTORY and COMPANY_TAG_HISTORY tables once a day. We are gradually rolling out the new feature to all existing connections.

March 2021

For all new Intercom connections created after March 1, we will capture webhook events through the endpoint registered in our OAuth app. This change makes it simpler and faster to set up an Intercom connection. For existing Intercom connections, we will continue to capture webhook events through the Fivetan endpoint you registered in Intercom during setup.

January 2021

We have released pre-built, dbt Core-compatible data models for Intercom. Find the models in Fivetran's dbt hub or data models documentation. Learn more about our dbt Core integration in our Transformations for dbt Core documentation.

July 2020

We now support Intercom REST API V2.0.

April 2020

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

November 2018

We have released a new version of the Intercom connector, now with an improved schema. You can find additional information in our Intercom documentation.

Thanks to leveraging Intercom webhooks, we now support the delete function in the following tables:

• USER_HISTORY
• LEAD_HISTORY
• ADMIN
• TEAM
• SEGMENT_HISTORY
• TAG

July 2018

We have added the conversation_rating column to the CONVERSATION table.

May 2018

We have added three new columns to the COMPANY table:

• size
• website
• industry