August 2026

Connector SDK

fivetran-connector-sdk PyPI package

We have released version 2.11.0 of the fivetran-connector-sdk PyPI package. This release includes the following updates:

• Adds support for errors and warnings.
• Introduces the --yes flag and updates other non-interactive flags for better clarity and user experience.
• Adds resolution precedence for required flags and providing the configuration.json path.
• Updates the new connection creation and debug flows to require configuration.json. For more information, see configuration resolution order.
• Updated fivetran init and AI plugin setup behavior for existing projects.
• Minor enhancements and improvements.
• Updated testers.

fivetran-api-playground PyPI package

We have released version 1.1.9 of the fivetran-api-playground PyPI package. This release upgrades the faker library dependency to 40.36.0.

In-Dashboard Contract Renewal

If your account is eligible, you can now renew your annual contract directly from the Fivetran dashboard, 90 days or less before the end of your current contract. The option is available on the Billing page to eligible users.

Learn more in our In-dashboard annual contract renewal documentation.

Insights Tab

We've added the Insights tab to the Connection Details page in the Fivetran dashboard. It highlights the value Fivetran provides for your connection.

You can now view key maintenance details about your connections, including:

• Schema changes handled
• Source deletes captured
• Volume of data processed
• Associated downstream models
• Recent connector improvements

Learn more in our Insights tab documentation.

Logs

Sync type in sync log events

We have added the sync_type field to the sync_start and sync_end log events. The field identifies whether a sync is HISTORICAL or INCREMENTAL.

Managed Data Lake Service

All new connections set up on or after August 28, 2026 preserve null byte characters in string values. Previously, we removed null byte characters before writing string values to the data lake, which could cause differences between the source and destination data.

Partner SDK

Partner SDK Tester

We have released version 2.26.0810.001 of the Partner SDK Tester. This release includes the following improvements:

• Added HTML rendering support for errors and warnings messages to improve readability during local testing.

Quickstart Package Updates

Quickstart data model package updates

v2.7.3

Feature Updates

• Adds DuckDB as a supported destination.

v1.3.1

Feature Updates

• Adds DuckDB as a supported destination.

v0.5.1

Feature Updates

• Adds DuckDB as a supported destination.

v1.4.1

Feature Updates

• Adds DuckDB as a supported destination.

v1.3.2

Feature Updates

• Adds DuckDB as a supported destination.

v1.3.2

Feature Updates

• Adds DuckDB as a supported destination.

v1.3.1

Feature Updates

• Adds DuckDB as a supported destination.

v1.4.1

Feature Updates

• Adds DuckDB as a supported destination.

v0.4.1

Feature Updates

• Adds DuckDB as a supported destination.

v1.5.1

Feature Updates

• Adds DuckDB as a supported destination.

v1.3.1

Feature Updates

• Adds DuckDB as a supported destination.

v2.5.3

Feature Updates

• Adds DuckDB as a supported destination.

v1.4.1

Feature Updates

• Adds DuckDB as a supported destination.

v1.4.1

Feature Updates

• Adds DuckDB as a supported destination.

v0.7.2

Feature Updates

• Adds DuckDB as a supported destination.

v1.3.1

Feature Updates

• Adds DuckDB as a supported destination.

v1.4.1

Feature Updates

• Adds DuckDB as a supported destination.

v1.9.2

Feature Updates

• Adds DuckDB as a supported destination.

v1.2.1

Feature Updates

• Adds DuckDB as a supported destination.

v1.7.1

Feature Updates

• Adds DuckDB as a supported destination.

v1.5.1

Feature Updates

• Adds DuckDB as a supported destination.

v1.4.1

Feature Updates

• Adds DuckDB as a supported destination.

v1.3.1

Feature Updates

• Adds DuckDB as a supported destination.

v1.3.1

Feature Updates

• Adds DuckDB as a supported destination.

v1.5.1

Feature Updates

• Adds DuckDB as a supported destination.

v1.3.2

Feature Updates

• Adds DuckDB as a supported destination.

v1.4.1

Feature Updates

• Adds DuckDB as a supported destination.

v1.3.1

Feature Updates

• Adds DuckDB as a supported destination.

v0.4.1

Feature Updates

• Adds DuckDB as a supported destination.

v1.7.1

Feature Updates

• Adds DuckDB as a supported destination.

v1.4.1

Feature Updates

• Adds DuckDB as a supported destination.

v1.4.1

Feature Updates

• Adds DuckDB as a supported destination.

v1.3.1

Feature Updates

• Adds DuckDB as a supported destination.

v1.3.1

Feature Updates

• Adds DuckDB as a supported destination.

v1.9.1

Feature Updates

• Adds DuckDB as a supported destination.

v1.5.2

Feature Updates

• Adds DuckDB as a supported destination.

v1.5.1

Feature Updates

• Adds DuckDB as a supported destination.

v1.5.1

Feature Updates

• Adds DuckDB as a supported destination.

v1.4.1

Feature Updates

• Adds DuckDB as a supported destination.

v0.6.1

Feature Updates

• Adds DuckDB as a supported destination.

v2.4.1

Feature Updates

• Adds DuckDB as a supported destination.

v0.8.1

Feature Updates

• Adds DuckDB as a supported destination.

v1.0.2

Feature Updates

• Adds DuckDB as a supported destination.

v1.3.1

Feature Updates

• Adds DuckDB as a supported destination.

v1.9.2

Feature Updates

• Adds DuckDB as a supported destination.

v1.3.1

Feature Updates

• Adds DuckDB as a supported destination.

v1.6.2

Feature Updates

• Adds DuckDB as a supported destination.

v0.2.1

Feature Updates

• Adds DuckDB as a supported destination.

v1.4.1

Feature Updates

• Adds DuckDB as a supported destination.

v1.4.1

Feature Updates

• Adds DuckDB as a supported destination.

v0.3.1

Feature Updates

• Adds DuckDB as a supported destination.

v1.0.3

Feature Updates

• Adds DuckDB as a supported destination.

v1.3.1

Feature Updates

• Adds DuckDB as a supported destination.

v1.2.1

Feature Updates

• Adds DuckDB as a supported destination.

v1.6.1

Feature Updates

• Adds DuckDB as a supported destination.

v1.2.1

Feature Updates

• Adds DuckDB as a supported destination.

v1.7.1

Feature Updates

• Adds DuckDB as a supported destination.

v1.4.1

Feature Updates

• Adds DuckDB as a supported destination.

v1.10.2

Feature Updates

• Adds DuckDB as a supported destination.

v0.17.1

Feature Updates

• Adds DuckDB as a supported destination.

v1.10.1

Feature Updates

• Adds DuckDB as a supported destination.

v1.9.1

Bug Fix

• Fixes a compilation error in hubspot__conversations when either variable hubspot_team_enabled or hubspot_role_enabled is set to false.

v1.4.2

Documentation

• Removes the image_ids field from src_tiktok_ads.yml. It's not used downstream, and TikTok will stop populating it starting August 2026.

v1.3.1

Bug Fix

• Fixes int_apple_store__date_spine compilation errors by falling back to a default one-year date range when the underlying APP_STORE_* tables aren't synced.

v1.3.1

Bug Fix

• Resolves a BigQuery error when the segment, campaign, and automation sources supply mismatched datatypes by casting the segment_id join keys in mailchimp__segments to string.

v1.5.1

Bug Fixes

• Fixes a runtime error in int_recharge__calendar_spine by falling back to a default one-year date range when the CHARGE table wasn't synced.
• Fixes a compilation error caused by an invalid datatype reference for when the _fivetran_synced column was not synced.

v1.4.2

Bug Fix

• Fixes a union type mismatch error in sage_intacct__ap_ar_enhanced by explicitly casting:
  • customer_id to a string in stg_sage_intacct__ap_bill_item and stg_sage_intacct__ar_invoice_item.
  • due_in_days to an integer in stg_sage_intacct__ap_bill and stg_sage_intacct__ar_invoice.
• Previously, these columns could be inferred as different data types, causing the model to fail.

v1.0.2

PR #37 includes the following update.

Bug Fix

• Fixes a bug where int_workday__employee_history failed to run if annual_currency_summary_primary_compensation_basis, annual_currency_summary_total_base_pay, or annual_currency_summary_total_salary_and_allowances weren't enabled. These fields are optional, so they now resolve to null when not synced instead of failing the model.

v1.3.3

Bug Fix

• Corrects the default source table identifier for app_store_app, which pointed at the wrong table name and caused a runtime error in stg_apple_store__app_store_app_tmp. This default had no effect prior to v1.3.0's move to fivetran_utils.union_connections, which resolves the source table using this identifier.
• Renames the apple_store_app_identifier variable to apple_store_app_store_app_identifier to match this package's variable naming convention. If you had set apple_store_app_identifier in your own project, update your configuration to use the new variable name.

v0.6.0

Schema/Data Change

1 total change • 1 possible breaking change

v1.6.1

Feature Update

• Updates Quickstart to surface the connector-level models that Social Media Reporting does not already build, so you can enable them directly from Quickstart:
  • facebook_pages__pages_report
  • youtube__age_demographics_pivot
  • youtube__gender_demographics_pivot
  • youtube__demographics_report

v1.3.1

Feature Updates

• Updates Quickstart to surface the connector-level models that App Reporting does not already build, so you can enable them directly from Quickstart:
  • apple_store__subscription_report
  • google_play__finance_report
• Adds support for configuring individual apple_store and google_play package-level variables (e.g. apple_store__subscription_events) directly from Quickstart.

Under the Hood

• Adds system-only table variables for non-essential connector source tables (app_crash_daily for Apple Store, stats_store_performance_traffic_source for Google Play) so a missing optional source no longer blocks downstream Quickstart models.

v1.8.0

Schema/Data Change

1 total change • 1 possible breaking change

Feature Update

• Adds the transaction_accounting_lines_pass_through_columns variable, persisting chosen custom columns from the TRANSACTION_ACCOUNTING_LINE source table. These fields are brought into netsuite2__transaction_details. For more details, refer to the Passing Through Additional Fields section of the README.

Bug Fix

• Fixes null conversion amounts for top-level subsidiaries missing a self-conversion exchange rate; rate now defaults to 1. Updates converted_amount values in netsuite2__transaction_details, netsuite2__income_statement, and netsuite2__balance_sheet.

Note: A --full-refresh is recommended after upgrading.

v2.4.0

The account, campaign, contact, and opportunity daily history models, and their related variables, are not currently available in Quickstart.

Schema/Data Change (--full-refresh required after upgrading)

1 total change • 1 possible breaking change

Bug Fix

• Fixes an issue in salesforce__account_daily_history, salesforce__campaign_daily_history, salesforce__contact_daily_history, and salesforce__opportunity_daily_history where a record that remained current but hadn't changed recently could stop receiving new daily rows on incremental runs. Currently active records now continue to receive a daily row regardless of how recently they last changed. Requires --full-refresh to backfill any rows that were previously missing.

Feature Update

• Adds a configurable lookback_window variable (default 1 day) to salesforce__account_daily_history, salesforce__campaign_daily_history, salesforce__contact_daily_history, and salesforce__opportunity_daily_history. Each incremental run now reprocesses the last lookback_window days in addition to any new dates, so a corrected or backfilled history record landing within that window is picked up automatically instead of requiring a --full-refresh.

v1.10.0

Schema/Data Change

5 total changes • 4 possible breaking changes

v1.10.0

PR #167, PR #172 include the following updates:

Schema/Data Changes

4 total changes • 0 possible breaking changes

v0.8.0

Schema/Data Change (--full-refresh required after upgrading)

7 total changes • 4 breaking changes

Bug Fix

• Fixes case-sensitive string comparisons in coss.sql (the field-name-to-column dispatch logic, and the set_to_zero/xcoss/mig_source/bstat/accasty filters) and faglflexa.sql (the bstat filter) that compared against lowercase literals while the underlying SAP data uses uppercase codes. This caused rows to be silently dropped or amount fields to incorrectly fall through to 0.

Documentation

• Splits the staging and compatibility view YAML doc files into one file per model (previously grouped together), and simplifies the source YAML by removing redundant column-level documentation. Makes the docs easier to navigate for both humans and AI coding agents.

v1.9.0

Schema/Data Change

46 new models • 0 possible breaking changes

Feature Updates

Property History Models

The following changes apply to daily property history models:

• Adds the hubspot__contact_property_history_columns variable to pivot out additional properties as string columns in hubspot__daily_contact_history. See the README for configuration details.
• Adds the hubspot__deal_property_history_columns variable to pivot out additional properties as string columns in hubspot__daily_deal_history. See the README for configuration details.
• Adds the hubspot__company_property_history_columns variable to pivot out additional properties as string columns in hubspot__daily_company_history. See the README for configuration details.
• Adds the deal_history_extension_days variable to limit or extend the history of deals in hubspot__daily_deal_history past their close dates (default=30 days). See the README for configuration details.
• Adds the hubspot__daily_history_start_date variable to limit daily history models to a specific start date, reducing build time for large datasets. Applies to hubspot__daily_contact_history, hubspot__daily_deal_history, hubspot__daily_company_history, and hubspot__daily_ticket_history. See the README for configuration details.
• Adds a configurable lookback_window variable to all incremental windows to catch late-arriving records. Default value = 3 days. See the README for configuration details.

Custom Columns

The following changes allow for additional custom columns:

• Adds the hubspot_marketing_event_custom_properties variable to pivot custom property values from marketing_event_custom_property into columns in hubspot__marketing_event_performance. Set to a list of property names (e.g. ['spent', 'budget']); defaults to [] (no properties pivoted). See the README for details.
• Adds the hubspot__company_list_pass_through_columns variable to bring additional columns from the company_list source table through to hubspot__company_lists and stg_hubspot__company_list. See the README for configuration details.
• Adds the hubspot__contact_list_pass_through_columns variable to bring additional columns from the contact_list source table through to hubspot__contact_lists and stg_hubspot__contact_list. See the README for configuration details.
• The hubspot__pass_through_all_columns and hubspot__enable_all_property_labels variables now also apply to company_list and contact_list models.

Under the Hood

• Casts form_id and/or conversion_id as strings when missing from source data in stg_hubspot__form and stg_hubspot__contact_form_submission.
• Ensures user_id is an integer in stg_hubspot__users when missing from source data.
• Optimizes int_hubspot__ticket_calendar_spine by limiting how far into the future it looks (one day vs one week) and its start date on incremental runs.
  • This will require a --full-refresh run.

Syncing empty columns

We now support syncing empty columns or columns with null values for Files connectors to the following destinations:

• ClickHouse Cloud
• Managed Data Lake Service
• PostgreSQL
• Redshift

Transformations for dbt Core

dbt Core version adoption

We have added support of dbt Core* version 1.1.6 for the following destinations:

• BigQuery
• ClickHouse Cloud
• Databricks
• PostgreSQL
• Redshift
• Snowflake
• SQL Server
• Azure Synapse
• Teradata Vantage

We have added support of dbt Core* version 1.2.7 for the following destinations:

• BigQuery
• ClickHouse Cloud
• Databricks
• PostgreSQL
• Redshift
• Snowflake
• SQL Server
• Azure Synapse
• Teradata Vantage

We have added support of dbt Core* version 1.3.8 for the following destinations:

• BigQuery
• ClickHouse Cloud
• Databricks
• PostgreSQL
• Redshift
• Snowflake
• SQL Server
• Azure Synapse
• Teradata Vantage

We have added support of dbt Core* version 1.4.10 for the following destinations:

• BigQuery
• ClickHouse Cloud
• Databricks
• PostgreSQL
• Redshift
• Snowflake
• SQL Server
• Azure Synapse
• Teradata Vantage

We have added support of dbt Core* version 1.5.12 for the following destinations:

• BigQuery
• ClickHouse Cloud
• Databricks
• PostgreSQL
• Redshift
• Snowflake
• Azure Synapse
• Teradata Vantage

We have added support of dbt Core* version 1.6.19 for the following destinations:

• BigQuery
• ClickHouse Cloud
• Databricks
• PostgreSQL
• Redshift
• Snowflake
• Teradata Vantage

We have added support of dbt Core* version 1.7.20 for the following destinations:

• BigQuery
• ClickHouse Cloud
• Databricks
• PostgreSQL
• Redshift
• Snowflake
• SQL Server
• Azure Synapse
• Teradata Vantage

We have added support of dbt Core* version 1.8.10 for the following destinations:

• BigQuery
• ClickHouse Cloud
• Databricks
• PostgreSQL
• Redshift
• Snowflake
• SQL Server
• Azure Synapse
• Teradata Vantage

We have added support of dbt Core* version 1.9.11 for the following destinations:

• BigQuery
• ClickHouse Cloud
• Databricks
• PostgreSQL
• Redshift
• Snowflake
• SQL Server
• Azure Synapse
• Teradata Vantage

We have added support of dbt Core* version 1.10.23 for the following destinations:

• BigQuery
• ClickHouse Cloud
• Databricks
• PostgreSQL
• Redshift
• Snowflake
• SQL Server
• Azure Synapse
• Teradata Vantage

We have added support of dbt Core* version 1.11.13 for the following destinations:

• BigQuery
• ClickHouse Cloud
• Databricks
• PostgreSQL
• Redshift
• Snowflake
• SQL Server
• Azure Synapse
• Teradata Vantage

We have added support of dbt Core* version 1.12.1 for the following destinations:

• BigQuery
• Databricks
• PostgreSQL
• Redshift
• Snowflake
• SQL Server
• Azure Synapse
• Teradata Vantage

We have added support of dbt Core* version 1.12.2 for the following destinations:

• BigQuery
• Databricks
• PostgreSQL
• Redshift
• Snowflake
• SQL Server
• Azure Synapse
• Teradata Vantage

Schema changes

ADP Workforce Now

We have removed the PERSON_DOCUMENT table.

BillingPlatform

Braze

We have added two new tables, CAMPAIGN_ANALYTICS and CAMPAIGN_ANALYTICS_VARIATION.

Canvas Data 2 by Instructure

Cornerstone

Coupa

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

• created_at
• currency_id
• negotiated_savings
• negotiated_savings_currency_id
• original_id
• planned_savings
• planned_savings_currency_id
• public
• state

We have added a new column, participation, to the QUOTE_SUPPLIER table.

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

• contract_parties_field_container_id
• contract_parties_field_container_created_at
• contract_parties_field_container_updated_at
• contract_parties_field_container_custom_fields
• contract_parties_field_container_contract_type_custom_field_1
• contract_parties_field_container_contract_type_custom_field_2
• contract_parties_field_container_contract_type_custom_field_3
• contract_parties_field_container_contract_type_custom_field_4
• contract_parties_field_container_contract_type_custom_field_5
• contract_parties_field_container_contract_type_custom_field_6
• contract_parties_field_container_contract_type_custom_field_7
• contract_parties_field_container_contract_type_custom_field_8
• contract_parties_field_container_contract_type_custom_field_9
• contract_parties_field_container_contract_type_custom_field_10
• contract_price_and_payment_id
• contract_price_and_payment_created_at
• contract_price_and_payment_updated_at
• contract_price_and_payment_custom_fields
• contract_price_and_payment_contract_type_custom_field_1
• contract_price_and_payment_contract_type_custom_field_2
• contract_price_and_payment_contract_type_custom_field_3
• contract_price_and_payment_contract_type_custom_field_4
• contract_price_and_payment_contract_type_custom_field_5
• contract_price_and_payment_contract_type_custom_field_6
• contract_price_and_payment_contract_type_custom_field_7
• contract_price_and_payment_contract_type_custom_field_8
• contract_price_and_payment_contract_type_custom_field_9
• contract_price_and_payment_contract_type_custom_field_10
• contract_relationship_and_reporting_id
• contract_relationship_and_reporting_created_at
• contract_relationship_and_reporting_updated_at
• contract_relationship_and_reporting_custom_fields
• contract_relationship_and_reporting_contract_type_custom_field_1
• contract_relationship_and_reporting_contract_type_custom_field_2
• contract_relationship_and_reporting_contract_type_custom_field_3
• contract_relationship_and_reporting_contract_type_custom_field_4
• contract_relationship_and_reporting_contract_type_custom_field_5
• contract_relationship_and_reporting_contract_type_custom_field_6
• contract_relationship_and_reporting_contract_type_custom_field_7
• contract_relationship_and_reporting_contract_type_custom_field_8
• contract_relationship_and_reporting_contract_type_custom_field_9
• contract_relationship_and_reporting_contract_type_custom_field_10
• contract_terms_and_renewal_id
• contract_terms_and_renewal_created_at
• contract_terms_and_renewal_updated_at
• contract_terms_and_renewal_custom_fields
• contract_terms_and_renewal_contract_type_custom_field_1
• contract_terms_and_renewal_contract_type_custom_field_2
• contract_terms_and_renewal_contract_type_custom_field_3
• contract_terms_and_renewal_contract_type_custom_field_4
• contract_terms_and_renewal_contract_type_custom_field_5
• contract_terms_and_renewal_contract_type_custom_field_6
• contract_terms_and_renewal_contract_type_custom_field_7
• contract_terms_and_renewal_contract_type_custom_field_8
• contract_terms_and_renewal_contract_type_custom_field_9
• contract_terms_and_renewal_contract_type_custom_field_10
• contract_termination_id
• contract_termination_created_at
• contract_termination_updated_at
• contract_termination_custom_fields
• contract_termination_contract_type_custom_field_1
• contract_termination_contract_type_custom_field_2
• contract_termination_contract_type_custom_field_3
• contract_termination_contract_type_custom_field_4
• contract_termination_contract_type_custom_field_5
• contract_termination_contract_type_custom_field_6
• contract_termination_contract_type_custom_field_7
• contract_termination_contract_type_custom_field_8
• contract_termination_contract_type_custom_field_9
• contract_termination_contract_type_custom_field_10

We have added a new column, party_directionality, to the CONTRACT_PARTY table.

D2L Brightspace

Facebook Ads

We've added a new table, CUSTOM_AUDIENCE_LABEL. The table contains the audience labels assigned to each custom audience.

Fivetran Platform Connector

We've added a new column, config, to the CONNECTION and GROUP tables.

Freshchat

Freshdesk

Effective August 20, 2026, we have discontinued the TICKET table. You can use the TICKET_HISTORY table, which supports history mode, to access current and historical ticket data. To use the TICKET_HISTORY table, select it in the Schema tab of your connection details page.

Be sure to update your downstream queries to align with this change. Failing to do so may lead to missing or incomplete data in your data pipelines.

Front

We've added a new table, ACTIVITY. The table contains an audit trail of actions taken in your Front workspace, including assignments, comments, tags, mentions, macro triggers, call events, and other conversation activity. Th

GitHub

We've added a new table, ORG_MEMBER.

We have added a new column, role, to the TEAM_MEMBERSHIP table.

Gorgias

Hex

HiBob

HubSpot

We have added the following new tables to sync data for the Courses object:

• COURSE
• COURSE_COMPANY
• COURSE_CONTACT
• COURSE_DEAL
• COURSE_ENGAGEMENT
• COURSE_PIPELINE
• COURSE_PIPELINE_STAGE
• COURSE_PROJECT
• COURSE_PROPERTY_HISTORY
• COURSE_TICKET

We are gradually rolling out this change to all connections.

Kustomer

Effective August 20, 2026, we have discontinued the following tables:

• CONVERSATION
• CONVERSATION_ASSIGNED_TEAM
• CONVERSATION_ASSIGNED_USER
• CONVERSATION_CHANNEL
• CONVERSATION_SUGGESTED_TAG
• CONVERSATION_TAG

You can use the corresponding _HISTORY tables, which support history mode, to access the current and historical conversation data. To use the corresponding _HISTORY tables, select them in the Schema tab of your connection details page. Be sure to update your downstream queries to align with this change. Failing to do so may lead to missing or incomplete data in your data pipelines.

LinkedIn Ad Analytics

We've added a new table, VIDEO. The table contains video media assets referenced by posts, including the download URL, its expiration time, duration, aspect ratio, thumbnail, owner, and processing status.

Microsoft Advertising

We've added the following new tables: CAMPAIGN_PERFORMANCE_DAILY_REPORT_UPCOMING and CAMPAIGN_PERFORMANCE_HOURLY_REPORT_UPCOMING. These tables include the goal and goal_type columns.

OpenAI

We have added the following new tables to store organization admin and usage data:

• CODE_INTERPRETER_SESSION
• FILE_SEARCH_CALL
• IMAGE
• MODERATION
• PROJECT_API_KEY
• VECTOR_STORE_USAGE
• WEB_SEARCH_CALL

Ordway

PagerDuty

Pinterest Ads

We've added a new column, optimization_goal_metadata, to the AD_GROUP_HISTORY table.

Pylon Support Platform

Recharge

We have added two new tables, CHARGE_ACTIVITY and CHARGE_ACTIVITY_PAYMENT_METHOD_INFO. We are gradually rolling out this changes to all existing connections.

Rocketlane

Salesforce Commerce Cloud

We have added the following new tables:

• PRODUCT_IMAGE_GROUP
• PRODUCT_IMAGE_GROUP_IMAGE
• PRODUCT_IMAGE_GROUP_VARIATION_ATTRIBUTE
• PRODUCT_IMAGE_GROUP_VARIATION_ATTRIBUTE_VALUE

We have added the following new locale-specific columns to the PRODUCT table:

• long_description_{locale}_markup
• long_description_{locale}_source
• short_description_{locale}_markup
• short_description_{locale}_source

SAP Concur

We have added a new column, _fivetran_deleted, to all tables in your connection schema. This change applies only when you trigger a table re-sync. During the re-sync, Fivetran uses the _fivetran_deleted column to soft-delete existing records in parent and child tables. It does not affect how we handle deletes during regular incremental syncs. For more information, see our documentation.

We have added a new column, report_id, to the ITEMIZATION table.

We have added the following new tables:

• ATTENDEE_V4
• ATTENDEE_TYPE_V4
• DUPLICATE_SEARCH_FIELD

For information about the OAuth app configuration required to sync these tables, see our setup instructions. If you add the required scopes to your OAuth app after setting up the connection, re-authenticate the connection in Fivetran to obtain a new token that includes the updated scopes.

SAP SuccessFactors

ShipHero

Snapchat Ads

We've added two new columns, objective_v2_type and promotion_type, to the CAMPAIGN_HISTORY table.

Sprout Social

We have added two new columns, impressions and net_sentiment_score, to the THREADS_PROFILE_POST table.

Stripe

We have added a new column, latest_charge_id, to the PAYMENT_INTENT table.

We have added two new tables, CHECKOUT_SESSION_CUSTOM_FIELD and CHECKOUT_SESSION_CUSTOM_FIELD_DROPDOWN_OPTION, to store data from the custom fields of the Checkout Session object.

We have added the following new tables:

• BILLING_METER_EVENT_SUMMARY
• CREDIT_GRANT
• CREDIT_GRANT_APPLICABILITY_CONFIG_SCOPE_PRICES

We have added a new column, connected_account_id, to the CUSTOMER and INVOICE tables to support syncing connected accounts data to these tables.

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

Tableau

Visma

Walmart Marketplace

Workday Financial Management

We have added two new tables, FISCAL_PERIOD and FISCAL_YEAR.

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

Xero

We've added the following new tables:

• BUDGET
• BUDGET_LINE
• BUDGET_BALANCE

To sync data from these tables, follow the steps below based on your connection type:

Web App :

1. In the Fivetran dashboard, go to Edit Connection.
2. Re-authorize the connection.
3. Click Save & Test.

Custom connection :

1. In your custom connection app, add the accounting.budgets.read scope.
2. Click Save and connect.
3. Re-authorize the connection through the app.

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

Zoom

Improvements

Adobe Workfront

You can now specify the Adobe Workfront environment whose data you want to sync when setting up the connection. To support this enhancement, we have added a new field, Environment, to the connection setup form. For more information, see our setup instructions.

ADP Workforce Now

We now mark stale WORKER_TIME_CARD records as deleted during a historical re-sync. When you trigger a historical re-sync, we set _fivetran_deleted = true for records that the ADP API no longer returns within its 15-month lookback window.

Amazon Attribution

You can now select the Amazon Advertising profiles whose data you want to sync. To support this change, we have added an optional field, Profiles to sync, to the connection setup form. For more information, see our setup instructions and REST API documentation.

Amazon DocumentDB

We now support reading change streams from secondary instances for Amazon DocumentDB versions 5.0 and above. We no longer require a connection to the primary instance to perform incremental updates on these versions. Versions below 5.0 only support change streams on the primary instance. For more information, see our Amazon DocumentDB Setup Guide.

If you have an existing connection to an Amazon DocumentDB cluster running version 5.0 or above, and you have confirmed that Fivetran user can access change streams on the secondary instances, you can edit the connection details to connect to the secondary instances and sync from them.

Amazon Selling Partner

We have changed the data type of the following columns in the ITEM_DIMENSION table from BIGINT to DOUBLE PRECISION:

• item_height_value
• item_length_value
• item_weight_value
• item_width_value
• package_height_value
• package_length_value
• package_weight_value
• package_width_value

We have made this change to preserve decimal values in dimension measurements instead of truncating them. We are gradually rolling out this change to all existing connections.

Apple App Store

We now support the Hybrid Deployment model for the Apple App Store connector. Learn more in the Apple App Store setup guide.

Azure Blob Storage

We have added a new authentication method, Microsoft Entra ID - Client credentials grant using client certificate. This authentication method enables you to securely connect using a Microsoft Entra ID service principal and a client certificate.

To support this feature, we have added the following fields to the connection setup form:

• Container name
• Storage account name
• Tenant ID
• Client ID
• Client certificate
• Private key for client certificate

For more information, see our setup instructions.

BigQuery destination

All new connections set up on or after August 28, 2026 preserve null byte characters in string values. Previously, we removed null byte characters before writing string values to the destination, which could cause differences between the source and destination data.

We now preserve NaN and Infinity values in non-primary-key FLOAT and DOUBLE columns instead of syncing them as NULL values. Primary key columns still require valid, non-NaN values. We have made this change for all new connections set up on or after August 18, 2026.

Close

We have improved our Close connector to capture deletes for the LEAD, CONTACT, and OPPORTUNITY tables using webhooks.

When a record is deleted, we now mark it as deleted in your destination by setting _fivetran_deleted = TRUE. Previously, deleted records could only be detected through periodic re-imports.

Databricks destination

All new connections set up on or after August 28, 2026 preserve null byte characters in string values. Previously, we removed null byte characters before writing string values to the destination, which could cause differences between the source and destination data.

We have made the following changes for all new connections set up on or after August 18, 2026:

• We now preserve NaN and Infinity values in non-primary-key FLOAT and DOUBLE columns instead of syncing them as NULL values. Primary key columns still require valid, non-NaN values.
• We now preserve the sign of negative zero (-0.0) instead of normalizing it to 0.0.

Db2 for LUW

We have added support for IBM Db2 for LUW version 12.1. The stored procedures package (fivetran_db2luw_stored_procedures.tar.gz) now includes shared library binaries for Db2 12.1 on Linux, AIX/Unix, and Windows. Download the updated package from the Downloads page.

dbt Cloud Orchestration

We've expanded the list of supported regions in the dbt Cloud orchestration setup form and added a new Service Provider selector.

Previously, only a limited set of regions were available. You can now choose from all current dbt Cloud regions, including cell-based regions that require an account prefix in the access URL.

To update your dbt Cloud orchestration connection to use a different region:

1. In the Fivetran dashboard, click Transformations.
2. Click Manage projects.
3. In the transformation list, click the three dots on the right side of the relevant dbt Cloud project.
4. Click Edit connection settings.
5. Select your Service Provider and Region.
6. Click Save & Test.

Default Sync Mode

You can set a connection-level Sync mode default for new tables that support the selected sync mode.

Existing tables with Soft delete mode, Live mode, or History mode selected keep that table-level selection when you change the connection default. To make an existing table use the connection default, open the table’s Sync mode menu in the Schema tab and select Default. The table then uses the connection’s Sync mode default. If you later change the connection default, tables set to Default follow the new selection.

Selecting Soft delete mode, Live mode, or History mode instead creates or keeps a table-level override. A table shows only the sync modes it supports. If Default is not available, that table has a restricted set of modes and cannot inherit the connection default.

For more information, see Sync modes.

Elasticsearch

We now support Elasticsearch version 9.x. Learn more in our Elasticsearch connector documentation.

Email

We have added a new feature, support for files linked in the email body. You can now define a regex pattern to sync the attachments associated with your email. To support this feature, we have made the following changes to the connection setup form:

• Added a new option , File source, that allows you to choose between Attachment and URL in email body.
• Added a new field, URL link pattern, that allows you to sync files linked in the email body.

For more information, see our setup instructions

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

Facebook Pages

You can now authenticate using a System User Token as an alternative to OAuth. This authentication method is recommended for organizations that don't want to ask their end-users to grant user access, such as digital marketing agencies or Powered by Fivetran users.

For more information about setting up this authentication method, including permissions and access level requirements, see our Facebook Pages setup guide.

GitHub

We've added a new Include commits only from default branch option to the connection setup form. When enabled, we sync only the commits reachable from each repository's default branch. This option significantly reduces the sync duration and API usage for repositories with many branches.

Enabling this option excludes the BRANCH_COMMIT_RELATION and COMMIT_PULL_REQUEST tables from your sync.

Healthie

We have changed our sync strategy for the FORM_ANSWER_GROUP table. We now incrementally sync this table and use a 7-day lookback window to capture delayed updates.

JSON Double Quotes

Effective August 14, 2026, we have improved Fivetran replication for JSON scalar values for all connections. New connections created on or after August 14, 2026, will no longer persist these values with quotes (unless they are strings) in destinations, improving data consistency. Existing connections continue to use their current behavior.

Klaviyo

We can now sync campaign custom reports from Klaviyo. To support this enhancement, we have added a new option, Campaign, to the Type drop-down menu for connections configured in Pack Mode.

Loop

We now support syncing return data in presentment currency, allowing return amounts in the RETURN_OPEN_CLOSED_EXPIRED table to reflect the shopper’s local currency.

Marketo

Our Marketo connector now supports an additional sync of activity data from the previous three days during each incremental sync, to help capture late-arriving activity records. To support this enhancement, we have made the following changes:

• Added a new toggle, Sync Late Arriving Activities, to the connection setup form
• Added a new parameter, trailingSyncEnabled, to the Fivetran REST API

For more information, see our Marketo documentation.

Microsoft Advertising

We updated how we process the view_through_revenue column. Microsoft Advertising returns these values with a comma as a thousands separator (for example, 1,013.99). We now remove the separator and store the values as plain numbers (for example, 1013.99) for consistency with the connector's other metric columns.

This change applies to data synced going forward. If you rely on the previous formatting, update any downstream logic accordingly.

Microsoft Dynamics 365 CRM — Human-readable labels for coded values

We have released a Quickstart package that enables you to enhance Microsoft Dynamics 365 CRM data by adding human-readable labels for coded values and integrating STRINGMAP data into source tables. It creates enriched models with metrics focused on translating codes into meaningful labels for better data analysis. Find out more in our Microsoft Dynamics 365 CRM Data Model documentation.

MongoDB

We no longer support the oplog incremental update method. If your connection was using the oplog incremental update method, syncs will no longer work.

MySQL

If a DATE or DATETIME column contains a value that isn't a valid date or datetime (for example, a zero date like 0000-00-00), we now preserve the original value by promoting the column to STRING instead of syncing it as NULL.

If you have type locking enabled on a connection, this promotion doesn't happen — invalid values are synced as NULL instead, and the column keeps its original type.

We now preserve the zero-sentinel value 0000-00-00 00:00:00 in MySQL and MariaDB TIMESTAMP columns by changing the destination column type to STRING. Previously, we synced this value as NULL.

If you enable type locking for your connection, we keep the existing column type and continue to sync the zero-sentinel value as NULL.

This change affects connectors created on or after August 13, 2026.

MySQL destination

All new connections set up on or after August 28, 2026 preserve null byte characters in string values. Previously, we removed null byte characters before writing string values to the destination, which could cause differences between the source and destination data.

NetSuite SuiteAnalytics

We have upgraded the JDBC driver for the NetSuite SuiteAnalytics connector from version 8.10.184.0 to 8.10.190.0.

Odoo Synconics

We have renamed our Odoo connector, which uses the Synconics REST API module to sync Odoo data, to Odoo Synconics.

Oracle

We support Active Data Guard as the source for the Binary Log Reader incremental sync method in Private Preview.

We support physical standby databases in read-only mode only. However, we still need to connect to the primary database to manage directory objects. For more information about the required settings, see the Binary Log Reader setup instructions.

PagerDuty

We have changed the sync strategy for the following tables and their child tables. We now incrementally sync these tables instead of re-importing them during every sync:

• AUDIT_RECORD
• EVENT_ORCHESTRATION
• PAUSED_INCIDENT_REPORTING_ALERT
• SCHEDULE
• SLACK_DEDICATED_CHANNEL
• TEMPLATE

We have changed the re-import strategy for the following tables and their child tables. We now re-import them once a day to capture updates and deletes. Previously, we re-imported these tables during every sync.

• ADDON
• BUSINESS_SERVICE
• EXTENSION
• EXTENSION_SCHEMA
• INCIDENT_WORKFLOW
• LICENSE
• RULESET
• TAGS
• VENDOR

Pendo

We now support history mode for the following tables:

• ACCOUNT_APPLICATION_HISTORY
• ACCOUNT_HISTORY
• APPLICATION_HISTORY
• FEATURE_ELEMENT_PATH_RULE_HISTORY
• FEATURE_HISTORY
• GUIDE_HISTORY
• GUIDE_STEP_HISTORY
• PAGE_HISTORY
• PAGE_RULE_HISTORY
• STEP_HISTORY
• STEP_POLL_HISTORY
• STEP_THUMBNAIL_URL_HISTORY
• TRACK_TYPE_HISTORY
• TRACK_TYPE_RULE_HISTORY
• VISITOR_ACCOUNT_HISTORY
• VISITOR_APPLICATION_HISTORY
• VISITOR_HISTORY

Pinterest Ads

You can now select Advertiser Targeting, Campaign Targeting, and Ad Group Targeting as breakdown levels for custom reports, along with two new metrics: paid impressions and eCPM. These new targeting levels let you break down account-, campaign-, and ad group-level performance by targeting dimensions, giving you more flexibility to build granular custom reports.

Pylon Support Platform

We have updated our sync strategy and now incrementally sync the ISSUE table. Previously, we re-imported this table weekly.

Sage Intacct

We now support syncing data from custom fields for the PO_DOCUMENT and PO_DOCUMENT_ENTRY tables. To sync this data, you must select the PO_DOCUMENT_PARAMS table in the Schema tab.

Salesforce

We now sync the ConversionRate field in the CURRENCY_TYPE table as BIGDECIMAL instead of DOUBLE. This change corrects small floating-point rounding differences in formula fields that depend on the ConversionRate field. To apply this change, you must drop and resync the CURRENCY_TYPE table.

We have upgraded our Salesforce and Salesforce Sandbox connectors from version 65.0 to 66.0 of the Salesforce REST API. For more information, see Salesforce documentation.

SAP Business ByDesign

We have fixed an issue where columns with address data in the BUSINESS_PARTNER_ADDRESS table were synced as NULL even when valid data for these columns was available in SAP Business ByDesign. By default, we will update the data for this table in a subsequent sync, which will count towards free MAR.

SFTP

We now support authentication using a keypair while configuring your connection using Hybrid Deployment. Previously, the Login with keypair? option was available only for connections configured using the SaaS Deployment model.

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

Shopify

We have improved data integrity for the BALANCE_TRANSACTION table. We now track records that are missing a payout ID and automatically re-sync them after Shopify finalizes the associated payout. This ensures that we backfill the associated_payout_id column when it becomes available. This improvement applies only to incremental data. To backfill the associated_payout_id column for historical records where it is missing, manually re-sync the BALANCE_TRANSACTION table.

Sigma Computing

We have added a new drop-down menu, Environment, to the connection setup form. You can now select the Sigma Computing environment from which you want to sync your data.

For more information, see our Sigma Computing setup guide.

Snowflake destination

All new connections set up on or after August 28, 2026 preserve null byte characters in string values. Previously, we removed null byte characters before writing string values to the destination, which could cause differences between the source and destination data.

We have made the following changes for all new connections set up on or after August 18, 2026:

• We now preserve NaN and Infinity values in non-primary-key FLOAT and DOUBLE columns instead of syncing them as NULL values. Primary key columns still require valid, non-NaN values.
• We now preserve the sign of negative zero (-0.0) instead of normalizing it to 0.0.

We now support using Managed Data Lake Service as the storage layer for Snowflake destinations, allowing you to store your data as Apache Iceberg™ tables in a Fivetran-managed data lake and query those tables from Snowflake. This feature is available for SaaS Deployment only and is currently in beta.

To support this feature, we have added the following fields to the Snowflake destination setup form:

• Table Type: Allows you to select how Fivetran stores the destination data, either in native Snowflake tables or as Iceberg tables in an associated Managed Data Lake Service destination.
• Storage Configuration: Allows you to select an existing Managed Data Lake Service destination to use as the storage layer or create a new data lake.

When you store destination data as Iceberg tables, Fivetran loads the data into the associated Managed Data Lake Service destination and makes the tables available for querying in Snowflake. After each successful data load, Fivetran refreshes the Iceberg metadata in Snowflake so that the corresponding tables reflect the latest data.

For more information, see our Snowflake setup guide.

Apache Iceberg is a trademark of the Apache Software Foundation.

SQL Server

Effective August 5, 2026, we have improved Fivetran Teleport Sync change detection for nullable columns in SQL Server connections. New connections created on or after August 5, 2026, distinguish NULL values from non-NULL values when calculating row hashes, improving data consistency in your destination. Existing connections continue to use their current behavior.

Effective August 7, 2026, we have improved change tracking (CT) accuracy for computed columns in SQL Server connections. New connections created on or after August 7, 2026, exclude non-persisted computed columns from CT syncs if they use nondeterministic expressions that return DATETIME or INTEGER values, such as GETDATE().

Previously, CT syncs evaluated these expressions when processing historical changes. As a result, the synced value could differ from the value at the time of the change, causing incorrect data in your destination. Existing connections continue to use their current behavior.

To resume syncing an excluded computed column, update it to use a deterministic expression.

Effective August 20, 2026, we've improved change tracking (CT) history mode syncs for SQL Server connections. New connections created on or after August 20, 2026, handle temporarily unavailable transaction metadata without omitting affected rows.

Previously, delays in the availability of SQL Server transaction metadata could cause some rows to be omitted during historical data processing. Existing connections continue to use their current behavior.

SQL Server destination

All new connections set up on or after August 28, 2026 preserve null byte characters in string values. Previously, we removed null byte characters before writing string values to the destination, which could cause differences between the source and destination data.

Square

We have fixed an issue that prevented new data from syncing to the CASH_DRAWER and CASH_DRAWER_EVENT tables. We will perform a one-time historical sync to backfill any missing data from these tables. This re-sync counts toward Free Monthly Active Rows (MAR).

Stripe

We have expanded the DISCOUNT table to store discounts associated with subscription items. We are gradually rolling out this change to all existing connections.

Workday Adaptive Planning

We have added a new configuration option, Select all, to the Dimensions field in the connection setup form to allow you to select or deselect all available dimensions at once while configuring custom reports. For more information, see our setup instructions.

Zoho CRM

We can now sync data from Zoho accounts hosted in the Canada region. To support this enhancement, we have added a Canada option to the Data Center drop-down menu in the connection setup form. For more information, see our setup instructions.

REST API Improvements

Added 402 response for the Create a Destination endpoint

Our Create a Destination endpoint now returns 402 Payment Required response when the selected destination region or private networking is not available for your account plan.

Connection Schema API

The Connection Schema response now includes a new read-only parent_table field for tables that are grouped under a parent (core) table. The field contains the name of the parent table and only appears in the response for child tables. This allows API consumers, such as Terraform, to accurately reconcile schema configuration state.

Retrieve Move Connection Job Status REST API (Beta)

You can now check the status of asynchronous connection move operations using the Retrieve Move Connection Job Status (Beta) REST API endpoint. This endpoint allows you to monitor the progress of move jobs initiated with the CONTINUE_WITH_DATA sync behavior.

Row filtering in connection schema config

The Modify connection schema config endpoint now supports row filtering for individual tables.

See the full list of changes below:

• Each table in a schema update request now accepts a row_filter field of type RowFilterUpdateRequest. Setting this field creates or replaces the row filter for that table; sending null deletes the existing row filter; omitting the field leaves the existing row filter unchanged.
• A row filter consists of a name (required), a description (required), and between 1 and 10 column_clauses. Each clause specifies a column (max 500 characters), a column_type, an operator, and a list of values (each value max 1,000 characters). All clauses are combined with a logical AND, so only rows satisfying every clause are synced to your destination.
• The Retrieve connection schema config response now includes a row_filtering_supported boolean at the top level. The field is true when the connector type supports row filtering. The field is false when the connector does not support row filtering. The field is omitted when row filtering information is not available.
• The row_filter for each table is included in both GET and PATCH responses when row_filtering_supported is true. The field is omitted from a table's response when no filter is configured.
• Creating or removing a row filter triggers a historical resync for the affected table.

Supported operators depend on the column type:

Value format requirements by column type: