December 2024

Connector SDK

PyPI package `fivetran-connector-sdk`

We have released version 0.12.12.1 of the PyPI package. This release adds the following:

Updated testers for the fivetran debug command with better-formatted logs.
An error message when attempting to deploy a connector with more than 100 configuration fields.
Automatic handling of port conflicts on your local machine.

We have released version 0.12.17.1 of the PyPI package. This release contains some minor improvements.

PyPI package `fivetran-api-playground`

We have released version 0.12.12.1 of the PyPI package. This release adds the following:

Export CSV endpoint for testing export APIs.
Authentication endpoints for testing the following types of authentication:
- HTTP basic
- HTTP bearer
- API key
- Session token

Fivetran Azure US Servers

We have added new servers in the Azure US West 3 (Phoenix) region.

If you're on a Business Critical plan, you can now select this region in your destination setup form. Connectors configured in a destination run in their designated cloud and region, meaning that your data doesn't leave our region-specific servers during processing. For example, if you configure your connectors to use our servers in the US, your data does not leave the US during processing.

For more information, see our data residency documentation.

Lite Connectors

Lite connectors are now available for the following sources:

Sunset Service

Chartio

We no longer support Chartio as a BI tool for Fivetran-managed BigQuery destinations.

Transformations for dbt Core

Updated dbt Quickstart packages

We have updated the Quickstart packages for the following connectors:

Fivetran Log to version 1.10.0
Greenhouse to version 0.8.0
LinkedIn Ad Analytics to version 0.10.0
Mailchimp to version 0.10.0
Marketo to version 0.12.1
Quickbooks to version 0.17.0
Shopify to version 0.14.0
Stripe to version 0.15.1
Tiktok Ads to version 0.7.0
Twilio to version 0.4.0
Zendesk Support to version 0.19.1

We have also updated the Quickstart package for the Ad Reporting multi-connector data model to version 1.10.0.

Updated format for user-defined dbt jobs and Quickstart transformations

We have updated the format of logs and webhooks for user-defined dbt jobs and Quickstart transformations.

New connectors

AWS Cost and Usage Reports

AWS Cost and Usage Reports is a tool to track and extract your cost and usage metrics.

Read our AWS Cost and Usage Reports connector documentation.

Schema changes

Ada

Effective December 18, 2024 we use a new December 2024 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migrations article for more details.

We have made these schema changes for more efficient data management and retrieval.

4 total changes • 0 possible breaking changes

Table/column	Change type	New name
`CONVERSATION`
column	New Column	`generated_topic_v_2_desc`
column	New Column	`generated_topic_v_2_id`
column	New Column	`generated_topic_v_2_parent_id`
column	New Column	`generated_topic_v_2_title`

Aircall

Effective December 19, 2024 we use a new December 2024 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migrations article for more details.

We have made these schema changes to improve schema usability.

2 total changes • 0 possible breaking changes

Table/column	Change type	New name
`CALL`
column	New Column	`sid`
`USER_AVAILABILITY`
table	New Table

Apple App Store

We have added the date column to the SALES_SUBSCRIPTION_SUMMARY table.

For all existing connectors, we will perform a free historical re-sync of the SALES_SUBSCRIPTION_SUMMARY table to populate it with data. See the Apple App Store connector's latest ERD for more details.

Assembled

Effective December 19, 2024 we use a new December 2024 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migrations article for more details.

We made this schema change to add a new column.

1 total changes • 0 possible breaking changes

Table/column	Change type		Old name	New name	Notes
`EVENT_CHANGE`
column	New Column			`event_id`

Backbone PLM

Effective December 19, 2024 we use a new December 2024 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migrations article for more details.

We are making these schema changes to resolve data integrity issues.

You should review the changes and update your downstream queries if necessary. Failing to do so may lead to missing or incomplete data in your data pipelines.

16 total changes • 16 possible breaking changes

Table/column	Change type	Old name	New name	Notes
`BOM_DIVIDER`
column	Primary Key Change	`id` 🔑	`id`	No longer primary key.
column	Primary Key Change		`index` 🔑	New primary key.
`BOM_ITEM_COLORWAY`
column	Discontinued Column	`bom_item_id` 🔑		No longer primary key.
column	Primary Key Change	`custom_color` 🔑	`custom_color`	No longer primary key.
column	Primary Key Change		`bom_item_index` 🔑	New primary key.
column	Primary Key Change		`index` 🔑	New primary key.
`BOM_ITEM_COMPONENT_TECHPACK_IMAGE`
column	Discontinued Column	`bom_item_id` 🔑		No longer primary key.
column	Primary Key Change	`image` 🔑	`image`	No longer primary key.
column	Primary Key Change		`bom_item_index` 🔑	New primary key.
column	Primary Key Change		`index` 🔑	New primary key.
`BOM_ITEM_COMPONENT_VARIANT`
column	Discontinued Column	`bom_item_id` 🔑		No longer primary key.
column	Primary Key Change		`bom_item_index` 🔑	New primary key.
`BOM_ITEM_DETAIL`
column	Primary Key Change	`id` 🔑	`id`	No longer primary key.
column	Primary Key Change		`index` 🔑	New primary key.
`BOM_ITEM_TECHPACK_IMAGE`
column	Primary Key Change	`image` 🔑	`image`	No longer primary key.
column	Primary Key Change		`index` 🔑	New primary key.

Brevo

Effective December 9, 2024 we use a new December 2024 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migrations article for more details.

These schema changes are required to adhere to standard naming conventions.

You should review the changes and update your downstream queries if necessary. Failing to do so may lead to missing or incomplete data in your data pipelines.

2 total changes • 2 possible breaking changes

Table/column	Change type	Old name	New name
`EMAIL_CAMPAIGN`
column	Rename Column	`tag`	`tags`
`EMAIL_TEMPLATE`
column	Rename Column	`tag`	`tags`

Chameleon

Effective December 9, 2024 we use a new December 2024 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migrations article for more details.

We have made the following changes to adhere to standard naming conventions.

You should review the changes and update your downstream queries if necessary. Failing to do so may lead to missing or incomplete data in your data pipelines.

2 total changes • 2 possible breaking changes

Table/column	Change type	Old name	New name
`EXPERIENCE_DELIVERY`
column	Rename Column	`from`	`from_date`
`USER_PROFILE`
column	Rename Column	`percent`	`percents`

Chargebee Product Catalog 2.0

Effective December 5, 2024 we use a new December 2024 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migrations article for more details.

We are making these schema changes to introduce feature enhancements.

33 total changes • 0 possible breaking changes

Table/column	Change type	New name
`CREDIT_NOTE_LINE_ITEM`
column	New Column	`reference_line_item_id`
`INVOICE_DUNNING_ATTEMPT`
column	New Column	`transaction_amount`
column	New Column	`transaction_status`
`INVOICE_LINKED_PAYMENT`
column	New Column	`transaction_amount`
column	New Column	`transaction_date`
column	New Column	`transaction_status`
`QUOTE`
table	New Table	`QUOTE`
`QUOTE_DISCOUNT`
table	New Table	`QUOTE_DISCOUNT`
`QUOTE_LINE_ITEM`
table	New Table	`QUOTE_LINE_ITEM`
`QUOTE_LINE_ITEM_DISCOUNT`
table	New Table	`QUOTE_LINE_ITEM_DISCOUNT`
`QUOTE_LINE_ITEM_ITER`
table	New Table	`QUOTE_LINE_ITEM_ITER`
`QUOTE_LINE_ITEM_TAX`
table	New Table	`QUOTE_LINE_ITEM_TAX`
`QUOTE_NOTE`
table	New Table	`QUOTE_NOTE`
`QUOTE_SUBSCRIPTION`
table	New Table	`QUOTE_SUBSCRIPTION`
`QUOTE_SUBSCRIPTION_ADDON`
table	New Table	`QUOTE_SUBSCRIPTION_ADDON`
`QUOTE_SUBSCRIPTION_COUPON`
table	New Table	`QUOTE_SUBSCRIPTION_COUPON`
`QUOTE_SUBSCRIPTION_DISCOUNT`
table	New Table	`QUOTE_SUBSCRIPTION_DISCOUNT`
`QUOTE_SUBSCRIPTION_EVENT_BASED_ADDON`
table	New Table	`QUOTE_SUBSCRIPTION_EVENT_BASED_ADDON`
`QUOTE_SUBSCRIPTION_ITEM`
table	New Table	`QUOTE_SUBSCRIPTION_ITEM`
`QUOTE_SUBSCRIPTION_ITEM_ITER`
table	New Table	`QUOTE_SUBSCRIPTION_ITEM_ITER`
`QUOTE_TAX`
table	New Table	`QUOTE_TAX`
`SUBSCRIPTION`
column	New Column	`active_id`
column	New Column	`changes_scheduled_at`
column	New Column	`contract_term_total_contract_value_before_tax`
column	New Column	`shipping_address_index`
`SUBSCRIPTION_DISCOUNT`
table	New Table	`SUBSCRIPTION_DISCOUNT`
`SUBSCRIPTION_ITEM_PRICE`
column	New Column	`billing_period`
column	New Column	`billing_period_unit`
column	New Column	`charge_once`
column	New Column	`free_quantity_in_decimal`
column	New Column	`proration_type`
column	New Column	`trial_end`
column	New Column	`usage_accumulation_reset_frequency`

Collibra

Effective December 19, 2024 we use a new December 2024 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migrations article for more details.

We have made these schema changes to improve schema usability.

You should review the changes and update your downstream queries if necessary. Failing to do so may lead to missing or incomplete data in your data pipelines.

10 total changes • 9 possible breaking changes

Table/column	Change type	Old name	New name	Notes
`ASSIGNMENT_ASSET`
table	Discontinued Table	`ASSIGNMENT_ASSET`		Data available in the `ASSIGNMENT_ASSET_TYPE` table.
`ASSIGNMENT_ASSET_ARTICULATION_RULE`
table	Discontinued Table	`ASSIGNMENT_ASSET_ARTICULATION_RULE`		Data available in the `ASSIGNMENT_ASSET_TYPE_ARTICULATION_RULE` table.
`ASSIGNMENT_ASSET_CHARACTERISTIC_TYPE`
table	Discontinued Table	`ASSIGNMENT_ASSET_CHARACTERISTIC_TYPE`		Data available in the `ASSIGNMENT_ASSET_TYPE_CHARACTERISTIC_TYPE` table.
`ASSIGNMENT_ASSET_DATA_QUALITY_RULE`
table	Discontinued Table	`ASSIGNMENT_ASSET_DATA_QUALITY_RULE`		Data available in the `ASSIGNMENT_ASSET_TYPE_DATA_QUALITY_RULE` table.
`ASSIGNMENT_ASSET_DOMAIN_TYPE`
table	Discontinued Table	`ASSIGNMENT_ASSET_DOMAIN_TYPE`		Data available in the `ASSIGNMENT_ASSET_TYPE_DOMAIN_TYPE` table.
`ASSIGNMENT_ASSET_STATUS`
table	Discontinued Table	`ASSIGNMENT_ASSET_STATUS`		Data available in the `ASSIGNMENT_ASSET_TYPE_STATUS` table.
`ASSIGNMENT_ASSET_TYPE`
column	New Column		`scope_id`	Column added to establish a relationship with the `SCOPE_COMMUNITY` and `SCOPE_DOMAIN` tables.
`ASSIGNMENT_ASSET_VALIDATION_RULE`
table	Discontinued Table	`ASSIGNMENT_ASSET_VALIDATION_RULE`		Data available in the `ASSIGNMENT_ASSET_TYPE_VALIDATION_RULE` table.
`ASSIGNMENT_SCOPE_COMMUNITY`
table	Discontinued Table	`ASSIGNMENT_SCOPE_COMMUNITY`		Data available in the `SCOPE_COMMUNITY` table.
`ASSIGNMENT_SCOPE_DOMAIN`
table	Discontinued Table	`ASSIGNMENT_SCOPE_DOMAIN`		Data available in the `SCOPE_DOMAIN` table.

dbt Cloud

Effective December 11, 2024 we use a new November 2024 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migrations article for more details.

We have made these schema changes to improve schema usability.

You should review the changes and update your downstream queries if necessary. Failing to do so may lead to missing or incomplete data in your data pipelines.

2 total changes • 1 possible breaking changes

Table/column	Change type	Old name	New name
`RUN`
column	Rename Column	`artifact_s3_path`	`artifact_s_3_path`
`RUN_ARTIFACT`
table	New Table		`RUN_ARTIFACT`

Facebook Pages

We have added two new metadata tables, PAGE_VIDEO_HISTORY and PAGE_VIDEO_THUMBNAILS.

For more information see Facebook's API docs.

Fivetran Platform Connector

We've added the TRANSFORMATION_RUNS table to sync Transformations usage data.

Freshchat

Effective December 9, 2024 we use a new December 2024 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migrations article for more details.

We are making these schema changes for more efficient data management and retrieval.

You should review the changes and update your downstream queries if necessary. Failing to do so may lead to missing or incomplete data in your data pipelines.

11 total changes • 6 possible breaking changes

Table/column	Change type	Old name	New name	Notes
`CHANNEL`
column	New Column		`bots_private_note`
column	New Column		`message_type`
column	New Column		`restrict_response`
`CHANNEL_TAG`
column	Rename Column	`tag`	`tags`	The previous name is a reserved word
`CHANNEL_WELCOME_MESSAGE`
column	Discontinued Column		`bots_private_note`	Column moved to the CHANNEL table
column	Discontinued Column		`message_type`	Column moved to the CHANNEL table
column	Discontinued Column		`restrict_response`	Column moved to the CHANNEL table
`CONVERSATION_PROPERTY`
table	New Table		`CONVERSATION_PROPERTY`
`CONVERSATION_PROPERTY_CHOICE`
table	New Table		`CONVERSATION_PROPERTY_CHOICE`
`OUTBOUND_MESSAGE`
table	Discontinued Table
`OUTBOUND_MESSAGE_PHONE_NUMBER`
table	Discontinued Table

Google Ads

We now support the following resources as custom reports:

We now support the following fields for the CAMPAIGN report:

segments.travel_destination_city
segments.travel_destination_country
segments.travel_destination_region
metrics.general_invalid_clicks
metrics.general_invalid_click_rate
campaign.brand_guidelines_enabled

We now support the following fields for the AD_GROUP report:

segments.travel_destination_city
segments.travel_destination_country
segments.travel_destination_region
ad_group.exclude_demographic_expansion

Google Analytics 4 Export

We've added the following columns to the EVENT table:

session_traffic_source_last_click
batch_event_index
batch_ordering_id
batch_page_id

Re-sync the connector to backfill the historical data for the new columns.

Google Display & Video 360

We've removed the following dimensions because they are no longer available in the Bid Manager API:

FILTER_PUBLISHER_PROPERTY
FILTER_PUBLISHER_PROPERTY_ID
FILTER_PUBLISHER_PROPERTY_SECTION
FILTER_PUBLISHER_PROPERTY_SECTION_ID

HubSpot

Effective December 20, 2024 we use a new December 2024 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migrations article for more details.

7 total changes • 0 possible breaking changes

Table/column	Change type	New name
`INVOICE`
table	New Table	`INVOICE`
`INVOICE_COMPANY`
table	New Table	`INVOICE_COMPANY`
`INVOICE_CONTACT`
table	New Table	`INVOICE_CONTACT`
`INVOICE_DEAL`
table	New Table	`INVOICE_DEAL`
`INVOICE_LINE_ITEM`
table	New Table	`INVOICE_LINE_ITEM`
`INVOICE_PROPERTY_HISTORY`
table	New Table	`INVOICE_PROPERTY_HISTORY`
`INVOICE_TICKET`
table	New Table	`INVOICE_TICKET`

Instagram Business

We've removed the video_views column from the MEDIA_INSIGHTS table.

We've also removed the following columns from the USER_INSIGHTS table:

email_contacts
get_direction_clicks
profile_views
text_message_clicks
website_clicks
phone_call_clicks

We made these changes because these metrics are no longer available in the Instagram API.

Jira Align

Effective December 3, 2024 we use a new December 2024 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migrations article for more details.

We have made this schema change to fix validation errors.

You should review the changes and update your downstream queries if necessary. Failing to do so may lead to missing or incomplete data in your data pipelines.

1 total changes • 1 possible breaking changes

Table/column	Change type		Old name	New name	Notes
`DEPENDENCY`
column	Rename Column		`isResponse_blocked`	`is_response_blocked`	We have made this change to fix validation errors.

JustCall

Effective December 5, 2024 we use a new December 2024 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migrations article for more details.

We have made these schema changes to improve schema usability.

You should review the changes and update your downstream queries if necessary. Failing to do so may lead to missing or incomplete data in your data pipelines.

118 total changes • 30 possible breaking changes

Table/column	Change type	Old name	New name
`CALL`
column	Discontinued Column	`agent_email`
column	Discontinued Column	`call_info_url`
column	Discontinued Column	`direction`
column	Discontinued Column	`disposition_code`
column	Discontinued Column	`duration`
column	Discontinued Column	`friendly_duration`
column	Discontinued Column	`ivr_digit`
column	Discontinued Column	`ivr_digit_description`
column	Discontinued Column	`justcall_agent`
column	Discontinued Column	`missed_call_type`
column	Discontinued Column	`notes`
column	Discontinued Column	`queue_callback_agent_picked`
column	Discontinued Column	`queue_callback_customer_picked`
column	Discontinued Column	`queue_callback_request_time_elapsed`
column	Discontinued Column	`queue_callback_ringing_time_elapsed`
column	Discontinued Column	`rating`
column	Discontinued Column	`recording`
column	Discontinued Column	`status`
column	Discontinued Column	`time`
column	Discontinued Column	`time_utc`
column	Discontinued Column	`type`
column	New Column		`agent_active`
column	New Column		`call_date`
column	New Column		`call_duration_conversation_time`
column	New Column		`call_duration_friendly_duration`
column	New Column		`call_duration_handle_time`
column	New Column		`call_duration_hold_time`
column	New Column		`call_duration_queue_wait_time`
column	New Column		`call_duration_ring_time`
column	New Column		`call_duration_total_duration`
column	New Column		`call_duration_wrap_up_time`
column	New Column		`call_info_direction`
column	New Column		`call_info_disposition`
column	New Column		`call_info_missed_call_reason`
column	New Column		`call_info_notes`
column	New Column		`call_info_rating`
column	New Column		`call_info_recording`
column	New Column		`call_info_recording_child`
column	New Column		`call_info_status`
column	New Column		`call_info_type`
column	New Column		`call_info_voicemail_transcription`
column	New Column		`call_sid`
column	New Column		`call_time`
column	New Column		`call_user_date`
column	New Column		`call_user_time`
column	New Column		`contact_email`
column	New Column		`cost_incurred`
column	New Column		`forward_info_datetime`
column	New Column		`forward_info_from_number`
column	New Column		`forward_info_to_number`
column	New Column		`ivr_info_content`
column	New Column		`ivr_info_digit_pressed`
column	New Column		`justcall_ai_call_score`
column	New Column		`justcall_ai_call_score_parameters_call_etiquette`
column	New Column		`justcall_ai_call_score_parameters_customer_sentiment_score`
column	New Column		`justcall_ai_call_score_parameters_de_escalation`
column	New Column		`justcall_ai_call_score_parameters_dead_air_time`
column	New Column		`justcall_ai_call_score_parameters_empathy`
column	New Column		`justcall_ai_call_score_parameters_filler_word`
column	New Column		`justcall_ai_call_score_parameters_greeting`
column	New Column		`justcall_ai_call_score_parameters_monologue_duration`
column	New Column		`justcall_ai_call_score_parameters_talk_listen_ratio`
column	New Column		`justcall_ai_call_score_parameters_words_per_minute`
column	New Column		`justcall_ai_call_summary`
column	New Column		`justcall_ai_customer_sentiment`
column	New Column		`justcall_ai_manual_call_score`
column	New Column		`justcall_line_name`
column	New Column		`queue_callback_attempted_time`
column	New Column		`queue_callback_reached`
column	New Column		`queue_callback_reached_duration`
column	New Column		`queue_callback_reached_time`
column	New Column		`queue_callback_requested_time`
column	New Column		`queue_callback_status`
column	New Column		`queue_callback_wait_duration`
column	New Column		`queue_entered_at_position`
column	New Column		`queue_exit_reason`
`CALL_AI_MOMENT`
table	New Table		`CALL_AI_MOMENT`
`CALL_AI_TAG`
table	New Table		`CALL_AI_TAG`
`CALL_INFO_TRAIT`
table	New Table		`CALL_INFO_TRAIT`
`SALE_DIALER_CAMPAIGN`
column	New Column		`default_number`
column	New Column		`type`
`SALES_DIALER_ANALYTIC`
table	New Table		`SALES_DIALER_ANALYTIC`
`SALES_DIALER_CALL`
table	New Table		`SALES_DIALER_CALL`
`SALES_DIALER_CALL_AI_MOMENT`
table	New Table		`SALES_DIALER_CALL_AI_MOMENT`
`SALES_DIALER_CALL_AI_TAG`
table	New Table		`SALES_DIALER_CALL_AI_TAG`
`TEXT`
column	Discontinued Column	`agent_name`
column	Discontinued Column	`body`
column	Discontinued Column	`is_mms`
column	Discontinued Column	`mms`
column	New Column		`contact_email`
column	New Column		`contact_number`
column	New Column		`cost_incurred`
column	New Column		`justcall_line_name`
column	New Column		`medium`
column	New Column		`sms_date`
column	New Column		`sms_info_body`
column	New Column		`sms_info_is_mms`
column	New Column		`sms_time`
column	New Column		`sms_user_date`
column	New Column		`sms_user_time`
`USER_GROUP`
table	New Table		`USER_GROUP`
`USER_OWNED_NUMBER`
table	New Table		`USER_OWNED_NUMBER`
table	New Table		`USER_OWNED_NUMBER`
`USER_SHARED_NUMBER`
table	New Table		`USER_SHARED_NUMBER`
`USERS`
column	Discontinued Column	`availability`
column	Discontinued Column	`firstname`
column	Discontinued Column	`last_login`
column	Discontinued Column	`lastname`
column	Discontinued Column	`owner_id`
column	New Column		`available`
column	New Column		`created_at`
column	New Column		`extention`
column	New Column		`last_login_timestamp`
column	New Column		`name`
column	New Column		`role`
column	New Column		`timezone`
column	New Column		`unavailability_reason`
column	New Column		`working_hours_type`

MNTN

Effective December 12, 2024 we use a new November 2024 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migrations article for more details.

We are making these changes to resolve data integrity issues caused by the MNTN API version update.

You should review the changes and update your downstream queries if necessary. Failing to do so may lead to missing or incomplete data in your data pipelines.

4 total changes • 2 possible breaking changes

Table/column	Change type	Old name	New name
`CONVERSION`
column	Discontinued Column	`campaign_group_id`
column	Discontinued Column	`channel_name`
column	New Column		`conversion_point`
column	New Column		`last_touch`

Notion

Effective December 19, 2024 we use a new December 2024 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migrations article for more details.

We are making this schema change to add a new column.

1 total changes • 0 possible breaking changes

Table/column	Change type		Old name	New name	Notes
`PAGE`
column	New Column			`in_trash`

Persona

Effective December 17, 2024 we use a new December 2024 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migrations article for more details.

We've made the following schema changes to improve schema usability.

2 total changes • 0 possible breaking changes

Table/column	Change type	New name
`INQUIRY`
column	New Column	`current_government_id`
column	New Column	`current_selfie`

Pingdom

Effective December 4, 2024 we use a new Decenber 2024 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migrations article for more details.

We are making these schema changes for more efficient data management and retrieval.

You should review the changes and update your downstream queries if necessary. Failing to do so may lead to missing or incomplete data in your data pipelines.

6 total changes • 6 possible breaking changes

Table/column	Change type	Old name	New name	Notes
`CHECK_DESCRIPTION`
column	Rename Column	`ipv6`	`ipv_6`
`CHECKS`
column	Rename Column	`ipv6`	`ipv_6`
`EMAIL`
column	Primary Key Change		`index` 🔑	New primary key
`PROBE`
column	Rename Column	`ipv6`	`ipv_6`
`SMS`
column	Primary Key Change		`index` 🔑	New primary key
`STATE`
column	Primary Key Change		`index` 🔑	New primary key

PostHog

Effective December 2, 2024 we use a new December 2024 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migrations article for more details.

We are making these schema changes to introduce feature enhancements.

4 total changes • 0 possible breaking changes

Table/column	Change type	New name
`COHORT`
column	New Column	`groups`
`COHORT_PERSON`
table	New Table	`COHORT_PERSON`
`SESSION`
table	New Table	`SESSION`
`SESSION_RECORDING`
table	New Table	`SESSION_RECORDING`

Retently

Effective December 17, 2024 we use a new December 2024 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migrations article for more details.

December 17, 2024: Migration window begins. Additions and Phase 1 changes take effect. You can manually start the update in your Fivetran dashboard.

January 17, 2025: Migration window closes. If you haven't already started the update manually, Fivetran will apply the remaining changes automatically.

We are making these schema changes to improve schema usability.

You should review the changes and update your downstream queries if necessary. Failing to do so may lead to missing or incomplete data in your data pipelines.

21 total changes • 16 possible breaking changes

Table/column	Change type	Old name	New name	Notes
`COMPANY_TAG`
table	New Table		`COMPANY_TAG`
`CUSTOMER_PROPERTY`
column	Discontinued Column	`_fivetran_id` 🔑		No longer primary key.
column	Primary key Change	`customer_id`	`customer_id` 🔑	Added to primary key.
column	Primary key Change		`index` 🔑	New primary key.
`CUSTOMER_TAG`
table	New Table		`CUSTOMER_TAG`
`FEEDBACK_ADDITIONAL_QUESTION`
column	Discontinued Column	`_fivetran_id` 🔑		No longer primary key.
column	Primary key Change	`feedback_id`	`feedback_id` 🔑	Added to primary key.
column	Primary key Change		`index` 🔑	New primary key.
`FEEDBACK_NOTE`
column	Discontinued Column	`_fivetran_id` 🔑		No longer primary key.
column	Primary key Change	`feedback_id`	`feedback_id` 🔑	Added to primary key.
column	Primary key Change		`index` 🔑	New primary key.
`FEEDBACK_RESPONSE_TAG`
table	New Table		`FEEDBACK_RESPONSE_TAG`
`FEEDBACK_TAG`
table	New Table		`FEEDBACK_TAG`
`OUTBOX_ADDITIONAL_RECIPIENT`
column	Discontinued Column	`_fivetran_id` 🔑		No longer primary key.
column	Primary key Change	`customer_id`	`customer_id` 🔑	Added to primary key.
column	Primary key Change		`index` 🔑	New primary key.
`OUTBOX_CUSTOMER_TAG`
table	New Table		`OUTBOX_CUSTOMER_TAG`
`REPORT_TREND`
column	Discontinued Column	`_fivetran_id` 🔑		No longer primary key.
column	Primary key Change	`report_campaign_id`	`report_campaign_id` 🔑	Added to primary key.
column	Primary key Change		`index` 🔑	New primary key.
`TAGS`
table	Discontinued Table	`TAGS`		Data now available in the `COMPANY_TAG`, `CUSTOMER_TAG`, `FEEDBACK_RESPONSE_TAG`, `FEEDBACK_TAG`, and `OUTBOX_CUSTOMER_TAG` tables.

REVIEWS.io

Effective December 9, 2024 we use a new December 2024 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migrations article for more details.

This schema change is required due to a data integrity issue.

1 total changes • 0 possible breaking changes

Table/column	Change type		Old name	New name	Notes
`REVIEW_AND_QUESTION`
column	New Column			`nps`

Rocketlane

Effective December 12, 2024 we use a new November 2024 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migrations article for more details.

We are making these changes to improve schema usability.

You should review the changes and update your downstream queries if necessary. Failing to do so may lead to missing or incomplete data in your data pipelines.

36 total changes • 3 possible breaking changes

Table/column	Change type	Old name	New name	Notes
`PROJECT`
column	New Column		`allocated_minute`
column	New Column		`billable_hour`
column	New Column		`billable_minute`
column	New Column		`currency_code`
column	New Column		`currency_name`
column	New Column		`currency_symbol`
column	New Column		`external_reference_id`
column	New Column		`financial_subscription_contract_frequency`
column	New Column		`financial_subscription_contract_no_of_periods`
column	New Column		`financial_subscription_contract_period_budget`
column	New Column		`financial_subscription_contract_period_minute`
column	New Column		`financial_subscription_contract_start_date`
column	New Column		`non_billable_hour`
column	New Column		`non_billable_minute`
column	New Column		`percentage_budget_consumed`
column	New Column		`tracked_minute`
`TASK`
column	New Column		`billable`
column	New Column		`csat_enabled`
column	New Column		`external_reference_id`
column	New Column		`parent_task_id`
column	New Column		`parent_task_name`
column	New Column		`phase_id`
column	New Column		`phase_name`
column	New Column		`priority_label`
column	New Column		`priority_value`
column	New Column		`task_private_note`
column	New Column		`time_entry_category_id`
column	New Column		`time_entry_category_name`
`TASK_DEPENDENCY`
column	Discontinued Column	`task_id` 🔑		No longer primary key
column	Primary Key Change		`task_dependency_id` 🔑	New primary key
column	Primary Key Change		`TASK_id` 🔑	New primary key
`TIME_ENTRY`
column	New Column		`bill_rate`
column	New Column		`bill_rate_currency`
column	New Column		`cost_rate`
column	New Column		`cost_rate_currency`
column	New Column		`status`

Sage Intacct

We have added existing columns, location_id and department_id, to the composite primary key in the USERRESTRICTION table.

SAP Business ByDesign

We have added a new column, SALES_ORDER_UUID to the following tables.

SALES_ORDER_ITEM_PRODUCT_TAX_DETAILS
SALES_ORDER_ITEM_SCHEDULE_LINE
SALES_ORDER_PRICE_COMPONENT

Shopify

We have added the following new tables:

APP
CATALOG
DISPUTE
PRODUCT_PUBLICATION
PUBLICATION
RETURN
RETURN_LINE_ITEM

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

Perform resync of ORDER table to fetch historical data for RETURN and RETURN_LINE_ITEM

We will re-import the remaining tables and their child tables daily to capture updates and deletes.

Shopware

Effective December 5, 2024 we use a new December 2024 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migrations article for more details.

We are making these schema changes to improve schema usability.

You should review the changes and update your downstream queries if necessary. Failing to do so may lead to missing or incomplete data in your data pipelines.

3 total changes • 1 possible breaking changes

Table/column	Change type	Old name	New name	Notes
`PRODUCT_ATTRIBUTE_CHEAPEST_PRICE`
table	New Table		`PRODUCT_ATTRIBUTE_CHEAPEST_PRICE`
`PRODUCT_ATTRIBUTE_PRICE`
table	New Table		`PRODUCT_ATTRIBUTE_PRICE`
`PRODUCT_PRICE`
table	Discontinued Table	`PRODUCT_PRICE`		Data now available in the `PRODUCT_ATTRIBUTE_PRICE` and `PRODUCT_ATTRIBUTE_CHEAPEST_PRICE` tables.

Squarespace

Effective December 5, 2024 we use a new December 2024 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migrations article for more details.

We've made the following changes to ensure data integrity.

You should review the changes and update your downstream queries if necessary. Failing to do so may lead to missing or incomplete data in your data pipelines.

1 total changes • 1 possible breaking changes

Table/column	Change type		Old name	New name	Notes
`INTERNAL_NOTE`
column	Primary Key Change		`orders_id`	`orders_id` 🔑	Added to primary key.

Stripe

We've added the COUPON_PRODUCT table with two columns, coupon_id and product_id, to support mapping between the COUPON and PRODUCT tables.

Taboola

We've added the following columns to the ACCOUNT table:

default_platform
country
currency

We've added the following columns to the CAMPAIGN table:

bid_strategy
branding_text
campaign_item_type
campaign_profile
cpa_goal
end_date_in_utc
is_spend_guard_active
learning_state
marketing_objective
min_expected_conversions_for_cpa_goal
pricing_model
roas_goal
safety_rating
start_date_in_utc
target_cpa
traffic_allocation_ab_test_end_date
type

Teads

Effective December 4, 2024 we use a new December 2024 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migrations article for more details.

We've made these schema changes to ensure alignment with development framework best practices.

You should review the changes and update your downstream queries if necessary. Failing to do so may lead to missing or incomplete data in your data pipelines.

42 total changes • 7 possible breaking changes

Table/column	Change type	Old name	New name	Notes
`REPORT_BUDGET`
column	Primary Key Change	`_fivetran_id` 🔑	`_fivetran_id` 🔑	We've changed the way we calculate the primary key.
column	New Column		`advertiser_updated_at`
column	New Column		`campaign_updated_at`
column	New Column		`creative_updated_at`
column	New Column		`line_group_updated_at`
column	New Column		`line_item_updated_at`
`REPORT_DISPLAY_PROGRESS`
column	Primary Key Change	`_fivetran_id` 🔑	`_fivetran_id` 🔑	We've changed the way we calculate the primary key.
column	New Column		`advertiser_updated_at`
column	New Column		`campaign_updated_at`
column	New Column		`creative_updated_at`
column	New Column		`line_group_updated_at`
column	New Column		`line_item_updated_at`
`REPORT_LUMEN`
column	Primary Key Change	`_fivetran_id` 🔑	`_fivetran_id` 🔑	We've changed the way we calculate the primary key.
column	New Column		`advertiser_updated_at`
column	New Column		`campaign_updated_at`
column	New Column		`creative_updated_at`
column	New Column		`line_group_updated_at`
column	New Column		`line_item_updated_at`
`REPORT_MOAT`
column	Primary Key Change	`_fivetran_id` 🔑	`_fivetran_id` 🔑	We've changed the way we calculate the primary key.
column	New Column		`advertiser_updated_at`
column	New Column		`campaign_updated_at`
column	New Column		`creative_updated_at`
column	New Column		`line_group_updated_at`
column	New Column		`line_item_updated_at`
`REPORT_SCOPE`
column	Primary Key Change	`_fivetran_id` 🔑	`_fivetran_id` 🔑	We've changed the way we calculate the primary key.
column	New Column		`advertiser_updated_at`
column	New Column		`campaign_updated_at`
column	New Column		`creative_updated_at`
column	New Column		`line_group_updated_at`
column	New Column		`line_item_updated_at`
`REPORT_VIDEO`
column	Primary Key Change	`_fivetran_id` 🔑	`_fivetran_id` 🔑	We've changed the way we calculate the primary key.
column	New Column		`advertiser_updated_at`
column	New Column		`campaign_updated_at`
column	New Column		`creative_updated_at`
column	New Column		`line_group_updated_at`
column	New Column		`line_item_updated_at`
`REPORT_VIDEO_PROGRESS`
column	Primary Key Change	`_fivetran_id` 🔑	`_fivetran_id` 🔑	We've changed the way we calculate the primary key.
column	New Column		`advertiser_updated_at`
column	New Column		`campaign_updated_at`
column	New Column		`creative_updated_at`
column	New Column		`line_group_updated_at`
column	New Column		`line_item_updated_at`

Workday Financial Management

Effective December 17, 2024 we use a new December 2024 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migrations article for more details.

We have added a new column, revenue_category_id, to the CUSTOMER_INVOICE_LINE and CUSTOMER_INVOICE_ADJUSTMENT_LINE_DATA tables with a foreign key reference to the REVENUE_CATEGORYtable.

2 total changes • 0 possible breaking changes

Table/column	Change type	New name	Notes
`CUSTOMER_INVOICE_ADJUSTMENT_LINE_DATA`
column	New Column	`revenue_category_id`	The new column supports the mapping between the `CUSTOMER_INVOICE_ADJUSTMENT_LINE_DATA` and `REVENUE_CATEGORY` tables.
`CUSTOMER_INVOICE_LINE`
column	New Column	`revenue_category_id`	The new column supports the mapping between the `CUSTOMER_INVOICE_LINE` and `REVENUE_CATEGORY` tables.

Xactly

Effective December 20, 2024 we use a new December 2024 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migrations article for more details.

We are making these schema changes to introduce a feature enhancement.

6 total changes • 0 possible breaking changes

Table/column	Change type	New name
`RATE_TABLE`
table	New Table	`RATE_TABLE`
`RATE_TABLE_TIER`
table	New Table	`RATE_TABLE_TIER`
`RATE_TIER_VALUE`
table	New Table	`RATE_TIER_VALUE`
`TITLE`
table	New Table	`TITLE`
`TITLE_CATEGORY`
table	New Table	`TITLE_CATEGORY`
`USER_ROLE`
table	New Table	`USER_ROLE`

Zip

Effective December 19, 2024 we use a new December 2024 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migrations article for more details.

This schema change is required to resolve the null primary key issue.

You should review the changes and update your downstream queries if necessary. Failing to do so may lead to missing or incomplete data in your data pipelines.

2 total changes • 2 possible breaking changes

Table/column	Change type	Old name	New name	Notes
`VENDOR_EXTERNAL_DATA`
column	Primary Key Change	`id` 🔑	`id`	No longer primary key
column	Primary Key Change		`index` 🔑	New primary key

Improvements

Adyen

Our Adyen connector is now generally available. Read our Adyen documentation.

Affinity

We have added table re-sync support. Previously, we only supported connector-level re-syncs.

You can now select and deselect tables to be synced on the Schema tab of the connector details page in your Fivetran dashboard.

Amazon Ads

The Amazon Ads connector now supports the Hybrid Deployment model. For more information, see our setup instructions

Apache Kafka

The Apache Kafka connector now supports the Hybrid Deployment model. For more information, see our setup instructions.

Autodesk BIM 360

We have added table re-sync support. Previously, we only supported connector-level re-syncs.

You can now select and deselect tables to be synced on the Schema tab of the connector details page in your Fivetran dashboard.

Azure Blob Storage

We have improved the setup experience for Azure Blob Storage connectors. New connectors created on or after December 20, 2024, will have the following changes in the connector setup form:

Added a new configuration option, Run connection test to perform an intermediate test during configuration
Added a new configuration option, Preview Files, to perform an intermediate test during configuration
Added support for displaying fields based on the file type
Added a new field, Quote character, to use an enclosing character
Reorganised fields to make the setup form more intuitive
Removed Infer as an option from the File Type field
Removed the Enable Advanced Options toggle
Changed the Null Sequence field to a toggle
For the Delimiter character(s) field, we now use , as the default value
For the Line Separator field, we now use \n as the default value

For more information, see our setup instructions and REST API configuration.

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

Azure DevOps

Our Azure DevOps connector is now generally available.

Read our Azure DevOps connector documentation.

BigQuery destination

We now support the following BigQuery dataset locations:

Region	Code
Columbus, Ohio	us-east5
Dallas	us-south1
Santiago	southamerica-west1
Toronto	northamerica-northeast2
Madrid	europe-southwest1
Milan	europe-west8
Paris	europe-west9
Berlin	europe-west10
Turin	europe-west12
Doha	me-central1
Dammam	me-central2
Tel Aviv	me-west1
Johannesburg	africa-south1

Confluent Cloud

The Confluent Cloud connector now supports the Hybrid Deployment model. For more information, see our setup instructions.

Databricks

We now support IAM role authentication to authorize S3 buckets associated with Databricks destinations configured for Hybrid Deployment. We are gradually rolling out this change to all existing destinations.

Dropbox Sign

We have added table re-sync support. Previously, we only supported connector-level re-syncs.

You can now select and deselect tables to be synced on the Schema tab of the connector details page in your Fivetran dashboard.

Email

We have added a new configuration option, Primary Key used for file process and load, in the connector setup form to support syncing files with custom primary keys. You can now select the custom primary keys during the connector configuration and use them to update or insert new rows in your destination. We process the most recently modified files to your destination. For more information, see our setup instructions.

Eventbrite

We have added table re-sync support. Previously, we only supported connector-level re-syncs.

You can now select and deselect tables to be synced on the Schema tab of the connector details page in your Fivetran dashboard.

Everhour

We now incrementally sync the ASSIGNMENT table.

We also re-import this table once a week to capture updates and deletes.

Facebook Ads

The Facebook Ads connector now supports the Hybrid Deployment model. For more information, see our setup instructions.

Flexport

We have added table re-sync support. Previously, we only supported connector-level re-syncs.

You can now select and deselect tables to be synced on the Schema tab of the connector details page in your Fivetran dashboard.

Float

We have added table re-sync support. Previously, we only supported connector-level re-syncs.

You can now select and deselect tables to be synced on the Schema tab of the connector details page in your Fivetran dashboard.

Freshsales

We have changed our sync strategy and now incrementally sync the CONTACT table and its child tables to capture updates and deletes. Previously, we re-imported the table.

Gainsight Customer Success

We now capture deletes for all standard and custom objects in Gainsight Customer Success. We are gradually rolling out this change to all existing connectors.

Google Ads

We now support Google Ads v18.

Google Cloud Storage

We have improved the setup experience for Google Cloud Storage connectors. New connectors created on or after December 20, 2024, will have the following changes in the connector setup form:

Added a new configuration option, Run connection test to perform an intermediate test during configuration
Added a new configuration option, Preview Files to perform an intermediate test during configuration
Added support for displaying fields based on the file type
Added a new field, Quote character, to use an enclosing character
Reorganised fields to make the setup form more intuitive
Removed Infer as an option from the File Type field
Removed the Enable Advanced Options toggle
Changed the Null Sequence field to a toggle
For the Delimiter character(s) field, we now use , as the default value
For the Line Separator field, we now use \n as the default value

For more information, see our setup instructions and REST API configuration.

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

Google Display & Video 360

The Google Display & Video 360 connector now supports the Hybrid Deployment model. For more information, see our setup instructions.

Google Drive

We have improved the setup experience for Google Drive connectors. New connectors created on or after December 21, 2024, will have the following changes in the connector setup form:

Added a new configuration option, Run connection test to perform an intermediate test during configuration
Added a new configuration option, Preview Files to perform an intermediate test during configuration
Added support for displaying fields based on the file type
Added a new field, Quote character, to use an enclosing character
Reorganised fields to make the setup form more intuitive
Removed Infer as an option from the File Type field
Removed the Enable Advanced Options toggle
Changed the Null Sequence field to a toggle
For the Delimiter character(s) field, we now use , as the default value
For the Line Separator field, we now use \n as the default value

For more information, see our setup instructions and REST API configuration.

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

Gorgias

We made the following changes to the sync strategy:

We now incrementally sync all tables and their child tables during every sync.
we now re-import all tables and their child tables once a week to capture updates and deletes.

Healthie

We now re-import the USERS table once a week to capture updates and deletes.

Heroku Kafka

The Heroku Kafka connector now supports the Hybrid Deployment model. For more information, see our setup instructions.

HubSpot

We have added a new field, Historical sync time frame, to the connector setup form. This allows you to select how many months' worth of historical data you want to sync. For an existing connector, you can edit the connection details and set the time frame value. For more information, see our Historical sync time frame documentation.

We apply the historical sync limit to the following tables only:

CUSTOM_EVENT
EMAIL_EVENT
EVENT

We are gradually rolling out this feature to all connectors.

HubSpot will sunset the Contact List V1 APIs on May 2025. For all connectors created on or after December 13, 2024, we will use the V3 APIs to sync data to the CONTACT_LIST and CONTACT_LIST_MEMBER tables. For more information, see Hubspot documentation. We are gradually rolling out these changes to all existing connectors.

JustCall

We now sync only the last one day's worth of data for the following tables during each incremental sync.

CALL
SALE_DIALER_CAMPAIGN
SALES_DIALER_CALL
TEXT

We now sync only the last 4 hours' worth of data for the SALES_DIALER_ANALYTIC table during each incremental sync.

Mode

We now re-import the REPORT_COLLECTION and REPORT_USING_DATA_SOURCE tables and their child tables once a week. See our Mode connector documentation for more details.

Notion

We have added table re-sync support. Previously, we only supported connector-level re-syncs.

You can now select and deselect tables to be synced on the Schema tab of the connector details page in your Fivetran dashboard.

Pardot

We have removed the optional Sync External Activities toggle from the connector setup form and now sync the EXTERNAL_ACTIVITY table if you provide the required scopes for the /external-activities endpoint. We make API calls to the endpoint to validate the scopes, and if the calls succeed, we sync the EXTERNAL_ACTIVITY table. For more information, see Pardot documentation.

You must continue to specify the Set up API rate limit for External Activities for the /external-activities endpoint.

If your schema change handling configuration settings is Allow all, we will sync the EXTERNAL_ACTIVITY table to your destination.

Persona

We made the following changes to the sync strategy:

We now incrementally sync the following tables and their child tables:
- ACCOUNT
- CASES
- INQUIRY
- LIST
- REPORT
- TRANSACTION
- USER_AUDIT_LOG
We now re-import the above tables and their child tables once a month to capture updates and deletes.

PowerReviews Enterprise

We have added table re-sync support. Previously, we only supported connector-level re-syncs.

You can now select and deselect tables to be synced on the Schema tab of the connector details page in your Fivetran dashboard.

Recurly

We have added table re-sync support. Previously, we only supported connector-level re-syncs.

You can now select and deselect tables to be synced on the Schema tab of the connector details page in your Fivetran dashboard.

Retently

We have added table re-sync support. Previously, we only supported connector-level re-syncs.

Revel Systems

We have added table re-sync support. Previously, we only supported connector-level re-syncs.

You can now select and deselect tables to be synced on the Schema tab of the connector details page in your Fivetran dashboard.

Rocketlane

We now re-import the following tables once a day to capture updates and deletes:

PROJECT
TASK
TIME_ENTRY

RTB House

We have added table re-sync support. Previously, we only supported connector-level re-syncs.

You can now select and deselect tables to be synced on the Schema tab of the connector details page in your Fivetran dashboard.

Ruddr

We now capture deletes for the ALLOCATION and TIME_ENTRY tables. We have also changed our sync strategy and now re-import the ALLOCATION and TIME_ENTRY tables once a week.

Salesforce

We have added a new toggle, Sync formula fields directly, to the connector setup form, with a default value of OFF. For an existing connector, you can click Edit connection in the Setup tab and enable or disable the toggle. Previously, this configuration (of syncing formula fields directly) was only possible via REST API.

This toggle allows you to sync formula fields directly. However, to maintain data integrity, we recommend using our transformation-based approach instead. Directly syncing formula fields can lead to data integrity issues, as outlined in the Sync limitations section.

Samsara

We have changed the sync strategy for the Samsara connector. We now re-import the VEHICLE table during every sync. Previously, we used to incrementally sync this table.

SFTP

We have updated the connection method for configuring a connector through REST API. We now use DIRECT and SSH_TUNNEL for configuration. Previously, we used direct and sshTunnel. For more information, see our REST API configuration.

SharePoint

We have improved the setup experience for Sharepoint connectors. New connectors created on or after December 20, 2024, will have the following changes in the connector setup form:

Added a new configuration option, Preview Files to perform an intermediate test during configuration
Added support for displaying fields based on the file type
Added a new field, Quote character, to use an enclosing character
Reorganised fields to make the setup form more intuitive
Removed Infer as an option from the File Type field
Removed the Enable Advanced Options toggle
Changed the Null Sequence field to a toggle
For the Delimiter character(s) field, we now use , as the default value
For the Line Separator field, we now use \n as the default value

For more information, see our setup instructions and REST API configuration.

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

Short.io

We have changed our sync strategy and now incrementally sync the LINK_STATISTICS and DOMAIN_STATISTICS tables. Previously, we re-imported these tables.

We no longer incrementally sync the LINK table.

We now re-import the DOMAIN_STATISTICS table once a week to capture updates and deletes.

Skilljar

We have added table re-sync support. Previously, we only supported connector-level re-syncs.

You can now select and deselect tables to be synced on the Schema tab of the connector details page in your Fivetran dashboard.

Snowflake

The Snowflake connector now supports the Hybrid Deployment model. For more information, see our setup instructions.

StackAdapt

We have added table re-sync support. Previously, we only supported connector-level re-syncs.

You can now select and deselect tables to be synced on the Schema tab of the connector details page in your Fivetran dashboard.

Stripe

The Stripe connector now supports the Hybrid Deployment model. For more information, see our setup instructions.

Trisolute

We have added table re-sync support. Previously, we only supported connector-level re-syncs.

You can now select and deselect tables to be synced on the Schema tab of the connector details page in your Fivetran dashboard.

Workable

We have changed our sync strategy and no longer re-import the CANDIDATE table and its child tables.

REST API Improvements

Delighted

We have added a new paramater, password, to the REST API configuration.

December 2024

Connector SDK

PyPI package fivetran-connector-sdk

PyPI package fivetran-api-playground

Fivetran Azure US Servers

Lite Connectors

Sunset Service

Chartio

Transformations for dbt Core

Updated dbt Quickstart packages

Updated format for user-defined dbt jobs and Quickstart transformations

New connectors

AWS Cost and Usage Reports

Schema changes

Ada

Aircall

Apple App Store

Assembled

Backbone PLM

Brevo

Chameleon

Chargebee Product Catalog 2.0

Collibra

dbt Cloud

Facebook Pages

Fivetran Platform Connector

Freshchat

Google Ads

Google Analytics 4 Export

Google Display & Video 360

HubSpot

Instagram Business

Jira Align

JustCall

MNTN

Notion

Persona

Pingdom

PostHog

Retently

REVIEWS.io

Rocketlane

Sage Intacct

SAP Business ByDesign

Shopify

Shopware

Squarespace

Stripe

Taboola

Teads

Workday Financial Management

Xactly

Zip

Improvements

Adyen

Affinity

Amazon Ads

Apache Kafka

Autodesk BIM 360

Azure Blob Storage

Azure DevOps

BigQuery destination

Confluent Cloud

Databricks

Dropbox Sign

Email

Eventbrite

Everhour

Facebook Ads

Flexport

Float

Freshsales

Gainsight Customer Success

Google Ads

Google Cloud Storage

Google Display & Video 360

Google Drive

Gorgias

Healthie

Heroku Kafka

PyPI package `fivetran-connector-sdk`

PyPI package `fivetran-api-playground`