October 2025

Connector SDK

`fivetran-connector-sdk` PyPI package

We have released version 2.3.1 of the fivetran-connector-sdk PyPI package. This release adds the following:

Previously, list objects required an explicit type definition within the schema() method. This release removes that limitation. Now, we automatically infer the list type values to JSON.
Minor improvements and enhancements.

We have released version 2.3.0 of the fivetran-connector-sdk PyPI package. This release adds the following:

Timeout handling for connector operations.
Minor improvements and enhancements.

Fivetran Connector SDK

The latest sync log events are now displayed at the top of the list on the Connector SDK Logs tab of the Connection Details page in the dashboard.

Fivetran Proxy Agent

Version 1.1.2

We released Fivetran Proxy Agent 1.1.2, which is bundled with High-Volume Agent version 6.1.0/88. The proxy_host and proxy_port configuration settings now apply to all agent communications, including connections to the Fivetran control service. Previously, these settings applied only to data source connections.

You can download the updated package from the Downloads page.

Lite Connectors

Lite connectors are now available for the following sources:

Logs

Extract Summary Event Now Includes SQL Query Count

The extract_summary log event for database connectors now includes SQL query count information, in addition to the API call count for API-based connectors. We are gradually rolling out this change to all existing connections.

See our extract_summary event documentation for more details.

Referencing users by ID instead of email address

We now reference users by unique ID instead of email address to improve data security. We updated the relevant BigQuery and Snowflake sample queries that join the LOG and USER tables.

Splunk Logging

We've updated the following field names in log messages we send to Splunk:

connector_id has been renamed to connection_id
connector_name has been renamed to connection_name

Partner SDK

SingleStore destination is in beta

The SingleStore destination is now in beta. For more information, see the Singlestore destination documentation.

Quickstart Package Updates

Quickstart data model package updates

v1.0.1

Bug Fixes

Removed extra tab spacing within the src_linkedin_pages.yml and stg_linkedin_pages.yml to resolve a potential error when persisting docs.

v1.0.1

Under the Hood

Resolved a dbt Fusion error around {% set abc = abc.append() %} in marketo__change_data_scd, as this syntax is valid only in dbt Core. We have opted for do instead of set.

v1.0.2

Bug Fixes

Changed snippet_published_at and status_publish_at from datetime to timestamp datatype to fix compatibility issues with Databricks SQL Warehouses (PR #29)

Under the Hood

Added integration testing step for Databricks SQL Warehouse.

v0.2.2

Under the Hood

Added _fivetran_deleted filter to stg_amazon_selling_partner__item_relationship model to exclude soft-deleted records and improve data quality, corresponding with the same update being added to the upstream connector.

v0.1.0

This is the initial release of the Unified RAG dbt package!

Under the Hood

Addition of the version: 2 tag within the src_rag_hubspot.yml file. (#16)
Resolved a dbt Fusion error around {% set abc = abc.append() %}, as this syntax is valid only in dbt Core. We have opted for do instead of set. (#32)

v1.1.1

Bug Fix

To handle changes to the property_attribution field JSON structure introduced in the September 2025 Fivetran Klaviyo release, updates the int_klaviyo__event_attribution model to handle both legacy and new structures
Ensures the property_attribution field is a string for parsing downstream by implementing the json_to_string macro to properly handle JSON columns across different warehouses

v1.1.0

Schema/Data Change

1 total change • 0 possible breaking changes

Data Model(s)	Change type	Old	New	Notes
All models	New column		`source_relation`	Identifies the source connection when using multiple GitHub connections

Feature Update

Union Data Functionality: This release supports running the package on multiple GitHub source connections. See the README for details on how to leverage this feature.

Tests Update

Removes uniqueness tests. The new unioning feature requires combination-of-column tests to consider the new source_relation column in addition to the existing primary key, but this is not supported across dbt versions.
- These tests will be reintroduced once a version-agnostic solution is available.

Under the Hood

Updates consistency tests to enable dynamic column exclusion.

v1.1.0

Bug Fixes

Performance optimization: Refactored int_intercom__conversation_part_events for customers with large intercom__conversation_part_history source tables:
- Consolidated redundant CTEs and eliminated unnecessary joins to reduce compute load and memory usage for larger source tables.
- Implemented single window function pass instead of multiple subqueries.
- Replicate IGNORE NULLS logic with first_value() window functions using custom ordering (case when condition then 0 else 1 end) to prioritize relevant events and naturally skip null values.
Data accuracy fix: Corrected the last_close_by_author_id window function logic that was incorrectly using ascending order instead of descending order, causing it to return the same value as first_close_by_author_id. The fix ensures proper chronological ordering to capture the actual last close event author.

Under the Hood

Created consistency and integrity tests for intercom__conversation_enhanced to validate that the above changes do not impact end model values.

v1.1.0

Schema/Data Change

7 total changes • 2 possible breaking changes

Data Model(s)	Change type	New	Notes
`netsuite2__entity_subsidiary_relationships`	New model		Unified view combining customer and vendor subsidiary relationships
`netsuite2__transaction_details`	New columns	`nexus_id` `nexus_country` `nexus_state` `tax_agency_id` `tax_agency_alt_name` `is_nexus_override` `is_tax_details_override` `tax_point_date` `is_tax_point_date_override`	Adds nexus-related tax information. Breaking change: If you already include any of these fields via the passthrough columns variable `transactions_pass_through_columns`, remove them from the list to avoid duplicate column errors.
`stg_netsuite2__nexuses`	New model		Provides access to Netsuite tax nexus data with configurable pass-through columns. See the README for instructions on adding the pass-through columns.
`stg_netsuite2__customer_subsidiary_relationships`	New model		Maps customers to their associated subsidiaries
`stg_netsuite2__vendor_subsidiary_relationships`	New model		Maps vendors to their associated subsidiaries
`stg_netsuite2__transactions`	New columns	`nexus_id` `is_nexus_override` `is_tax_details_override` `tax_point_date` `is_tax_point_date_override`	Adds nexus-related tax information. Breaking change: If you already include any of these fields via the passthrough columns variable `transactions_pass_through_columns`, remove them from the list to avoid duplicate column errors.
`stg_netsuite2__vendors`	New column	`entity_id`	For use in `netsuite2__entity_subsidiary_relationships`. Breaking change: If you already include this field via the passthrough columns variable `vendors_pass_through_columns`, remove it from the list to avoid duplicate column errors.
All models	New column	`source_relation`	Identifies the source connection when using multiple Netsuite connectors

Feature Update

Union Data Functionality: This release supports running the package on multiple Netsuite source connections. See the README for details on how to leverage this feature.
Entity-Subsidiary Relationships: New end model netsuite2__entity_subsidiary_relationships provides a unified view of both customer and vendor subsidiary relationships with enhanced metadata including currency information. Unions and enhances data from stg_netsuite2__customer_subsidiary_relationships and stg_netsuite2__vendor_subsidiary_relationships.
Nexus Support: Adds comprehensive support for Netsuite nexus data through new staging model stg_netsuite2__nexuses with configurable pass-through columns. See the README for instructions on how to configure them.
Adds Streamlit example to the README. See the README for more details.

Under the Hood

Updates integration tests configuration and seed data references
Updates the get_*_columns macros to return only the columns referenced by the corresponding staging model.

Contributors:

@jmongerlyra (PR #171)
@fivetran-poonamagate (PR #104)

v1.1.0

Schema Changes

4 total changes • 0 possible breaking changes

Data Model/Column	Change type	Old	New	Notes
`int_zendesk__ticket_work_time_business`	Materialization	Ephemeral	Table	This is intended to resolve potential timeout issues when running the `zendesk__ticket_metrics` model.
`int_zendesk__ticket_first_reply_time_business`	Materialization	Ephemeral	Table	This is intended to resolve potential timeout issues when running the `zendesk__ticket_metrics` model.
`int_zendesk__ticket_full_resolution_time_business`	Materialization	Ephemeral	Table	This is intended to resolve potential timeout issues when running the `zendesk__ticket_metrics` model.
`int_zendesk__ticket_first_resolution_time_business`	Materialization	Ephemeral	Table	This is intended to resolve potential timeout issues when running the `zendesk__ticket_metrics` model.

Feature Update

Materializes the above intermediate models as tables so as to optimize runs of zendesk__ticket_metrics and avoid potential timeout issues. (PR #216)
- If you would like to maintain the ephemeral materialization of these models and are running the Zendesk package via dbt Core, add the following configuration to your dbt_project.yml:

models:
  zendesk:
    agent_work_time:
      int_zendesk__ticket_work_time_business:
        +materialized: ephemeral
    reply_times:
      int_zendesk__ticket_first_reply_time_business:
        +materialized: ephemeral
    resolution_times:
      int_zendesk__ticket_full_resolution_time_business:
        +materialized: ephemeral
      int_zendesk__ticket_first_resolution_time_business:
        +materialized: ephemeral

Bug Fixes

Removes a filter in int_zendesk__updates that was erroneously filtering out some first reply messages. This filter was intended to remove "batched" chat messages stored in the TICKET_COMMENT table, but the filter is unnecessary (and in some cases problematic) for properly calculating downstream SLA metrics. (PR #216)
Creates the partition_by_source_relation() macro to dynamically include source_relation in the partition clauses of all window functions based on whether multiple Zendesk sources are being used. Previously, Redshift users running the package on one Zendesk connection may have encountered constant expression errors due to source_relation containing the same value across all records. (PR #219)
Updates the logic in int_zendesk__schedule_spine to accommodate 24/7 schedules. Previously, tickets with 24/7 schedules may have experienced gaps in business time metrics. (PR #218)
Updates calculations of sla_breach_at from the minute to second level to avoid potential rounding errors that may have caused discrepancies between Zendesk data models and UI reports. This adjustment has been made in the following intermediate models (PR #217):
- int_zendesk__agent_work_time_business_hours
- int_zendesk__agent_work_time_calendar_hours
- int_zendesk__reply_time_business_hours
- int_zendesk__reply_time_calendar_hours
- int_zendesk__requester_wait_time_business_hours
- int_zendesk__requester_wait_time_calendar_hours

Documentation

Renders a sample SLA Policy report from the Zendesk Streamlit App in the README. (PR #220)

v1.1.0

Schema/Data Change

11 total changes • 11 possible breaking changes

Data Model(s)	Change type	Old	New	Notes
shopify__customers or shopify_gql__customers	New Columns		`CUSTOMER` metafields	Disable by setting the `shopify_using_customer_metafields` and `shopify_using_all_metafields` variables to False.
shopify__daily_shop or shopify_gql__daily_shop	New Columns		`SHOP` metafields	Disable by setting the `shopify_using_shop_metafields` and `shopify_using_all_metafields` variables to False.
shopify__inventory_levels or shopify_gql__inventory_levels	New Columns		`PRODUCT_VARIANT` metafields	Disable by setting the `shopify_using_product_variant_metafields` and `shopify_using_all_metafields` variables to False.
shopify__orders or shopify_gql__orders	New Columns		`ORDER` metafields	Disable by setting the `shopify_using_order_metafields` and `shopify_using_all_metafields` variables to False.
shopify__products or shopify_gql__products	New Columns		`PRODUCT` metafields	Disable by setting the `shopify_using_product_metafields` and `shopify_using_all_metafields` variables to False.
shopify__collection_metafields or shopify_gql__collection_metafields	Default Enablement	Disabled	Enabled	The default value of `shopify_using_collection_metafields` is now True (previously False). Currently, `COLLECTION` metafields are not included in any other end models.
shopify__customer_metafields or shopify_gql__customer_metafields	Default Enablement	Disabled	Enabled	The default value of `shopify_using_customer_metafields` is now True (previously False).
shopify__order_metafields or shopify_gql__order_metafields	Default Enablement	Disabled	Enabled	The default value of `shopify_using_order_metafields` is now True (previously False).
shopify__product_metafields or shopify_gql__product_metafields	Default Enablement	Disabled	Enabled	The default value of `shopify_using_product_metafields` is now True (previously False).
shopify__product_variant_metafields or shopify_gql__product_variant_metafields	Default Enablement	Disabled	Enabled	The default value of `shopify_using_product_variant_metafields` is now True (previously False).
shopify__shop_metafields or shopify_gql__shop_metafields	Default Enablement	Disabled	Enabled	The default value of `shopify_using_shop_metafields` is now True (previously False).

Note: If you are running the package via Fivetran Quickstart, the shopify_using_[object]_metafields variables are automatically configured based on the presence of relevant source data in your warehouse.
Please refer to the README for more details on these variables.

Under the Hood

Adjusts seed data to test the incorporation of metafields.
Adds consistency validation tests for all GraphQL models.
Adds metafield variables to quickstart.yml to enable dynamic configuration in Fivetran Quickstart.

v1.0.0

Breaking Changes

Source Package Consolidation

Removed the dependency on the fivetran/quickbooks_source package.
- All functionality from the source package has been merged into this transformation package for improved maintainability and clarity.
- If you reference fivetran/quickbooks_source in your packages.yml, you must remove this dependency to avoid conflicts.
- Any source overrides referencing the fivetran/quickbooks_source package will also need to be removed or updated to reference this package.
- Update any quickbooks_source-scoped variables to be scoped to only under this package. See the README for how to configure the build schema of staging models.
As part of the consolidation, vars are no longer used to reference staging models, and only sources are represented by vars. Staging models are now referenced directly with ref() in downstream models.

Schema Updates

14 new models -- 14 potential breaking changes

NOTE: These models are not available to Quickstart users until we have validated tax lines work as expected. Please open a Fivetran support ticket if you'd like to try out the pre-release that contains tax line support. They are available for dbt Core customers only if you enable the appropriate variables (see the README for more details).

Data Model	Change Type	Notes
`stg_quickbooks__invoice_tax_line`	New Staging Model	Source: `invoice_tax_line` table. Disabled by default, leverage `using_invoice_tax_line` variable in `dbt_project.yml` to enable. (Once available in a future update, this will be dynamically handled for Quickstart users.)
`stg_quickbooks__journal_entry_tax_line`	New Staging Model	Source: `journal_entry_tax_line` table. Disabled by default, leverage `using_journal_entry_tax_line` variable in `dbt_project.yml` to enable. (Once available in a future update, this will be dynamically handled for Quickstart users.)
`stg_quickbooks__purchase_tax_line`	New Staging Model	Source: `purchase_tax_line` table. Disabled by default, leverage `using_purchase_tax_line` variable in `dbt_project.yml` to enable. (Once available in a future update, this will be dynamically handled for Quickstart users.)
`stg_quickbooks__refund_receipt_tax_line`	New Staging Model	Source: `refund_receipt_tax_line` table. Disabled by default, leverage `using_refund_receipt_tax_line` variable in `dbt_project.yml` to enable. (Once available in a future update, this will be dynamically handled for Quickstart users.)
`stg_quickbooks__sales_receipt_tax_line`	New Staging Model	Source: `sales_receipt_tax_line` table. Disabled by default, leverage `using_sales_receipt_tax_line` variable in `dbt_project.yml` to enable. (Once available in a future update, this will be dynamically handled for Quickstart users.)
`stg_quickbooks__tax_agency`	New Staging Model	Source: `tax_agency` table. Disabled by default, leverage `using_tax_agency` variable in `dbt_project.yml` to enable. (Once available in a future update, this will be dynamically handled for Quickstart users.)
`stg_quickbooks__tax_rate`	New Staging Model	Source: `tax_rate` table. Disabled by default, leverage `using_tax_rate` variable in `dbt_project.yml` to enable. (Once available in a future update, this will be dynamically handled for Quickstart users.)
`stg_quickbooks__invoice_tax_line_tmp`	New Temp Model	Source: `invoice_tax_line` table. Enabled by default, leverage `using_invoice_tax_line` variable in `dbt_project.yml` to disable. (Once available in a future update, this will be dynamically handled for Quickstart users.)
`stg_quickbooks__journal_entry_tax_line_tmp`	New Temp Model	Source: `journal_entry_tax_line` table. Disabled by default, leverage `using_journal_entry_tax_line` variable in `dbt_project.yml` to enable. (Once available in a future update, this will be dynamically handled for Quickstart users.)
`stg_quickbooks__purchase_tax_line_tmp`	New Temp Model	Source: `purchase_tax_line` table. Disabled by default, leverage `using_purchase_tax_line` variable in `dbt_project.yml` to enable. (Once available in a future update, this will be dynamically handled for Quickstart users.)
`stg_quickbooks__refund_receipt_tax_line_tmp`	New Temp Model	Source: `refund_receipt_tax_line` table. Disabled by default, leverage `using_refund_receipt_tax_line` variable in `dbt_project.yml` to enable. (Once available in a future update, this will be dynamically handled for Quickstart users.)
`stg_quickbooks__sales_receipt_tax_line_tmp`	New Temp Model	Source: `sales_receipt_tax_line` table. Disabled by default, leverage `using_sales_receipt_tax_line` variable in `dbt_project.yml` to enable. (Once available in a future update, this will be dynamically handled for Quickstart users.)
`stg_quickbooks__tax_agency_tmp`	New Temp Model	Source: `tax_agency` table. Disabled by default, leverage `using_tax_agency` variable in `dbt_project.yml` to enable. (Once available in a future update, this will be dynamically handled for Quickstart users.)
`stg_quickbooks__tax_rate_tmp`	New Temp Model	Source: `tax_rate` table. Disabled by default, leverage `using_tax_rate` variable in `dbt_project.yml` to enable. (Once available in a future update, this will be dynamically handled for Quickstart users.)

Bug Fixes

Corrected the int_quickbooks__invoice_double_entry model to accurately map bundled invoice lines to the correct amount, converted_amount, account_id, index, and class_id.

Under the Hood

Updated seed files to ensure accurate representation of invoice bundles.
Updated run_models.sh to execute for when the new variables are enabled.
Updated general_ledger_amounts_match integrity test to properly validate general ledger amounts.
Excluded the running_balance and cumulative_running_balance values from the consistency_general_ledger validation test as these results can change based on how the window function orders transactions on the same date.

Transformations for dbt

Automated Quickstart schema changes

We now automatically upgrade Quickstart Data Models to the latest version after a 30-day notification period. Once notified via email and in your dashboard, you have 30 days to prepare and review for each upgrade. This ensures you always have access to the most recent features and schema improvements.

We add new output models to Quickstarts by default for new customers. Existing customers can choose to automatically allow or block new output models.

Minor patch updates (e.g., vx.x.1 to vx.x.2) will continue to be applied immediately and do not follow the 30-day upgrade window.

Fivetran data model consolidation

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.

New connectors

Workday Adaptive Planning

Workday Adaptive Planning provides budgeting, forecasting, reporting, and analytics for businesses of all sizes.

Read our Workday Adaptive Planning connector documentation.

Schema changes

Adobe Workfront

Effective October 3, 2025 we use a new October 2025 schema. Review the latest ERD to better understand the schema changes.

We are updating the connector schema to support a feature enhancement.

1 total changes • 0 possible breaking changes

Table/column	Change type		Old name	New name	Notes
`TASK_CUSTOM_VALUE`
table	New Table			`TASK_CUSTOM_VALUE`

Amazon DSP

We have added the following new tables:

AD_CREATIVE
AD_CREATIVE_AD_GROUP_ASSOCIATION
AD_CREATIVE_FORMAT_PROPERTY_AD_COPY
AD_CREATIVE_FORMAT_PROPERTY_ASSET
AD_CREATIVE_FORMAT_PROPERTY_CLICK_ACTION
AD_CREATIVE_FORMAT_PROPERTY_CREATIVE_SIZE
AD_CREATIVE_FORMAT_PROPERTY_PRODUCT
AD_CREATIVE_FORMAT_PROPERTY_TRACKING_URL
AD_CREATIVE_MODERATION_AD_EXPERIENCE
AD_GROUP
AD_GROUP_ADVERTISED_PRODUCT_CATEGORY
AD_GROUP_BUDGET_CAP
AD_GROUP_FEE
AD_GROUP_FREQUENCY
ADVERTISED_PRODUCT_CATEGORY
CAMPAIGN_CONVERSION_TRACKING_PRODUCT
CAMPAIGN_LIST
CAMPAIGN_LIST_BUDGET_CAP
CAMPAIGN_LIST_FLIGHT
CAMPAIGN_LIST_FREQUENCY
INVENTORY_SOURCE_EXCHANGE
THIRD_PARTY_TARGET_SEGMENT

We have discontinued the following tables:

CREATIVE
CREATIVE_ASSOCIATION_LINE_ITEM
CREATIVE_IMAGE
CREATIVE_IMAGE_SEARCH_KEYWORD
CREATIVE_IMAGE_SEARCH_PRODUCT_ASIN
CREATIVE_IMAGE_THIRD_PARTY_CLICK_TRACKER
CREATIVE_IMAGE_THIRD_PARTY_TRACKER
CREATIVE_SUPPORTED_LINE_ITEM
CREATIVE_THIRD_PARTY_TRACKER
CREATIVE_VIDEO
CREATIVE_VIDEO_THIRD_PARTY_TRACKER
CUSTOM_CONTEXTUAL_SEGMENT
GOAL_CONFIGURATION
GOAL_CONFIGURATION_AVAILABLE_KPI
MODERATION_CREATIVE
MODERATION_CREATIVE_ADDITIONAL_NOTE
MODERATION_CREATIVE_REASON
ORACLE_DATA_CLOUD_PREDICT
ORDER_AUTO_OPTIMIZATION
ORDER_BUDGET_CAP
ORDER_BUDGET_FLIGHT
ORDER_CONVERSION_TRACKING_PIXEL
ORDER_CONVERSION_TRACKING_PRODUCT
ORDER_LINE_ITEM
ORDER_LINE_ITEM_BUDGET_CAP
ORDERS
PIXEL
PIXEL_PURPOSE
PRODUCT_CATEGORY
REC_ALLOWED_FORMAT
REC_ALLOWED_SIZE
REC_ASSOCIATED_PRODUCT
REC_CONTENT_BACKGROUND
REC_CREATIVE
REC_THIRD_PARTY_CLICK_TRACKER
REC_THIRD_PARTY_TRACKER
SUPPLY_SOURCE
THIRD_PARTY_CREATIVE

We have added the following columns to the composite primary key for the tables below:

TABLE	COLUMN(S)	NOTES
`APP`	`profile_id`, `advertiser_id`	Added to primary key.
`DOMAIN_LIST`	`profile_id`	Added to primary key.
`IAB_CONTENT_CATEGORY`	`profile_id`	Added to primary key.

Amazon Selling Partner

We have added the MARKETPLACE_PARTICIPATION table.

We are gradually rolling out this change to all connections.

AppsFlyer

We have added a new table, CREATIVE_REPORT, for connections configured to sync Data Locker events. This table will not contribute to your MAR until November 30, 2025.

Azure DevOps

We have added the following new tables:

INSTALLED_EXTENSION_CONTRIBUTION_AUTHENTICATION_SCHEMA
INSTALLED_EXTENSION_CONTRIBUTION_CONSTRAINT
INSTALLED_EXTENSION_CONTRIBUTION_RESTRICTED
INSTALLED_EXTENSION_CONTRIBUTION_TARGET
INSTALLED_EXTENSION_CONTRIBUTION_TYPE
INSTALLED_EXTENSION_CONTRIBUTION
INSTALLED_EXTENSION_FILE
INSTALLED_EXTENSION_SCOPE
INSTALLED_EXTENSION
PROCESS_WORK_ITEM_TYPE_STATE
PROCESS_WORK_ITEM_TYPE
PROCESS
WORK_ITEM_RELATION

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

access_level_account_license_type
access_level_assignment_source
access_level_git_hub_license_type
access_level_license_display_name
access_level_licensing_source
access_level_msdn_license_type
access_level_status_message
access_level_status

Braze

We have made the following changes:

Added a new column, preheader, to the MESSAGE_VARIATION table
Added a new table, USER_PUSH_TOKEN

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

short_url
url
user_agent
user_phone_number

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

content_length
endpoint_url
host
http_status_code
is_terminal
raw_response
retry_count
url_path
webhook_duration
webhook_failure_source

CallRail

Effective October 1, 2025 we use a new October 2025 schema. Review the latest ERD to better understand the schema changes.

We are updating the connector schema to support a feature enhancement.

109 total changes • 0 possible breaking changes

Table/column	Change type	New name
`CALL`
column	New Column	`campaign`
column	New Column	`company_id`
column	New Column	`created_at`
column	New Column	`custom_*`
column	New Column	`device_type`
column	New Column	`first_call`
column	New Column	`first_touch_ad_position`
column	New Column	`first_touch_campaign`
column	New Column	`first_touch_device`
column	New Column	`first_touch_event_date`
column	New Column	`first_touch_keywords`
column	New Column	`first_touch_landing`
column	New Column	`first_touch_landing_page_url_params`
column	New Column	`first_touch_match_type`
column	New Column	`first_touch_medium`
column	New Column	`first_touch_referrer`
column	New Column	`first_touch_referrer_url_params`
column	New Column	`first_touch_session_browser`
column	New Column	`first_touch_source`
column	New Column	`first_touch_url_utm_params`
column	New Column	`formatted_business_phone_number`
column	New Column	`formatted_call_type`
column	New Column	`formatted_customer_location`
column	New Column	`formatted_customer_name`
column	New Column	`formatted_customer_name_or_phone_number`
column	New Column	`formatted_customer_phone_number`
column	New Column	`formatted_duration`
column	New Column	`formatted_tracking_phone_number`
column	New Column	`formatted_tracking_source`
column	New Column	`formatted_value`
column	New Column	`ga`
column	New Column	`good_lead_call_id`
column	New Column	`good_lead_call_time`
column	New Column	`highlights`
column	New Column	`keypad_entry_*`
column	New Column	`keywords`
column	New Column	`keywords_spotted`
column	New Column	`landing_page_url`
column	New Column	`last_requested_url`
column	New Column	`last_touch_ad_position`
column	New Column	`last_touch_campaign`
column	New Column	`last_touch_device`
column	New Column	`last_touch_event_date`
column	New Column	`last_touch_keywords`
column	New Column	`last_touch_landing`
column	New Column	`last_touch_landing_page_url_params`
column	New Column	`last_touch_match_type`
column	New Column	`last_touch_medium`
column	New Column	`last_touch_referrer`
column	New Column	`last_touch_referrer_url_params`
column	New Column	`last_touch_session_browser`
column	New Column	`last_touch_source`
column	New Column	`last_touch_url_utm_params`
column	New Column	`lead_created_ad_position`
column	New Column	`lead_created_campaign`
column	New Column	`lead_created_device`
column	New Column	`lead_created_event_date`
column	New Column	`lead_created_keywords`
column	New Column	`lead_created_landing`
column	New Column	`lead_created_landing_page_url_params`
column	New Column	`lead_created_match_type`
column	New Column	`lead_created_medium`
column	New Column	`lead_created_referrer`
column	New Column	`lead_created_referrer_url_params`
column	New Column	`lead_created_session_browser`
column	New Column	`lead_created_source`
column	New Column	`lead_created_url_utm_params`
column	New Column	`lead_status`
column	New Column	`medium`
column	New Column	`note`
column	New Column	`person_id`
column	New Column	`prior_calls`
column	New Column	`qualified_ad_position`
column	New Column	`qualified_campaign`
column	New Column	`qualified_device`
column	New Column	`qualified_event_date`
column	New Column	`qualified_keywords`
column	New Column	`qualified_landing`
column	New Column	`qualified_landing_page_url_params`
column	New Column	`qualified_match_type`
column	New Column	`qualified_medium`
column	New Column	`qualified_referrer`
column	New Column	`qualified_referrer_url_params`
column	New Column	`qualified_session_browser`
column	New Column	`qualified_source`
column	New Column	`qualified_url_utm_params`
column	New Column	`referrer_domain`
column	New Column	`referring_url`
column	New Column	`sentiment`
column	New Column	`session_uuid`
column	New Column	`source`
column	New Column	`source_name`
column	New Column	`speaker_percent_agent`
column	New Column	`speaker_percent_customer`
column	New Column	`summary`
column	New Column	`tags`
column	New Column	`timeline_url`
column	New Column	`total_calls`
column	New Column	`tracker_id`
column	New Column	`transcription`
column	New Column	`type`
column	New Column	`utm_campaign`
column	New Column	`utm_content`
column	New Column	`utm_medium`
column	New Column	`utm_source`
column	New Column	`utm_term`
column	New Column	`value`
column	New Column	`voice_assist_message`
column	New Column	`zip_code`

Centra

Effective October 29, 2025 we use a new October 2025 schema. Review the latest ERD to better understand the schema changes.

We are updating the connector schema to align with source changes.

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
`RETURN`
column	Discontinued Column		`status`

Cin7 Core

Effective October 6, 2025 we use a new October 2025 schema. Review the latest ERD to better understand the schema changes.

We are updating the connector schema to support a feature enhancement.

1 total changes • 0 possible breaking changes

Table/column	Change type		Old name	New name	Notes
`SALE`
column	New Column			`customer_reference`

ClickUp

Effective October 30, 2025 we use a new October 2025 schema. Review the latest ERD to better understand the schema changes.

We are updating the connector schema to enhance its usability.

3 total changes • 0 possible breaking changes

Table/column	Change type	New name
`CUSTOM_ITEM`
table	New Table	`CUSTOM_ITEM`
`SUB_TASK`
column	New Column	`custom_item_id`
`TASK`
column	New Column	`custom_item_id`

Cloudflare Analytics

Effective October 26, 2025 we use a new October 2025 schema. Review the latest ERD to better understand the schema changes.

We are updating the connector schema to enhance its 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 • 2 possible breaking changes

Table/column	Change type	Old name	New name	Notes
`REQUEST_GROUP`
column	Primary Key Change	`client_country_name`	`client_country_name` 🔑	Added to primary key.
column	Discontinued Column	`index` 🔑		No longer a primary key.

Coupa

We have added a new column, kind, to the PURPOSE table.

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

account_type_item
address_name
bank_account_number
bank_address
bank_city
bank_code
bank_fax_phone_area_code
bank_fax_phone_country_code
bank_fax_phone_extension
bank_fax_phone_id
bank_fax_phone_number
bank_postal_code
bank_routing_number
bank_state_region
bank_work_phone_area_code
bank_work_phone_country_code
bank_work_phone_extension
bank_work_phone_id
bank_work_phone_number
bank_country_id
bic
bic_routing_code
bsb_number
csp_rta_id
custom_field_1
custom_field_2
custom_field_3
custom_field_4
custom_field_5
custom_field_6
custom_field_7
custom_field_8
custom_field_9
custom_field_10
custom_field_11
custom_field_12
custom_field_13
custom_field_14
custom_field_15
custom_field_16
custom_field_17
custom_field_18
custom_field_19
custom_field_20
email
iban_number
ifsc
intermediary_bank_name
international_bank_account_number
kind
name_on_bank_account
payment_method_item
po_box
po_box_postal_code
sort_code
state_region
street_address
street_address2
street_address3
street_address4
supplier_information_id
swift_code
transit_number_and_institution_number
virtual_card_email
wire_routing_number

We have discontinued the following columns from the SUPPLIER_INFORMATION_ADDRESS table:

attention
business_group_name
custom_fields
external_src_name
external_src_ref
local_tax_number
name
state
street_1
street_2
street_3
street_4
vat_country_id
vat_number

Customer.io

We have added the transactional_message_id column to the EMAIL_EVENT table.

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

metrics_human_clicked
metrics_human_opened
metrics_prefetch_clicked
metrics_prefetch_opened

Delighted

We have added a new table unsubscribed_people.

Dialpad

Effective October 29, 2025 we use a new October 2025 schema. Review the latest ERD to better understand the schema changes.

We are updating the connector schema to support a feature enhancement.

1 total changes • 0 possible breaking changes

Table/column	Change type		Old name	New name	Notes
`CALL_TRANSCRIPT`
table	New Table			`CALL_TRANSCRIPT`

Eventbrite

Effective October 13, 2025 we use a new October 2025 schema. Review the latest ERD to better understand the schema changes.

We are updating the connector schema to enhance its 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.

7 total changes • 7 possible breaking changes

Table/column	Change type	Old name
`EVENT_TEAM`
table	Discontinued Table	`EVENT_TEAM`
`EVENT_TEAM_CREATOR_EMAIL`
table	Discontinued Table	`EVENT_TEAM_CREATOR_EMAIL`
`STRUCTURE_CONTENT_PUBLISHED`
table	Discontinued Table	`STRUCTURE_CONTENT_PUBLISHED`
`STRUCTURE_CONTENT_PUBLISHED_MODULE`
table	Discontinued Table	`STRUCTURE_CONTENT_PUBLISHED_MODULE`
`STRUCTURE_CONTENT_PUBLISHED_WIDGET_TAB`
table	Discontinued Table	`STRUCTURE_CONTENT_PUBLISHED_WIDGET_TAB`
`STRUCTURE_CONTENT_PUBLISHED_WIDGET_TAB_SLOT`
table	Discontinued Table	`STRUCTURE_CONTENT_PUBLISHED_WIDGET_TAB_SLOT`
`STRUCTURE_CONTENT_PUBLISHED_WIDGET_TAB_SLOT_HOST`
table	Discontinued Table	`STRUCTURE_CONTENT_PUBLISHED_WIDGET_TAB_SLOT_HOST`

Facebook Pages

We have added a new column, post_video_followers, to the LIFETIME_REEL_METRICS_TOTAL table. This column contains the number of follows for your reel.

We've also added the following columns in order to prepare for upcoming Graph API deprecations:

page_media_view to the DAILY_PAGE_METRICS_TOTAL table.
page_follows_city to the DAILY_PAGE_METRICS_BY_CITY table.
page_follows_country to the DAILY_PAGE_METRICS_BY_COUNTRY table.
post_media_view to the LIFETIME_POST_METRICS_TOTAL table.

Learn more about these changes in the Facebook Graph API changelog.

Float

Effective October 29, 2025 we use a new October 2025 schema. Review the latest ERD to better understand the schema changes.

We are updating the connector schema to support a feature enhancement.

1 total changes • 0 possible breaking changes

Table/column	Change type		Old name	New name	Notes
`PEOPLE_CONTRACT`
table	New Table			`PEOPLE_CONTRACT`

Freshservice

We have added support for custom fields in the TICKET_ITEM table. You can now sync additional metadata.

The custom fields appear with the custom_ prefix in your destination. For example, custom_priority_level and custom_approval_required.

Google Ads

The following metrics have been renamed to align with changes in the Google Ads API:

metrics.average_cpv is now metrics.trueview_average_cpv
metrics.video_view_rate is now metrics.video_trueview_view_rate
metrics.video_views is now metrics.video_trueview_views
metrics.video_view_rate_in_feed is now metrics.video_trueview_view_rate_in_feed
metrics.video_view_rate_in_stream is now metrics.video_trueview_view_rate_in_stream
metrics.video_view_rate_shorts is now metrics.video_trueview_view_rate_shorts

We now support the following metrics for video ads:

metrics.video_watch_time_duration_millis
metrics.average_video_watch_time_duration_millis

A variety of new metrics are now available for asset_group_asset, channel_aggregate_asset_view, and campaign_aggregate_asset_view custom reports.

The asset_group_asset custom report now supports the following segments:

segments.device
segments.conversion_action
segments.conversion_action_name
segments.conversion_action_category

The campaign custom report now supports the following new fields:

metrics.clicks_unique_query_clusters
metrics.conversions_unique_query_clusters
metrics.impressions_unique_query_clusters
segments.ad_using_product_data
segments.ad_using_video
campaign.feed_types
campaign.contains_eu_political_advertising

We now support the following new reporting resources:

campaign_search_term_view
location_interest_view
targeting_expansion_view

Google Analytics 4 Export

We have added the following columns to the EVENT table:

session_traffic_source_last_click.sa360_campaign.*
session_traffic_source_last_click.cm360_campaign.*
session_traffic_source_last_click.dv360_campaign.*
session_traffic_source_last_click.cross_channel_campaign.default_channel_group
session_traffic_source_last_click.cross_channel_campaign.primary_channel_group

To backfill the historical data for these columns, re-sync the connection or contact Fivetran Support to re-sync it for you.

Google Display & Video 360

The previously announced Google Display & Video 360 API deprecations changed on the source side:

The deprecation of the Insertion Order ID(FILTER_INSERTION_ORDER) dimension is reverted
The Insertion Order [FILTER_YOUTUBE_PROGRAMMATIC_GUARANTEED_INSERTION_ORDER](FILTER_YOUTUBE_PROGRAMMATIC_GUARANTEED_INSERTION_ORDER) dimension is deprecated

Greenhouse

We have added the following new tables:

APPLICATION_ATTACHMENT
APPROVAL
APPROVER
APPROVER_GROUP
HIRING_TEAM_STATUS

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

recruiter_id
coordinator_id
custom_fields
current_stage_name
prospective_departmen
prospective_office

We have added two new columns, opening_id and values, to the OFFER table.

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

active
demographic_question_set_id
first_published_at
job_post_custom_location_id
job_post_location_type_id
job_post_location_type_name
location_office_id

Intercom

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.

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.

Kustomer

We have made the following schema changes:

Added a new table, WORK_SESSION, which contains work session information for agents, including capacity status, handled item counts, availability metrics, and time-tracking statistics.
We incrementally sync the WORK_SESSION table and its child tables to capture new records.

Lob

Effective October 1, 2025 we use a new October 2025 schema. Review the latest ERD to better understand the schema changes.

We are updating the connector schema to support a feature enhancement.

16 total changes • 0 possible breaking changes

Table/column	Change type	New name
`CAMPAIGN`
table	New Table	`CAMPAIGN`
`CAMPAIGN_CREATIVE`
table	New Table	`CAMPAIGN_CREATIVE`
`CAMPAIGN_CREATIVE_TEMPLATE_PREVIEW`
table	New Table	`CAMPAIGN_CREATIVE_TEMPLATE_PREVIEW`
`CAMPAIGN_UPLOAD`
table	New Table	`CAMPAIGN_UPLOAD`
`POSTCARD`
column	New Column	`completed_at`
column	New Column	`fsc`
column	New Column	`is_creative_proof`
column	New Column	`is_dashboard`
column	New Column	`lob_credits_funding_status`
column	New Column	`qr_code`
column	New Column	`raw_url`
column	New Column	`status`
column	New Column	`to_be_expunged_date`
column	New Column	`url`
column	New Column	`use_type`
column	New Column	`usps_campaign_id`

Mambu

Effective October 30, 2025 we use a new October 2025 schema. Review the latest ERD to better understand the schema changes.

We are updating the connector schema to align with source changes.

3 total changes • 0 possible breaking changes

Table/column	Change type	New name
`LOAN_ACCOUNT`
column	New Column	`interest_rate`
column	New Column	`repayment_period_count`
column	New Column	`repayment_period_unit`

Okta

We have added two new tables, USER_ENROLLED_FACTOR and USER_AUTHENTICATOR_ENROLLMENT. We are gradually rolling out this change to all connections.

Pinterest Organic

Effective October 29, 2025 we use a new October 2025 schema. Review the latest ERD to better understand the schema changes.

We are updating the connector schema to enhance its usability.

1 total changes • 0 possible breaking changes

Table/column	Change type		Old name	New name	Notes
`USER_ACCOUNT`
column	New Column			`pin_count`

Playvox

Effective October 29, 2025 we use a new October 2025 schema. Review the latest ERD to better understand the schema changes.

We are updating the connector schema to enhance its 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 • 2 possible breaking changes

Table/column	Change type	Old name	New name	Notes
`JOB_FAILED`
column	Primary Key Change	`interaction_id` 🔑	`interaction_id`	No longer a primary key.
column	Primary Key Change		`index` 🔑	New primary key.

PostHog

Effective October 8, 2025 we use a new October 2025 schema. Review the latest ERD to better understand the schema changes.

We are updating the connector schema to support a feature enhancement.

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	Notes
`DATA_ATTRIBUTE`
table	Discontinued Table	`DATA_ATTRIBUTE`		Data is available in the `PROJECT` table.
`PROJECT`
column	New Column		`data_attribute`

Productive

Effective October 31, 2025 we use a new October 2025 schema. Review the latest ERD to better understand the schema changes.

We are updating the connector schema to enhance its usability.

1 total changes • 0 possible breaking changes

Table/column	Change type		Old name	New name	Notes
`COMPANY`
column	New Column			`default_subsidiary_id`

Recharge

We have added the following new tables:

BUNDLE_SELECTION
BUNDLE_SELECTION_ITEM
CREDIT_ACCOUNT
CREDIT_ADJUSTMENT
CUSTOMER_DELIVERY_SCHEDULE_ORDER
CUSTOMER_DELIVERY_SCHEDULE_ORDER_LINE_ITEM
EVENT
EVENT_UPDATED_ATTRIBUTE

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

Salesforce Commerce Cloud

We have added a new column, customer_is_guest, to the ORDERS_HISTORY table. Be sure to re-sync the ORDERS_HISTORY table to backfill the data for the new column.

SAP Concur

We have added a new column, USER_ID, to the USER table. The column contains the unique identifier for each user in SAP Concur.

We have added the following new tables:

REPORT_APPROVER
SPEND_USER
SPEND_USER_AUTHORIZED_APPROVER
SPEND_USER_CUSTOM_DATA
SPEND_USER_EXPENSE_DELEGATE
SPEND_USER_ROLE

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

SmartRecruiters

Effective October 1, 2025 we use a new October 2025 schema. Review the latest ERD to better understand the schema changes.

We are updating the connector schema to support a feature enhancement.

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 • 5 possible breaking changes

Table/column	Change type	Old name	New name	Notes
`CANDIDATE`
column	New Column		`tags`
`CANDIDATE_EDUCATION`
column	Discontinued Column	`index` 🔑		No longer a primary key.
column	Primary Key Change		`_fivetran_id` 🔑	New primary key.
`CANDIDATE_EXPERIENCE`
column	Discontinued Column	`index` 🔑		No longer a primary key.
column	Primary Key Change		`_fivetran_id` 🔑	New primary key.
`CANDIDATE_TAG`
table	Discontinued Table	`CANDIDATE_TAG`

Snapchat Ads

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

geo_type
geo_value
fivetran_id

We've also discontinued support for the index column in the TARGETING_GEOLOCATION_HISTORY table.

Stripe

We've added below fields in the QUOTE table:

subscription_data_billing_mode_flexible_proration_discounts
subscription_data_billing_mode_type
subscription_data_description
subscription_data_effective_date
subscription_data_metadata
subscription_data_trial_period_days

Transcend

Effective October 15, 2025 we use a new October 2025 schema. Review the latest ERD to better understand the schema changes.

We are updating the connector schema to align with source changes.

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
`ASSESSMENT_FILE`
table	Discontinued Table		`ASSESSMENT_FILE`

Validio

Effective October 24, 2025 we use a new October 2025 schema. Review the latest ERD to better understand the schema changes.

We are updating the connector schema to align with source changes.

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.

8 total changes • 8 possible breaking changes

Table/column	Change type	Old name
`SOURCE_CATALOG_ASSET`
column	Discontinued Column	`query_user`
column	Discontinued Column	`stats_utilization`
`SOURCE_CATALOG_ASSET_JOINED_TABLE`
table	Discontinued Table	`SOURCE_CATALOG_ASSET_JOINED_TABLE`
`VALIDATOR`
column	Discontinued Column	`config_minimum_reference_data_point`
column	Discontinued Column	`config_minimum_relative_difference_percent`
column	Discontinued Column	`config_mininum_absolute_difference`
column	Discontinued Column	`config_reference_source_field`
column	Discontinued Column	`config_sensitivity`

Walmart Marketplace

Effective October 28, 2025 we use a new October 2025 schema. Review the latest ERD to better understand the schema changes.

We are updating the connector schema to align with source changes.

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 • 2 possible breaking changes

Table/column	Change type	Old name	New name
`INCENTIVE_ITEM`
table	Discontinued Table	`INCENTIVE_ITEM`
`PRICE_INCENTIVE`
table	New Table		`PRICE_INCENTIVE`
`PRO_SELLER_BADGE_STATUS`
table	Discontinued Table	`PRO_SELLER_BADGE_STATUS`

Workday Financial Management

We’ve added a new column, country_alpha_2_code, to the BUSINESS_ENTITY_ADDRESS table.

We’ve added a new column, account_set_name, to the JOURNAL_ENTRY_LINE table.

To backfill the historical data for these columns, re-sync the tables or contact Fivetran Support.

Workday HCM

We have added a new column country_alpha_2_code to the ADDRESS table. Be sure to re-sync the table to backfill the historical data or reach out to Fivetran Support to re-sync it for you.

Xero

We have added a new column, repeating_invoice_id, to the INVOICE table.

Improvements

Amazon Selling Partner

We’re updating the sync frequency to once a day for the following reports in the Amazon Selling Partner connector.

CUSTOMER_SHIPMENT_SALES_REPORT
FULFILLMENT_CUSTOMER_SHIPMENT_PROMOTION_REPORT
LONG_TERM_STORAGE_FEE_CHARGES_REPORT
MARKET_BASKET_ANALYSIS_REPORT_MONTHLY
MARKET_BASKET_ANALYSIS_REPORT_QUARTERLY
NET_PURE_PRODUCT_MARGIN_REPORT_MONTHLY
NET_PURE_PRODUCT_MARGIN_REPORT_QUARTERLY
ORDERS_REPORT
REIMBURSEMENTS_REPORT
REPEAT_PURCHASE_REPORT_MONTHLY
REPEAT_PURCHASE_REPORT_QUARTERLY
SALES_AND_TRAFFIC_BUSINESS_CHILD_ASIN_REPORT_MONTHLY
SALES_AND_TRAFFIC_BUSINESS_PARENT_ASIN_REPORT_MONTHLY
SALES_AND_TRAFFIC_BUSINESS_REPORT_MONTHLY
SALES_AND_TRAFFIC_BUSINESS_SKU_REPORT_MONTHLY
SEARCH_TERMS_REPORT_MONTHLY
SEARCH_TERMS_REPORT_QUARTERLY
VENDOR_INVENTORY_MANUFACTURING_FRESH_ASIN_REPORT_MONTHLY
VENDOR_INVENTORY_MANUFACTURING_FRESH_ASIN_REPORT_QUARTERLY
VENDOR_INVENTORY_MANUFACTURING_FRESH_REPORT_MONTHLY
VENDOR_INVENTORY_MANUFACTURING_FRESH_REPORT_QUARTERLY
VENDOR_INVENTORY_MANUFACTURING_RETAIL_ASIN_REPORT_MONTHLY
VENDOR_INVENTORY_MANUFACTURING_RETAIL_ASIN_REPORT_QUARTERLY
VENDOR_INVENTORY_MANUFACTURING_RETAIL_REPORT_MONTHLY
VENDOR_INVENTORY_MANUFACTURING_RETAIL_REPORT_QUARTERLY
VENDOR_INVENTORY_SOURCING_FRESH_ASIN_REPORT_MONTHLY
VENDOR_INVENTORY_SOURCING_FRESH_ASIN_REPORT_QUARTERLY
VENDOR_INVENTORY_SOURCING_FRESH_REPORT_MONTHLY
VENDOR_INVENTORY_SOURCING_FRESH_REPORT_QUARTERLY
VENDOR_INVENTORY_SOURCING_RETAIL_ASIN_REPORT_MONTHLY
VENDOR_INVENTORY_SOURCING_RETAIL_ASIN_REPORT_QUARTERLY
VENDOR_INVENTORY_SOURCING_RETAIL_REPORT_MONTHLY
VENDOR_INVENTORY_SOURCING_RETAIL_REPORT_QUARTERLY
VENDOR_SALES_MANUFACTURING_BUSINESS_ASIN_REPORT_MONTHLY
VENDOR_SALES_MANUFACTURING_BUSINESS_ASIN_REPORT_QUARTERLY
VENDOR_SALES_MANUFACTURING_BUSINESS_REPORT_MONTHLY
VENDOR_SALES_MANUFACTURING_BUSINESS_REPORT_QUARTERLY
VENDOR_SALES_MANUFACTURING_FRESH_ASIN_REPORT_MONTHLY
VENDOR_SALES_MANUFACTURING_FRESH_ASIN_REPORT_QUARTERLY
VENDOR_SALES_MANUFACTURING_FRESH_REPORT_MONTHLY
VENDOR_SALES_MANUFACTURING_FRESH_REPORT_QUARTERLY
VENDOR_SALES_MANUFACTURING_RETAIL_ASIN_REPORT_MONTHLY
VENDOR_SALES_MANUFACTURING_RETAIL_ASIN_REPORT_QUARTERLY
VENDOR_SALES_MANUFACTURING_RETAIL_REPORT_MONTHLY
VENDOR_SALES_MANUFACTURING_RETAIL_REPORT_QUARTERLY
VENDOR_SALES_SOURCING_BUSINESS_ASIN_REPORT_MONTHLY
VENDOR_SALES_SOURCING_BUSINESS_ASIN_REPORT_QUARTERLY
VENDOR_SALES_SOURCING_BUSINESS_REPORT_MONTHLY
VENDOR_SALES_SOURCING_BUSINESS_REPORT_QUARTERLY
VENDOR_SALES_SOURCING_FRESH_ASIN_REPORT_MONTHLY
VENDOR_SALES_SOURCING_FRESH_ASIN_REPORT_QUARTERLY
VENDOR_SALES_SOURCING_FRESH_REPORT_MONTHLY
VENDOR_SALES_SOURCING_FRESH_REPORT_QUARTERLY
VENDOR_SALES_SOURCING_RETAIL_ASIN_REPORT_MONTHLY
VENDOR_SALES_SOURCING_RETAIL_ASIN_REPORT_QUARTERLY
VENDOR_SALES_SOURCING_RETAIL_REPORT_MONTHLY
VENDOR_SALES_SOURCING_RETAIL_REPORT_QUARTERLY
VENDOR_TRAFFIC_REPORT_MONTHLY
VENDOR_TRAFFIC_REPORT_QUARTERLY

Azure Blob Storage

We have added a new authentication method for our Azure Blob Storage connector. You can now use a Microsoft Entra authentication method to connect your Azure Blob Storage with Fivetran. To support these features, we have made the following changes to the connection setup form:

Added Authentication method field, that allows you to select between Microsoft Entra ID - client credentials grant using client secret and Connection String authentication methods.
Added Storage account, Tenant ID, Client ID, and Client secret fields, allowing you to provide your own app credentials.

For more information, see our setup instructions and REST API configuration. We are gradually rolling out these changes to all existing connections.

Azure Devops

We’ve made the following improvements to prevent data integrity issues:

Improved how the list_work_item temp table filters work items to ensure cleaner and more efficient syncs. Project ID and team ID filters are now applied in the query body instead of the path parameters. This change eliminates duplicate work_item_ids that were appearing in some syncs.
Added incremental sync support so that only new or updated work items are fetched during subsequent syncs.

Centra

We now re-import the PRODUCT table daily to capture updates and deletes.

Coupa

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

Criteo Retail Media

We now retain data in the REPORT_CAMPAIGN and REPORT_LINE_ITEM tables for up to 3 years.

Databricks destination

You can now disable the VACUUM operations that Fivetran automatically runs on your destination tables. To support this enhancement, we have added a new toggle, Disable VACUUM operations, to the destination setup form.

Gainsight Customer Success

We have fixed a bug that prevented re-import tables from being re-synced. We now accurately re-sync these tables.

Gong

We have changed the sync strategy for the call and transcript tables. The weekly re-import process has been removed.

Google Ads

We now support Google Ads v22.

Google Analytics 4 Export

We have added a new option, Intraday Export Type, to the connection setup form for the connections created on or after July 24, 2023. You can now select one of the following export types:

Streaming - Sync a continuous export of events
Fresh Daily - Sync periodic batch updates
Daily Only (skip intraday events) - Sync only the full export of data that takes place daily

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

GRIN

We have fixed a bug that prevented us from syncing outstanding jobs data into the PARTNERSHIP_JOB table. Now, we correctly sync outstanding jobs data into this table.

Mailchimp

We have removed the option to select individual e-commerce stores in the setup form. Henceforth, data from all your e-commerce stores will be synced based on the tables selected in your schema.

Managed Data Lake Service

You can now modify the Snapshot Retention Period field in the setup form at any time for your Managed Data Lake destinations.

We have added a new setup test, Storage Blob Delegator Test, for ADLS to check whether the service principal has the Storage Blob Delegator role assigned at the storage account level.

Medallia

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

Microsoft Lists

We have added a new authentication method for our Microsoft List connector. You can now use a custom authentication method to connect your Microsoft list account with Fivetran. To support these features, we have made the following changes to the connection setup form:

Added Authentication method field, that allows you to select between a Quick Setup (Default) and an Advanced Setup.
Added Client ID, Client secret, Tenant Id and Site Id fields, allowing you to provide your own app credentials.
Added a Run connection test button to validate the connection credentials.

For more information, see our setup instructions and REST API configuration. We are gradually rolling out these changes to all existing connections.

Oracle

We now support capturing archived redo logs stored in Automatic Storage Management (ASM) using the Binary Log Reader incremental sync method.

PostgreSQL

We have changed our connection setup form and now support only two update methods, Logical Replication and Query-Based. Previously, we supported XMIN, Fivetran Teleport Sync, and Logical Replication. New connections created after November 5th, 2025, will support this functionality by default. We are gradually rolling out this change to all existing connections.

PostgreSQL "money" type improvement

We now support precision and scale for the money data type.

PostgreSQL source

We now handle JSON columns with duplicate keys by retaining only the last key’s value when writing to a PostgreSQL destination. Previously, such columns were populated with an error message if duplicate keys were detected.

Pylon Support Platform

We have updated our sync strategy for the ISSUE table. We now re-import the table once a week to capture updates. Previously, we incrementally synced it to capture updates.

Row Filtering support for IN operator

We now support the In operator for row filtering. You can filter rows by Integer, Serial, or String column values using a list of allowed values.

For more information, see our row filtering documentation.

Row Filtering supported for incremental syncs

We now support row filtering for incremental syncs. The filters are applied starting from the next sync after the filters are created.

Previously, we supported row filtering for initial syncs and re-syncs only.

For more information, see our row filtering documentation.

SAP ERP on HANA

A new version of the Fivetran NetWeaver API is now available for download: v1900284.

We added support for Netweaver 7.4.

SharePoint

Effective October 14, 2025, new SharePoint connections will support files with identical names located in different folders. To enable this enhancement, the connector will update the behavior of the _file column. Instead of including only the file name, the _file column will now store the full file path to uniquely identify files.

This change applies only to new SharePoint connections created after October 14, 2025. Existing connections will continue to work as they do today and will not be impacted by this update.

Shopify

We have added a new authentication method, Custom App to the setup form. You can now create and authorize a custom Shopify app directly from your Shopify admin to connect with Fivetran. For more information, see our setup guide.

SQL Server

The Binary Log Reader method now supports the following spatial and hierarchy data types:

GEOGRAPHY
GEOMETRY
HIERARCHYID

TikTok Organic

We no longer use the Authorization URL to access or sync your data. This change streamlines the connection setup process.

Tremendous

We’ve updated the Tremendous connector to use the default OAuth 2.0 framework, from custom OAuth 2.0 setup. This update introduces a centralized OAuth app, simplifying authentication and improving security. Be sure to re-authenticate your Tremendous connection. For more information, see our setup instructions.

Unicommerce

We now sync the sale_order entity data based on the facility code you provide in the connection setup form.

Workday Financial Management

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

Zendesk Support

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

Hybrid Deployment does not support the following webhook tables:

AGENT_CHANNEL_HISTORY
AGENT_MAX_CAPACITY_HISTORY
AGENT_STATUS_HISTORY
AGENT_UNIFIED_STATUS_HISTORY

October 2025

Connector SDK

fivetran-connector-sdk PyPI package

Fivetran Connector SDK

Fivetran Proxy Agent

Version 1.1.2

Lite Connectors

Logs

Extract Summary Event Now Includes SQL Query Count

Referencing users by ID instead of email address

Splunk Logging

Partner SDK

SingleStore destination is in beta

Quickstart Package Updates

Quickstart data model package updates

v1.0.1

Bug Fixes

v1.0.1

Under the Hood

v1.0.2

Bug Fixes

Under the Hood

v0.2.2

Under the Hood

v0.1.0

Under the Hood

v1.1.1

Bug Fix

v1.1.0

Schema/Data Change

Feature Update

Tests Update

Under the Hood

v1.1.0

Bug Fixes

Under the Hood

v1.1.0

Schema/Data Change

Feature Update

Under the Hood

Contributors:

v1.1.0

Schema Changes

Feature Update

Bug Fixes

Documentation

v1.1.0

Schema/Data Change

Under the Hood

v1.0.0

Breaking Changes

Source Package Consolidation

Schema Updates

Bug Fixes

Under the Hood

Transformations for dbt

Automated Quickstart schema changes

Fivetran data model consolidation

New connectors

Workday Adaptive Planning

Schema changes

Adobe Workfront

Amazon DSP

Amazon Selling Partner

AppsFlyer

Azure DevOps

Braze

CallRail

Centra

Cin7 Core

ClickUp

Cloudflare Analytics

Coupa

Customer.io

Delighted

Dialpad

Eventbrite

Facebook Pages

Float

Freshservice

`fivetran-connector-sdk` PyPI package