June 2026

Connector SDK

`fivetran-connector-sdk` PyPI package

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

The fivetran debug command now logs peak memory usage at the end of a debug run.
Added validation during fivetran init.
Minor enhancements and improvements.

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

fivetran init now supports Copilot plugins allowing users to leverage AI capabilities for faster and more efficient connector development.
We've deprecated the --force and -f flags and introduced a new --non-interactive flag for better clarity and user experience.
Updated the CLI to point to renamed repositories.
Minor enhancements and improvements.
Updated testers.

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

Updated fivetran init command to install fivetran-connector-sdk@fivetran-connector-sdk-ai plugin, which provides AI-powered features for connector development.
Improved prompts for dependency validations during package and deploy commands.
Minor enhancements and improvements.
Updated testers.

Lite Connectors

Lite connectors are now available for the following sources:

Managed Data Lake Service

You can now update the HTTP path of the Databricks cluster associated with a Unity Catalog for existing data lakes. To ensure compatibility, the new HTTP path must belong to a cluster in the same Unity Catalog and Databricks workspace.

Quickstart Package Updates

Quickstart data model package updates

v1.8.1

Under the Hood

Removes unused using_purchase variable from int_quickbooks__purchase_transactions.

v2.6.1

Bug Fixes

Updates macro argument type annotations in macros_docs.yml to support dbt's validate_macro_args flag.

v1.6.1

Bug Fix

Fixes a Snowflake runtime error in netsuite2__transaction_details caused by timestamp datatype mismatches.

v1.6.3

Bug Fix

Fixes Postgres/Redshift unknown datatype errors by explicitly casting string literals in our models as strings.

v1.6.2

Bug Fix

Corrects vendor credit account selection in int_quickbooks__vendor_credit_double_entry so credit_account_id uses expense_account_id before falling back to parent_income_account_id or income_account_id.
- IMPORTANT: credit_account_id may change for vendor credits with multiple available account options.

v1.0.1

PR #35 includes the following update.

Bug Fix

Fixes a runtime error in stg_workday__worker_history where annual_currency_summary_primary_compensation_basis, annual_currency_summary_total_base_pay, and annual_currency_summary_total_salary_and_allowances failed to cast when the value was non-numeric. These columns now resolve to null instead of erroring the run.

v0.9.2

PR #33 includes the following update.

Bug Fix

Fixes an issue in stg_workday__worker_history where annual_currency_summary_primary_compensation_basis, annual_currency_summary_total_base_pay, and annual_currency_summary_total_salary_and_allowances could surface as strings instead of numeric values. These columns are now cast to float when the source type is a string.

v1.4.0

Under the Hood

Migrates the union_connections, apply_source_relation, and partition_by_source_relation macros to the dbt_fivetran_utils package.
Adds the fivetran_using_source_casing variable for case-sensitive destination support. When enabled, downstream transformations respect source casing to ensure consistent results. See the Additional Configurations section of the README for details.

v1.10.0

Under the Hood

Migrates the union_connections, apply_source_relation, and partition_by_source_relation macros to the dbt_fivetran_utils package.
Adds the fivetran_using_source_casing variable for case-sensitive destination support. When enabled, downstream transformations respect source casing to ensure consistent results. See the Additional Configurations section of the README for details.

v1.4.0

Under the Hood

Migrates the union_connections, apply_source_relation, and partition_by_source_relation macros to the dbt_fivetran_utils package.
Adds the fivetran_using_source_casing variable for case-sensitive destination support. When enabled, downstream transformations respect source casing to ensure consistent results. See the Additional Configurations section of the README for details.

v1.4.0

Under the Hood

Migrates the union_connections, apply_source_relation, and partition_by_source_relation macros to the dbt_fivetran_utils package.
Adds the fivetran_using_source_casing variable for case-sensitive destination support. When enabled, downstream transformations respect source casing to ensure consistent results. See the Additional Configurations section of the README for details.

v1.4.0

Under the Hood

Migrates the union_connections, apply_source_relation, and partition_by_source_relation macros to the dbt_fivetran_utils package.
Adds the fivetran_using_source_casing variable for case-sensitive destination support. When enabled, downstream transformations respect source casing to ensure consistent results. See the Additional Configurations section of the README for details.

v1.4.0

Under the Hood

Migrates the union_connections, apply_source_relation, and partition_by_source_relation macros to the dbt_fivetran_utils package.
Adds the fivetran_using_source_casing variable for case-sensitive destination support. When enabled, downstream transformations respect source casing to ensure consistent results. See the Additional Configurations section of the README for details.

v1.8.0

Under the Hood

Migrates the union_connections, apply_source_relation, and partition_by_source_relation macros to the dbt_fivetran_utils package.
Adds the fivetran_using_source_casing variable for case-sensitive destination support. When enabled, downstream transformations respect source casing to ensure consistent results. See the Additional Configurations section of the README for details.

v1.4.0

Under the Hood

Migrates the union_connections, apply_source_relation, and partition_by_source_relation macros to the dbt_fivetran_utils package.
Adds the fivetran_using_source_casing variable for case-sensitive destination support. When enabled, downstream transformations respect source casing to ensure consistent results. See the Additional Configurations section of the README for details.

v1.7.0

Under the Hood

Migrates the union_connections, apply_source_relation, and partition_by_source_relation macros to the dbt_fivetran_utils package.
Adds the fivetran_using_source_casing variable for case-sensitive destination support. When enabled, downstream transformations respect source casing to ensure consistent results. See the Additional Configurations section of the README for details.

v1.5.0

Under the Hood

Migrates the union_connections, apply_source_relation, and partition_by_source_relation macros to the dbt_fivetran_utils package.
Adds the fivetran_using_source_casing variable for case-sensitive destination support. When enabled, downstream transformations respect source casing to ensure consistent results. See the Additional Configurations section of the README for details.

v1.7.0

Under the Hood

Migrates the union_connections, apply_source_relation, and partition_by_source_relation macros to the dbt_fivetran_utils package.
Adds the fivetran_using_source_casing variable for case-sensitive destination support. When enabled, downstream transformations respect source casing to ensure consistent results. See the Additional Configurations section of the README for details.

v1.5.0

Under the Hood

Migrates the union_connections, apply_source_relation, and partition_by_source_relation macros to the dbt_fivetran_utils package.
Adds the fivetran_using_source_casing variable for case-sensitive destination support. When enabled, downstream transformations respect source casing to ensure consistent results. See the Additional Configurations section of the README for details.

v1.4.0

Under the Hood

Migrates the union_connections, apply_source_relation, and partition_by_source_relation macros to the dbt_fivetran_utils package.
Adds the fivetran_using_source_casing variable for case-sensitive destination support. When enabled, downstream transformations respect source casing to ensure consistent results. See the Additional Configurations section of the README for details.

v1.3.0

Under the Hood

Migrates the union_connections, apply_source_relation, and partition_by_source_relation macros to the dbt_fivetran_utils package.
Adds the fivetran_using_source_casing variable for case-sensitive destination support. When enabled, downstream transformations respect source casing to ensure consistent results. See the Additional Configurations section of the README for details.

v0.17.0

Under the Hood

Migrates the union_connections, apply_source_relation, and partition_by_source_relation macros to the dbt_fivetran_utils package.
Adds the fivetran_using_source_casing variable for case-sensitive destination support. When enabled, downstream transformations respect source casing to ensure consistent results. See the Additional Configurations section of the README for details.

v1.4.0

Under the Hood

Migrates the union_connections, apply_source_relation, and partition_by_source_relation macros to the dbt_fivetran_utils package.
Adds the fivetran_using_source_casing variable for case-sensitive destination support. When enabled, downstream transformations respect source casing to ensure consistent results. See the Additional Configurations section of the README for details.

v0.2.0

Under the Hood

Migrates the union_connections, apply_source_relation, and partition_by_source_relation macros to the dbt_fivetran_utils package.
Adds the fivetran_using_source_casing variable for case-sensitive destination support. When enabled, downstream transformations respect source casing to ensure consistent results. See the Additional Configurations section of the README for details.

v1.4.0

Under the Hood

Migrates the union_connections, apply_source_relation, and partition_by_source_relation macros to the dbt_fivetran_utils package.
Adds the fivetran_using_source_casing variable for case-sensitive destination support. When enabled, downstream transformations respect source casing to ensure consistent results. See the Additional Configurations section of the README for details.

v0.4.0

Under the Hood

Migrates the union_connections, apply_source_relation, and partition_by_source_relation macros to the dbt_fivetran_utils package.
Adds the fivetran_using_source_casing variable for case-sensitive destination support. When enabled, downstream transformations respect source casing to ensure consistent results. See the Additional Configurations section of the README for details.

v0.5.0

Under the Hood

Migrates the union_connections, apply_source_relation, and partition_by_source_relation macros to the dbt_fivetran_utils package.
Adds the fivetran_using_source_casing variable for case-sensitive destination support. When enabled, downstream transformations respect source casing to ensure consistent results. See the Additional Configurations section of the README for details.

v1.8.2

Schema/Data Change

1 total change • 0 possible breaking changes

Data Model(s)	Change type	Old	New	Notes
`stg_shopify_gql__customer_visit`	New column		`is_most_recent_order_visit`	Boolean field indicating whether this visit is the most recent for a given order.

Bug Fix

Fixes duplicate records in shopify_gql__orders when multiple customer visits are attributed to the same order.
Fixes duplicate rows in shopify_gql__order_lines for order lines that belong to multiple fulfillment orders.
Fixes a model failure that occurred when checkout_id was absent from the source.

v1.10.1

Bug Fix

Fixes a runtime error on Snowflake and BigQuery that occurred when an issue's concatenated comments exceeded the warehouse's string length limit. The conversation field in jira__issue_enhanced now returns 'conversation too long to render' for those issues instead of failing the entire run. count_comments is unaffected. The character threshold defaults to 16,777,216 (16MB) but can be lowered using the jira_conversation_char_limit variable. See the README for configuration details and the DECISIONLOG for per-warehouse details.

v1.4.0

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

1 total change • 1 possible breaking change

Data Model(s)	Change type	Old	New	Notes
All models	`source_relation` column (when using a single stripe schema)	Empty string (`''`)	`<database>.<schema>`

Under the Hood

Migrates the union_connections, apply_source_relation, and partition_by_source_relation macros to the dbt_fivetran_utils package.
Adds the fivetran_using_source_casing variable for case-sensitive destination support. When enabled, downstream transformations respect source casing to ensure consistent results. See the Additional Configurations section of the README for details.

v1.4.0

Under the Hood

Updated int_zuora__transaction_date_spine model to reference stg_zuora__invoice vs stg_zuora__invoice_tmp when generating the date spine in order to ensure source casing compatibility.
Updated int_zuora__mrr_date_spine model to reference stg_zuora__invoice_item vs stg_zuora__invoice_item_tmp when generating the date spine in order to ensure source casing compatibility.
Migrates the union_connections, apply_source_relation, and partition_by_source_relation macros to the dbt_fivetran_utils package.
Adds the fivetran_using_source_casing variable for case-sensitive destination support. When enabled, downstream transformations respect source casing to ensure consistent results. See the Additional Configurations section of the README for details.

v1.8.0

Schema/Data Change

3 total changes • 0 possible breaking changes

Data Model(s)	Change type	Old	New	Notes
`quickbooks__inventory_item_activity`	New model	—	—	New line-level view of all item-bearing transactions, including item enrichment details, inventory quantity, unit price, and status indicators for inventory movement analysis.
`stg_quickbooks__item`	New fields	—	`description`, `stock_keeping_unit`, `quantity_on_hand`, `track_quantity_on_hand`, `fully_qualified_name`	Fields were present in the source but not previously exposed in the model.
`stg_quickbooks__purchase_order_line` `stg_quickbooks__bill_line` `stg_quickbooks__purchase_line`	New fields	—	`item_expense_quantity`, `item_expense_unit_price`	Fields were present in the source but not previously exposed in the model.

v1.5.0

Breaking Changes

Source table identifier variables have been renamed to include the recurly_ prefix for consistency with other Fivetran dbt packages and to ensure union functionality works as expected. If you have configured any identifier variables in your project, update them to the new format (e.g., account_history_identifier → recurly_account_history_identifier).

Under the Hood

Migrates the union_connections, apply_source_relation, and partition_by_source_relation macros to the dbt_fivetran_utils package.
Adds the fivetran_using_source_casing variable for case-sensitive destination support. When enabled, downstream transformations respect source casing to ensure consistent results. See the Additional Configurations section of the README for details.
Removed column from get_billing_info_history_columns() macro which is not referenced in staging model.

v1.3.0

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

1 total change • 1 possible breaking change

Data Model(s)	Change type	Old	New	Notes
All models	`source_relation` column (when not using the union connections of the same type feature)	Empty string (`''`)	`<database>.<schema>`

Feature Updates

Introduces the new (recommended) {connector_name}_sources variables for more robust union data configuration. The old {connector_name}_union_schemas and {connector_name}_union_databases variables will still be supported. See the README for specific details.

Upstream Dependency Changes

Increases the required Google Play package to version 1.3.0
Increases the required Apple Store package to version 1.3.0

v1.8.0

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

1 total change • 2 possible breaking change

Data Model(s)	Change type	Old	New	Notes
All models	`source_relation` column (when using a single stripe schema)	Empty string (`''`)	`<database>.<schema>`
All models	`source_relation` column (when using `stripe_union_schemas` or `stripe_union_databases` schema)	`<database>.<schema>`	only `<schema>` or `<database>` respectively	Updated to align with standard applied to other Fivetran packages.

Under the Hood

Migrates the union_connections, apply_source_relation, and partition_by_source_relation macros to the dbt_fivetran_utils package.
Adds the fivetran_using_source_casing variable for case-sensitive destination support. When enabled, downstream transformations respect source casing to ensure consistent results. See the Additional Configurations section of the README for details.

v1.3.0

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

1 total change • 1 possible breaking change

Data Model(s)	Change type	Old	New	Notes
All models	`source_relation` column (when not using the union connections of the same type feature)	Empty string (`''`)	`<database>.<schema>`

Feature Updates

Introduces the new (recommended) {connector_name}_sources variables for more robust union data configuration. The old {connector_name}_union_schemas and {connector_name}_union_databases variables will still be supported. See the README for specific details.

Upstream Dependency Changes

Increases the required Shopify package to version v1.9.0.
Increases the required Klaviyo package to version v1.4.0.

v1.4.0

Schema/Data Changes

1 total change • 0 possible breaking changes

Data Model	Change Type	Old	New	Notes
All models	`source_relation` column (when using a single TikTok Ads schema)	Empty string (`''`)	`<database>.<schema>`

Feature Updates

Introduces the new (recommended) tiktok_ads_sources variable for more robust union data configuration. The old tiktok_ads_union_schemas and tiktok_ads_union_databases variables will still be supported. See the README for specific details.

Under the Hood

Adds the fivetran_using_source_casing variable for case-sensitive destination support. When enabled, downstream transformations respect source casing to ensure consistent results. See the Additional Configurations section of the README for details.
Introduces fivetran_utils.partition_by_source_relation to conditionally include source_relation in partition clauses only when multiple sources are configured.

v1.7.0

Schema/Data Changes

1 total change

Data Model(s)	Change type	Old	New	Notes
All models	`source_relation` column (when using a single QuickBooks schema)	Empty string (`''`)	`<database>.<schema>`	Full refresh required after upgrading.

Feature Updates

Introduces the new (recommended) quickbooks_sources variable for more robust union data configuration. The old quickbooks_union_schemas and quickbooks_union_databases variables will still be supported. See the README for specific details.

Under the Hood

Adds the fivetran_using_source_casing variable for case-sensitive destination support. When enabled, downstream transformations respect source casing to ensure consistent results. See the Additional Configurations section of the README for details.
Updates partition_by_source_relation macro to conditionally include source_relation in partition clauses only when multiple sources are configured.

v1.4.0

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

1 total change • 1 possible breaking change

Data Model(s)	Change type	Old	New	Notes
All models	`source_relation` column (when using a single Klaviyo schema)	Empty string (`''`)	`<database>.<schema>`

Feature Updates

Introduces the new (recommended) klaviyo_sources variable for more robust union data configuration. The old klaviyo_union_schemas and klaviyo_union_databases variables will still be supported. See the README for specific details.

Under the Hood

Adds the fivetran_using_source_casing variable for case-sensitive destination support. When enabled, downstream transformations respect source casing to ensure consistent results. See the Additional Configurations section of the README for details.
Introduces fivetran_utils.partition_by_source_relation to conditionally include source_relation in partition clauses only when multiple sources are configured.

v0.3.0

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

1 total change • 1 possible breaking change

Data Model(s)	Change type	Old	New	Notes
All models	`source_relation` column (when using a single Unified Rag schema)	Empty string (`''`)	`<database>.<schema>`

Feature Updates

Introduces the new (recommended) rag_*_sources variable for more robust union data configuration. The old rag_*_union_schemas and rag_*_union_databases variables will still be supported. See the README for specific details.

Under the Hood

Adds the fivetran_using_source_casing variable for case-sensitive destination support. When enabled, downstream transformations respect source casing to ensure consistent results. See the Additional Configurations section of the README for details.
Introduces fivetran_utils.partition_by_source_relation to conditionally include source_relation in partition clauses only when multiple sources are configured.

v1.3.0

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

1 total change • 1 possible breaking change

Data Model(s)	Change type	Old	New	Notes
All models	`source_relation` column (when using a single amazon_ads schema)	Empty string (`''`)	`<database>.<schema>`

Feature Updates

Introduces the new (recommended) amazon_ads_sources variable for more robust union data configuration. The oldamazon_ads_union_schemas and amazon_ads_union_databases variables will still be supported. See the README for specific details.

Under the Hood

Adds the fivetran_using_source_casing variable for case-sensitive destination support. When enabled, downstream transformations respect source casing to ensure consistent results. See the Additional Configurations section of the README for details.
Introduces fivetran_utils.partition_by_source_relation to conditionally include source_relation in partition clauses only when multiplesources are configured.

v1.4.0

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

1 total change • 1 possible breaking change

Data Model(s)	Change type	Old	New	Notes
All models	`source_relation` column (when using a single Google Ads schema)	Empty string (`''`)	`<database>.<schema>`

Feature Updates

Introduces the new (recommended) google_ads_sources variable for more robust union data configuration. The old google_ads_union_schemas and google_ads_union_databases variables will still be supported. See the README for specific details.

Under the Hood

Adds the fivetran_using_source_casing variable for case-sensitive destination support. When enabled, downstream transformations respect source casing to ensure consistent results. See the Additional Configurations section of the README for details.
Introduces fivetran_utils.partition_by_source_relation to conditionally include source_relation in partition clauses only when multiple sources are configured.

v1.5.0

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

1 total change • 1 possible breaking change

Data Model(s)	Change type	Old	New	Notes
All models	`source_relation` column (when using a single reddit_ads schema)	Empty string (`''`)	`<database>.<schema>`

Feature Updates

Introduces the new (recommended) reddit_ads_sources variable for more robust union data configuration. The old reddit_ads_union_schemas and reddit_ads_union_databases variables will still be supported. See the README for specific details.

Under the Hood

Adds the fivetran_using_source_casing variable for case-sensitive destination support. When enabled, downstream transformations respect source casing to ensure consistent results. See the Additional Configurations section of the README for details.
Introduces fivetran_utils.partition_by_source_relation to conditionally include source_relation in partition clauses only when multiple sources are configured.

v1.0.0

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

1 total change • 1 possible breaking change

Data Model(s)	Change type	Old	New	Notes
All models	`source_relation` column (when using a single servicenow schema)	Empty string (`''`)	`<database>.<schema>`

Feature Updates

Introduces the new (recommended) servicenow_sources variable for more robust union data configuration. The old servicenow_union_schemas and servicenow_union_databases variables will still be supported. See the README for specific details.

Under the Hood

Adds the fivetran_using_source_casing variable for case-sensitive destination support. When enabled, downstream transformations respect source casing to ensure consistent results. See the Additional Configurations section of the README for details.
Introduces fivetran_utils.partition_by_source_relation to conditionally include source_relation in partition clauses only when multiple sources are configured.

v1.3.0

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

1 total change • 1 possible breaking change

Data Model(s)	Change type	Old	New	Notes
All models	`source_relation` column (when using a single LinkedIn Ads schema)	Empty string (`''`)	`<database>.<schema>`

Feature Updates

Introduces the new (recommended) linkedin_ads_sources variable for more robust union data configuration. The oldlinkedin_ads_union_schemas and linkedin_ads_union_databases variables will still be supported. See the README for specific details.

Under the Hood

Adds the fivetran_using_source_casing variable for case-sensitive destination support. When enabled, downstream transformations respect source casing to ensure consistent results. See the Additional Configurations section of the README for details.
Introduces fivetran_utils.partition_by_source_relation to conditionally include source_relation in partition clauses only when multiplesources are configured.

v1.3.0

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

1 total change • 1 possible breaking change

Data Model(s)	Change type	Old	New	Notes
All models	`source_relation` column (when using a single Apple Store schema)	Empty string (`''`)	`<database>.<schema>`

Feature Updates

Introduces the new (recommended) apple_store_sources variable for more robust union data configuration. The old apple_store_union_schemas and apple_store_union_databases variables will still be supported. See the README for specific details.

Under the Hood

Adds the fivetran_using_source_casing variable for case-sensitive destination support. When enabled, downstream transformations respect source casing to ensure consistent results. See the Additional Configurations section of the README for details.
Introduces fivetran_utils.partition_by_source_relation to conditionally include source_relation in partition clauses only when multiple sources are configured.

v1.3.0

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

1 total change • 1 possible breaking change

Data Model(s)	Change type	Old	New	Notes
All models	`source_relation` column (when using a single Google Play schema)	Empty string (`''`)	`<database>.<schema>`

Feature Updates

Introduces the new (recommended) google_play_sources variable for more robust union data configuration. The old google_play_union_schemas and google_play_union_databases variables will still be supported. See the README for specific details.

Under the Hood

Adds the fivetran_using_source_casing variable for case-sensitive destination support. When enabled, downstream transformations respect source casing to ensure consistent results. See the Additional Configurations section of the README for details.
Introduces fivetran_utils.partition_by_source_relation to conditionally include source_relation in partition clauses only when multiple sources are configured.

v1.5.0

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

1 total change • 1 possible breaking change

Data Model(s)	Change type	Old	New	Notes
All models	`source_relation` column (when using a single facebook_ads schema)	Empty string (`''`)	`<database>.<schema>`

Feature Updates

Introduces the new (recommended) facebook_ads_sources variable for more robust union data configuration. The oldfacebook_ads_union_schemas and facebook_ads_union_databases variables will still be supported. See the README for specific details.

Under the Hood

Adds the fivetran_using_source_casing variable for case-sensitive destination support. When enabled, downstream transformations respect source casing to ensure consistent results. See the Additional Configurations section of the README for details.
Introduces fivetran_utils.partition_by_source_relation to conditionally include source_relation in partition clauses only when multiplesources are configured.

v1.3.0

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

1 total change • 1 possible breaking change

Data Model(s)	Change type	Old	New	Notes
All models	`source_relation` column (when using a single Snapchat Ads schema)	Empty string (`''`)	`<database>.<schema>`

Feature Updates

Introduces the new (recommended) snapchat_ads_sources variable for more robust union data configuration. The old snapchat_ads_union_schemas and snapchat_ads_union_databases variables will still be supported. See the README for specific details.

Under the Hood

Adds the fivetran_using_source_casing variable for case-sensitive destination support. When enabled, downstream transformations respect source casing to ensure consistent results. See the Additional Configurations section of the README for details.
Introduces fivetran_utils.partition_by_source_relation to conditionally include source_relation in partition clauses only when multiple sources are configured.

v1.3.0

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

1 total change • 1 possible breaking change

Data Model(s)	Change type	Old	New	Notes
All models	`source_relation` column (when using a single facebook_pages schema)	Empty string (`''`)	`<database>.<schema>`

Feature Updates

Introduces the new (recommended) facebook_pages_sources variable for more robust union data configuration. The old facebook_pages_union_schemas and facebook_pages_union_databases variables will still be supported. See the README for specific details.

Under the Hood

Adds the fivetran_using_source_casing variable for case-sensitive destination support. When enabled, downstream transformations respect source casing to ensure consistent results. See the Additional Configurations section of the README for details.
Introduces fivetran_utils.partition_by_source_relation to conditionally include source_relation in partition clauses only when multiple sources are configured.

v1.2.0

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

1 total change • 1 possible breaking change

Data Model(s)	Change type	Old	New	Notes
All models	`source_relation` column (when using a single Twitter Organic schema)	Empty string (`''`)	`<database>.<schema>`

Feature Updates

Introduces the new (recommended) twitter_organic_sources variable for more robust union data configuration. The old twitter_organic_union_schemas and twitter_organic_union_databases variables will still be supported. See the README for specific details.

Under the Hood

Adds the fivetran_using_source_casing variable for case-sensitive destination support. When enabled, downstream transformations respect source casing to ensure consistent results. See the Additional Configurations section of the README for details.
Introduces fivetran_utils.partition_by_source_relation to conditionally include source_relation in partition clauses only when multiple sources are configured.

v1.3.0

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

1 total change • 1 possible breaking change

Data Model(s)	Change type	Old	New	Notes
All models	`source_relation` column (when using a single apple_search_ads schema)	Empty string (`''`)	`<database>.<schema>`

Feature Updates

Introduces the new (recommended) apple_search_ads_sources variable for more robust union data configuration. The oldapple_search_ads_union_schemas and apple_search_ads_union_databases variables will still be supported. See the README for specific details.

Under the Hood

Adds the fivetran_using_source_casing variable for case-sensitive destination support. When enabled, downstream transformations respect source casing to ensure consistent results. See the Additional Configurations section of the README for details.
Introduces fivetran_utils.partition_by_source_relation to conditionally include source_relation in partition clauses only when multiplesources are configured.

v1.2.0

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

1 total change • 1 possible breaking change

Data Model(s)	Change type	Old	New	Notes
All models	`source_relation` column (when using a single YouTube Analytics schema)	Empty string (`''`)	`<database>.<schema>`

Feature Updates

Introduces the new (recommended) youtube_analytics_sources variable for more robust union data configuration. The old youtube_analytics_union_schemas and youtube_analytics_union_databases variables will still be supported. See the README for specific details.

Under the Hood

Adds the fivetran_using_source_casing variable for case-sensitive destination support. When enabled, downstream transformations respect source casing to ensure consistent results. See the Additional Configurations section of the README for details.
Introduces fivetran_utils.partition_by_source_relation to conditionally include source_relation in partition clauses only when multiple sources are configured.

v1.2.0

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

1 total change • 1 possible breaking change

Data Model(s)	Change type	Old	New	Notes
All models	`source_relation` column (when using a single Instagram Business schema)	Empty string (`''`)	`<database>.<schema>`

Feature Updates

Introduces the new (recommended) instagram_business_sources variable for more robust union data configuration. The old instagram_business_union_schemas and instagram_business_union_databases variables will still be supported. See the README for specific details.

Under the Hood

Adds the fivetran_using_source_casing variable for case-sensitive destination support. When enabled, downstream transformations respect source casing to ensure consistent results. See the Additional Configurations section of the README for details.
Introduces fivetran_utils.partition_by_source_relation to conditionally include source_relation in partition clauses only when multiple sources are configured.

v1.0.0

PR #34 includes the following updates.

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

1 total change • 1 possible breaking change

Data Model(s)	Change type	Old	New	Notes
All models	`source_relation` column (when using a single Workday schema)	Empty string (`''`)	`<database>.<schema>`

Feature Updates

Introduces the new (recommended) workday_sources variable for more robust union data configuration. The old workday_union_schemas and workday_union_databases variables will still be supported. See the README for specific details.

Under the Hood

Adds the fivetran_using_source_casing variable for case-sensitive destination support. When enabled, downstream transformations respect source casing to ensure consistent results. See the Additional Configurations section of the README for details.
Introduces fivetran_utils.partition_by_source_relation to conditionally include source_relation in partition clauses only when multiple sources are configured.

v0.6.0

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

1 total change • 1 possible breaking change

Data Model(s)	Change type	Old	New	Notes
All models	`source_relation` column (when using a single Salesforce Marketing Cloud schema)	Empty string (`''`)	`<database>.<schema>`

Feature Updates

Introduces the new (recommended) salesforce_marketing_cloud_sources variable for more robust union data configuration. The old salesforce_marketing_cloud_union_schemas and salesforce_marketing_cloud_union_databases variables will still be supported. See the README for specific details.

Under the Hood

Adds the fivetran_using_source_casing variable for case-sensitive destination support. When enabled, downstream transformations respect source casing to ensure consistent results. See the Additional Configurations section of the README for details.
Introduces fivetran_utils.partition_by_source_relation to conditionally include source_relation in partition clauses only when multiple sources are configured.

v1.6.1

Schema/Data Change

1 total change • 1 possible breaking change

Data Model	Change type	Old	New	Notes
`zendesk__sla_policies` `int_zendesk__agent_work_time_business_hours` `int_zendesk__agent_work_time_filtered_statuses` `int_zendesk__reply_time_business_hours` `int_zendesk__reply_time_combined` `int_zendesk__requester_wait_time_business_hours` `int_zendesk__requester_wait_time_filtered_statuses` `int_zendesk__sla_policy_applied`	New column		`priority_applied`	The priority level that was active when each SLA event was applied.

Feature Enhancement

Updates SLA models to use historical priority levels when applying SLA targets. SLA events now reference the priority that was in effect at the time the event occurred, rather than the current priority. This ensures tickets with priority changes over time receive accurate SLA target calculations.

Bug Fix

Ensures first reply time records in zendesk__sla_policies use the proper schedule when calculating elapsed business minutes.
Ensures the proper priority SLA target is used in cases where the priority was changed immediately after ticket creation.

v1.4.0

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

1 total change • 1 possible breaking change

Data Model(s)	Change type	Old	New	Notes
All models	`source_relation` column (when using a single LinkedIn Pages schema)	Empty string (`''`)	`<database>.<schema>`

Feature Updates

Introduces the new (recommended) linkedin_pages_sources variable for more robust union data configuration. The old linkedin_pages_union_schemas and linkedin_pages_union_databases variables will still be supported. See the README for specific details.

Under the Hood

Adds the fivetran_using_source_casing variable for case-sensitive destination support. When enabled, downstream transformations respect source casing to ensure consistent results. See the Additional Configurations section of the README for details.
Introduces fivetran_utils.partition_by_source_relation to conditionally include source_relation in partition clauses only when multiple sources are configured.
Removed unnecessary --depends-on config within stg_linkedin_pages__organization_tmp.

v1.3.0

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

1 total change • 1 possible breaking change

Data Model(s)	Change type	Old	New	Notes
All models	`source_relation` column (when using a single qualtrics schema)	Empty string (`''`)	`<database>.<schema>`

Feature Updates

Introduces the new (recommended) qualtrics_sources variable for more robust union data configuration. The oldqualtrics_union_schemas and qualtrics_union_databases variables will still be supported. See the README for specific details.

Under the Hood

Adds the fivetran_using_source_casing variable for case-sensitive destination support. When enabled, downstream transformations respect source casing to ensure consistent results. See the Additional Configurations section of the README for details.
Introduces fivetran_utils.partition_by_source_relation to conditionally include source_relation in partition clauses only when multiplesources are configured.
Removed qualtrics.qualtrics_union_data and replaced the references with the standardized fivetran_utils.union_data macro.

v1.7.0

Schema/Data Change

2 total changes • 1 possible breaking change

Data Model(s)	Change type	Old	New	Notes
(Breaking) `stg_intercom__tag`, `stg_intercom__company_tag_history`, `stg_intercom__contact_tag_history`, `stg_intercom__conversation_tag_history`	Changed data type	integer	string	Casts `tag_id` as a string so joins succeed regardless of source type.
`stg_intercom__company_history`, `stg_intercom__company_tag_history`, `stg_intercom__contact_company_history`	explicit data type cast	source data type	string	Casts `company_id` as a string for consistent join keys.

Bug Fix

Resolves a Database Error in intercom__company_enhanced (and other tag-joined models) caused by mismatched tag_id data types. The fix casts all ID join keys to string in staging. See the Schema/Data Change table above.

Under the Hood

Migrates the union_connections, apply_source_relation, and partition_by_source_relation macros to the dbt_fivetran_utils package.
Adds the fivetran_using_source_casing variable for case-sensitive destination support. When enabled, downstream transformations respect source casing to ensure consistent results. See the Additional Configurations section of the README for details.

v1.6.0

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

1 total change • 1 possible breaking change

Data Model(s)	Change type	Old	New	Notes
All models	`source_relation` column (when not using the union connections of the same type feature)	Empty string (`''`)	`<database>.<schema>`

Feature Updates

Introduces the new (recommended) {connector_name}_sources variables for more robust union data configuration. The old {connector_name}_union_schemas and {connector_name}_union_databases variables will still be supported. See the README for specific details.

Upstream Dependency Changes

Increases the required Facebook Pages package to version 1.3.0
Increases the required Instagram Business package to version 1.2.0
Increases the required Twitter Organic package to version 1.2.0
Increases the required LinkedIn Pages package to version 1.4.0
Increases the required YouTube Analytics package to version 1.4.0

v1.3.0

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

1 total change • 1 possible breaking change

Data Model(s)	Change type	Old	New	Notes
All models	`source_relation` column (when using a single Microsoft Ads schema)	Empty string (`''`)	`<database>.<schema>`

Feature Updates

Introduces the new (recommended) microsoft_ads_sources variable for more robust union data configuration. The old microsoft_ads_union_schemas and microsoft_ads_union_databases variables will still be supported. See the README for specific details.

Bug Fixes

Renamed the source identifier variable for geographic_performance_daily_report.
- new: microsoft_ads_geographic_performance_daily_report_identifier
- previous: microsoft_ads_geographic_history_identifier

Under the Hood

Adds the fivetran_using_source_casing variable for case-sensitive destination support. When enabled, downstream transformations respect source casing to ensure consistent results. See the Additional Configurations section of the README for details.
Introduces fivetran_utils.partition_by_source_relation to conditionally include source_relation in partition clauses only when multiple sources are configured.

v1.3.0

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

2 total changes • 1 possible breaking change

Data Model(s)	Change type	Old	New	Notes
All models	`source_relation` column (when using a single lever schema)	Empty string (`''`)	`<database>.<schema>`
`user` `interviewer_user`	Sunset legacy source tables			See note below

As of August 2025, all Lever connectors use the current users and interview_user table names. The lever__using_users and lever__using_interview_user variables have been removed alongside the legacy source definitions.

Feature Updates

Introduces the new (recommended) lever_sources variable for more robust union data configuration. The old lever_union_schemas and lever_union_databases variables will still be supported. See the README for specific details.

Under the Hood

Adds the fivetran_using_source_casing variable for case-sensitive destination support. When enabled, downstream transformations respect source casing to ensure consistent results. See the Additional Configurations section of the README for details.
Introduces fivetran_utils.partition_by_source_relation to conditionally include source_relation in partition clauses only when multiple sources are configured.

v1.9.0

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

1 total change • 1 possible breaking change

Data Model(s)	Change type	Old	New	Notes
All models	`source_relation` column (when using a single Shopify schema)	Empty string (`''`)	`<database>.<schema>`

Breaking Changes

Shopify GraphQL table identifier variables have been renamed (shopify_gql_* → shopify_graphql_*) for consistency with other Fivetran dbt packages and to ensure union functionality works as expected. If you have configured any identifier variables in your project, update them to the new format.

Feature Updates

Introduces the new (recommended) shopify_sources variable for more robust union data configuration. The old shopify_union_schemas and shopify_union_databases variables will still be supported. See the README for specific details.

Under the Hood

Adds the fivetran_using_source_casing variable for case-sensitive destination support. When enabled, downstream transformations respect source casing to ensure consistent results. See the Additional Configurations section of the README for details.
Introduces fivetran_utils.partition_by_source_relation macro and replaces the shopify_partition_by_cols macro to conditionally include source_relation in partition clauses only when multiple sources are configured.

v1.3.0

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

1 total change • 1 possible breaking change

Data Model(s)	Change type	Old	New	Notes
All models	`source_relation` column (when using a single Pinterest schema)	Empty string (`''`)	`<database>.<schema>`

Feature Updates

Introduces the new (recommended) pinterest_ads_schema and pinterest_ads_database variables for defining the source schema and database respectively. The previous pinterest_schema and pinterest_database variables are still supported for backwards compatibility. This feature was applied to ensure consistent variable naming standards across Fivetran dbt packages.
Introduces the new (recommended) pinterest_ads_sources variable for more robust union data configuration. The old pinterest_ads_union_schemas and pinterest_ads_union_databases variables will still be supported. See the README for specific details.

Under the Hood

Adds the fivetran_using_source_casing variable for case-sensitive destination support. When enabled, downstream transformations respect source casing to ensure consistent results. See the Additional Configurations section of the README for details.
Introduces fivetran_utils.partition_by_source_relation to conditionally include source_relation in partition clauses only when multiple sources are configured.

v2.7.0

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

1 total change • 1 possible breaking change

Data Model(s)	Change type	Old	New	Notes
All models	`source_relation` column (when not using the union connections of the same type feature)	Empty string (`''`)	`<database>.<schema>`

Feature Updates

Introduces the new (recommended) {connector_name}_sources variables for more robust union data configuration. The old {connector_name}_union_schemas and {connector_name}_union_databases variables will still be supported. See the README for specific details.

Upstream Dependency Changes

Increases the required Amazon Ads package to version 1.3.0
Increases the required Apple Search Ads package to version 1.3.0
Increases the required Facebook Ads package to version 1.5.0
Increases the required Google Ads package to version 1.4.0
Increases the required LinkedIn Ads package to version 1.3.0
Increases the required Microsoft Ads package to version 1.3.0
Increases the required Pinterest Ads package to version 1.3.0
Increases the required Reddit Ads package to version 1.5.0
Increases the required Snapchat Ads package to version 1.3.0
Increases the required TikTok Ads package to version 1.3.0
Increases the required Twitter Ads package to version 1.3.0

Under the Hood

Adds the fivetran_using_source_casing variable for case-sensitive destination support. When enabled, downstream transformations respect source casing to ensure consistent results. See the Additional Configurations section of the README for details.
Introduces fivetran_utils.partition_by_source_relation to conditionally include source_relation in partition clauses only when multiple sources are configured.

Syncing empty columns

Our Files connectors now support creating empty columns and columns with null values in your destination. During the initial sync, we create these empty columns with the STRING data type. However, if the column later contains non-null values in subsequent syncs, we update the column data type based on the data type we infer from the schema. Previously, we did not support creating empty columns or columns with null values in your destination.

We support this enhancement only for the following File connectors set up using BigQuery, Databricks, and Snowflake as destinations:

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

Transformations for dbt Core

Automatic dbt Core patch version updates

We have added a new Automatically use latest patch version toggle to the dbt Core project setup form.

When enabled, the dbt Core Version dropdown shows minor versions with the current latest patch in parentheses (for example, 1.9 (1.9.10), 1.10 (1.10.22)). Fivetran automatically uses the latest patch release within the selected minor version as new patches become available.

When disabled, the dbt Core Version dropdown shows full patch versions (for example, 1.9.4, 1.9.8, 1.10.3), and you must select the exact version.

You can toggle between automatic and manual patch version management at any time. To access this setting, do the following:

In the Fivetran dashboard, click Transformations.
Click Manage projects.
In the transformation list, click the three dots on the right side of the relevant dbt project.
Click Edit connection settings.

Schema changes

15Five

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

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

5 total changes • 0 possible breaking changes

Table/column	Change type	New name
`HIGH_FIVE`
table	New Table	`HIGH_FIVE`
`HIGH_FIVE_EMAIL_RECEIVER`
table	New Table	`HIGH_FIVE_EMAIL_RECEIVER`
`HIGH_FIVE_RECEIVER`
table	New Table	`HIGH_FIVE_RECEIVER`
`REVIEW_CYCLE`
table	New Table	`REVIEW_CYCLE`
`REVIEW_CYCLE_PARTICIPANT`
table	New Table	`REVIEW_CYCLE_PARTICIPANT`

Aircall

Effective June 9, 2026 we use a new June 2026 schema. Review the latest ERD to better understand the schema changes.

We are updating the connector schema to 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
`AIRCALL_TO_PARTNER_CAMPAIGN`
table	Discontinued Table		`AIRCALL_TO_PARTNER_CAMPAIGN`

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

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

1 total changes • 0 possible breaking changes

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

Alchemer

We have added a new column, parent, to the SURVEY_DATA table.

Amazon DSP

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

detail_page_views
video_ad_complete
video_ad_first_quartile
video_ad_start

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

Amazon Selling Partner

Effective June 25, 2026, we are updating the primary keys and composite primary keys for the following tables to resolve data integrity issues and make each record uniquely identifiable:

Table name	Current primary key columns	New primary key columns	Notes
`COMPETITIVE_PRICE_TYPE`	`asin` and `id`	`asin`, `id`, and `marketplace_id`
`CPT_TRADE_IN_VALUE`	`asin`	`asin` and `marketplace_id`
`ITEM_BUY_BOX_PRICE_TYPE`	`asin`	`asin`, `condition`, and `marketplace_id`
`ITEM_OFFER_COUNT_TYPE`	`asin` and `type`	`asin`, `condition`, `marketplace_id`, and `type`
`ITEM_OFFER_DETAIL`	`asin`, `index`, and `subcondition`	`asin`, `index`, `marketplace_id`, and `subcondition`
`ITEM_OFFER_LOWEST_PRICE_TYPE`	`asin`	`asin`, `condition`, and `marketplace_id`
`ITEM_OFFER_SUMMARY`	`asin`	`asin`, `condition`, `marketplace_id`
`ITEM_QUANTITY_DISCOUNT_PRICE_TYPE`	`asin`	`asin`, `condition`, and `marketplace_id`
`ITEM_SALES_RANK_TYPE`	`asin`	`asin` and `marketplace_id`
`SETTLEMENT_REPORT`	`amount_description`, `fulfillment_id`, `order_id`, `settlement_id`, `shipment_id`, and `transaction_type`	`_fivetran_id`	The `_fivetran_id` column is a hash of all columns in the report.

On June 25, 2026, we will re-sync all the affected tables. During the re-sync, you may experience longer sync times depending on the volume of data in the affected tables. Before June 25, 2026, review and update any downstream queries, models, and workflows that reference these tables to use the new primary key columns. Failing to do so may lead to missing or incomplete data in your data pipelines.

We have added two new columns, amount_charged and qty_charged, to the LONG_TERM_STORAGE_FEE_CHARGES_REPORT table.

Apollo

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

We are updating the connector schema to enhance its usability.

2 total changes • 0 possible breaking changes

Table/column	Change type	New name
`DEAL`
table	New Table	`DEAL`
`DEAL_STAGE`
table	New Table	`DEAL_STAGE`

Apple App Store

We've added a new table, APP_STORE_RETENTION_MESSAGING. The table contains data about how users interact with retention messages during the subscription cancellation flow, including event counts broken down by subscription tier, message type, device, territory, and platform version.

AppLovin

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

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

40 total changes • 0 possible breaking changes

Table/column	Change type	New name
`ADVERTISER_REPORT`
column	New Column	`chka_usd_0d`
column	New Column	`chka_usd_14d`
column	New Column	`chka_usd_7d`
column	New Column	`cost_per_target_event_0d`
column	New Column	`cpp_0d`
column	New Column	`cpp_14d`
column	New Column	`cpp_7d`
column	New Column	`nc_d0_checkout`
column	New Column	`nc_d0_checkout_rev`
column	New Column	`nc_d0_cpp`
column	New Column	`nc_d0_roas`
column	New Column	`nc_percent_d0_checkout`
column	New Column	`nc_percent_d0_checkout_rev`
column	New Column	`roas_0d`
column	New Column	`roas_14d`
column	New Column	`roas_28d`
column	New Column	`sales_0d`
column	New Column	`sales_14d`
column	New Column	`sales_28d`
column	New Column	`target_event_count_0d`
`PROBABILISTIC_REPORT`
column	New Column	`chka_usd_0d`
column	New Column	`chka_usd_14d`
column	New Column	`chka_usd_7d`
column	New Column	`cost_per_target_event_0d`
column	New Column	`cpp_0d`
column	New Column	`cpp_14d`
column	New Column	`cpp_7d`
column	New Column	`nc_d0_checkout`
column	New Column	`nc_d0_checkout_rev`
column	New Column	`nc_d0_cpp`
column	New Column	`nc_d0_roas`
column	New Column	`nc_percent_d0_checkout`
column	New Column	`nc_percent_d0_checkout_rev`
column	New Column	`roas_0d`
column	New Column	`roas_14d`
column	New Column	`roas_7d`
column	New Column	`sales_0d`
column	New Column	`sales_14d`
column	New Column	`sales_28d`
column	New Column	`target_event_count_0d`

Birdeye

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

We are updating the connector schema to resolve data integrity issues.

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

3 total changes • 3 possible breaking changes

Table/column	Change type	Old name	New name	Notes
`CONTACT_MAPPING`
column	Primary Key Change	`mapping_business_id` 🔑	`mapping_business_id`	No longer a primary key.
column	Primary Key Change	`mapping_customer_id` 🔑	`mapping_customer_id`	No longer a primary key.
column	Primary Key Change		`index` 🔑	Added to primary key.

Bitly

Effective June 18, 2026 we use a new June 2026 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.

2 total changes • 2 possible breaking changes

Table/column	Change type	Old name
`QR_CODE_PNG`
table	Discontinued table	`QR_CODE_PNG`
`QR_CODE_SVG`
table	Discontinued table	`QR_CODE_SVG`

Brevo

Effective June 18, 2026 we use a new June 2026 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
`TRANSACTIONAL_EMAIL_EVENT`
table	New Table			`TRANSACTIONAL_EMAIL_EVENT`

Brightpearl

Effective June 22, 2026 we use a new June 2026 schema. Review the latest ERD to better understand the schema changes.

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

4 total changes • 0 possible breaking changes

Table/column	Change type	New name
`JOURNAL`
table	New Table	`JOURNAL`
`JOURNAL_TRANSACTION`
table	New Table	`JOURNAL_TRANSACTION`
`NOMINAL_CODE`
table	New Table	`NOMINAL_CODE`
`TAX_CODE`
table	New Table	`TAX_CODE`

Brivo

Effective June 11, 2026 we use a new June 2026 schema. Review the latest ERD to better understand the schema changes.

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

5 total changes • 0 possible breaking changes

Table/column	Change type	New name
`CONTROL_PANEL`
table	New Table	`CONTROL_PANEL`
`CREDENTIAL`
table	New Table	`CREDENTIAL`
`CREDENTIAL_FIELD_VALUE`
table	New Table	`CREDENTIAL_FIELD_VALUE`
`HOLIDAY`
table	New Table	`HOLIDAY`
`USER_CREDENTIAL`
table	New Table	`USER_CREDENTIAL`

Calendly

Effective June 2, 2026 we use a new June 2026 schema. Review the latest ERD to better understand the schema changes.

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

6 total changes • 0 possible breaking changes

Table/column	Change type	New name
`EVENT`
column	New Column	`location_extra`
column	New Column	`location_id`
column	New Column	`location_join_url`
column	New Column	`location_password`
column	New Column	`location_settings`
column	New Column	`location_status`

CallRail

Effective June 17, 2026 we use a new June 2026 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.

1 total changes • 1 possible breaking changes

Table/column	Change type		Old name	New name	Notes
`MILESTONE`
column	Primary Key Change		`form_submission` 🔑	`form_submission`	No longer a primary key.

Centra

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

We are updating the connector schema to enhance its usability.

7 total changes • 0 possible breaking changes

Table/column	Change type	New name
`SHIPMENT`
table	New Table	`SHIPMENT`
`SHIPMENT_ALLOCATION`
table	New Table	`SHIPMENT_ALLOCATION`
`SHIPMENT_APPLIED_TAX_RULE`
table	New Table	`SHIPMENT_APPLIED_TAX_RULE`
`SHIPMENT_INVOICE`
table	New Table	`SHIPMENT_INVOICE`
`SHIPMENT_INVOICE_LINE`
table	New Table	`SHIPMENT_INVOICE_LINE`
`SHIPMENT_LINE`
table	New Table	`SHIPMENT_LINE`
`SHIPMENT_RETURN`
table	New Table	`SHIPMENT_RETURN`

Cin7 Core

Effective June 16, 2026 we use a new June 2026 schema. Review the latest ERD to better understand the schema changes.

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

27 total changes • 0 possible breaking changes

Table/column	Change type	New name
`FACTORY_CALENDAR`
table	New Table	`FACTORY_CALENDAR`
`FACTORY_CALENDAR_DAY`
table	New Table	`FACTORY_CALENDAR_DAY`
`FACTORY_CALENDAR_SPECIAL_DAY`
table	New Table	`FACTORY_CALENDAR_SPECIAL_DAY`
`PRODUCT_FAMILY_PRODUCTION_BOM`
table	New Table	`PRODUCT_FAMILY_PRODUCTION_BOM`
`PRODUCT_FAMILY_PRODUCTION_BOM_OPERATION`
table	New Table	`PRODUCT_FAMILY_PRODUCTION_BOM_OPERATION`
`PRODUCT_PRODUCTION_BOM`
table	New Table	`PRODUCT_PRODUCTION_BOM`
`PRODUCT_PRODUCTION_BOM_COMPONENT`
table	New Table	`PRODUCT_PRODUCTION_BOM_COMPONENT`
`PRODUCT_PRODUCTION_BOM_NOTE`
table	New Table	`PRODUCT_PRODUCTION_BOM_NOTE`
`PRODUCT_PRODUCTION_BOM_OPERATION`
table	New Table	`PRODUCT_PRODUCTION_BOM_OPERATION`
`PRODUCT_PRODUCTION_BOM_OUTPUT_PRODUCT`
table	New Table	`PRODUCT_PRODUCTION_BOM_OUTPUT_PRODUCT`
`PRODUCT_PRODUCTION_BOM_RESOURCE`
table	New Table	`PRODUCT_PRODUCTION_BOM_RESOURCE`
`PRODUCTION_BOM_FINISHED_PRODUCT`
table	New Table	`PRODUCTION_BOM_FINISHED_PRODUCT`
`PRODUCTION_BOM_OPERATION_LINK`
table	New Table	`PRODUCTION_BOM_OPERATION_LINK`
`PRODUCTION_BOM_RESOURCE`
table	New Table	`PRODUCTION_BOM_RESOURCE`
`PRODUCTION_BOM_VARIATION_COMPONENT`
table	New Table	`PRODUCTION_BOM_VARIATION_COMPONENT`
`PRODUCTION_ORDER`
table	New Table	`PRODUCTION_ORDER`
`PRODUCTION_ORDER_SOURCE_TASK`
table	New Table	`PRODUCTION_ORDER_SOURCE_TASK`
`PRODUCTION_RESOURCE`
table	New Table	`PRODUCTION_RESOURCE`
`PRODUCTION_RUN`
table	New Table	`PRODUCTION_RUN`
`PRODUCTION_RUN_OPERATION`
table	New Table	`PRODUCTION_RUN_OPERATION`
`PRODUCTION_RUN_OPERATION_COMPONENT`
table	New Table	`PRODUCTION_RUN_OPERATION_COMPONENT`
`PRODUCTION_RUN_RESOURCE`
table	New Table	`PRODUCTION_RUN_RESOURCE`
`PRODUCTION_RUN_TRACEABILITY`
table	New Table	`PRODUCTION_RUN_TRACEABILITY`
`SUSPEND_REASON`
table	New Table	`SUSPEND_REASON`
`SUSPEND_REASON_WORKCENTER`
table	New Table	`SUSPEND_REASON_WORKCENTER`
`WORK_CENTER`
table	New Table	`WORK_CENTER`
`WORK_CENTER_LOCATION`
table	New Table	`WORK_CENTER_LOCATION`

commercetools

We have added two new tables, PRODUCT_TYPE and PRODUCT_TYPE_ATTRIBUTE.

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

discounted_value_cent_amount
discounted_value_currency_code
discounted_value_fraction_digits
discounted_value_precise_amount
discounted_value_type

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

Confluence

Effective June 22, 2026 we use a new June 2026 schema. Review the latest ERD to better understand the schema changes.

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

4 total changes • 0 possible breaking changes

Table/column	Change type	New name
`PAGE_ANCESTOR`
table	New Table	`PAGE_ANCESTOR`
`PAGE_LABEL`
column	New Column	`name`
column	New Column	`prefix`
`PAGE_LIKE`
table	New Table	`PAGE_LIKE`

Coupa

We have added a new table, EXTERNAL_PAYMENT. We are gradually rolling out this change to all existing connections.

Cvent

Effective June 19, 2026 we use a new June 2026 schema. Review the latest ERD to better understand the schema changes.

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

5 total changes • 0 possible breaking changes

Table/column	Change type	New name
`ATTENDEE_LINK`
table	New Table	`ATTENDEE_LINK`
`CONTACT_CUSTOM_FIELD`
table	New Table	`CONTACT_CUSTOM_FIELD`
`CUSTOM_FIELD`
table	New Table	`CUSTOM_FIELD`
`PLAYER`
table	New Table	`PLAYER`
`WEBCAST`
table	New Table	`WEBCAST`

dbt Cloud

Effective June 16, 2026 we use a new June 2026 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.

6 total changes • 2 possible breaking changes

Table/column	Change type	Old name	New name	Notes
`AUTH_PROVIDER_USER_GROUPS`
column	Primary Key Change	`users_id` 🔑	`users_id`	No longer a primary key.
`IP_RESTRICTION`
table	New Table		`IP_RESTRICTION`
`IP_RESTRICTION_CIDR`
table	New Table		`IP_RESTRICTION_CIDR`
`OAUTH_CONFIGURATION`
table	New Table		`OAUTH_CONFIGURATION`
`PERMISSION_STATEMENT`
column	Primary Key Change	`permission_id` 🔑	`permission_id`	No longer a primary key.
`WEBHOOK_EVENT`
table	New Table		`WEBHOOK_EVENT`

Dixa

Effective June 18, 2026 we use a new June 2026 schema. Review the latest ERD to better understand the schema changes.

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

2 total changes • 0 possible breaking changes

Table/column	Change type	New name
`AGENT_PRESENCE`
table	New Table	`AGENT_PRESENCE`
`AGENT_PRESENCE_ACTIVE_CHANNEL`
table	New Table	`AGENT_PRESENCE_ACTIVE_CHANNEL`

Docebo

Effective June 18, 2026 we use a new June 2026 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
`COURSE_ENROLLMENT_DETAILS`
table	New Table			`COURSE_ENROLLMENT_DETAILS`

Drata

Effective June 30, 2026 we use a new June 2026 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.

83 total changes • 40 possible breaking changes

Table/column	Change type	Old name	New name	Notes
`CONTROL`
column	Discontinued Column	`has_evidence`
column	Discontinued Column	`has_owner`
column	Discontinued Column	`has_ticket`
column	Discontinued Column	`is_monitored`
column	Discontinued Column	`is_ready`
column	New Column		`activity`
column	New Column		`control_template_id`
column	New Column		`created_at`
column	New Column		`flag_has_evidence`
column	New Column		`flag_has_owner`
column	New Column		`flag_has_policy`
column	New Column		`flag_has_ticket`
column	New Column		`flag_is_monitored`
column	New Column		`flag_is_ready`
column	New Column		`question`
column	New Column		`updated_at`
column	Primary Key Change		`workspace_id` 🔑	New primary key
`CONTROL_CUSTOM_FIELD`
table	New Table		`CONTROL_CUSTOM_FIELD`
`CONTROL_MAPPED_REQUIREMENT`
column	New Column		`created_at`
column	New Column		`external_id`
column	New Column		`updated_at`
column	Primary Key Change		`workspace_id` 🔑	New primary key
`CONTROL_OWNER`
column	Discontinued Column	`avatar_url`
column	Discontinued Column	`drata_terms_agreed_at`
column	Discontinued Column	`job_title`
column	Primary Key Change		`workspace_id` 🔑	New primary key
`MONITOR`
column	Discontinued Column	`auto_enabled_at`
column	Discontinued Column	`check_status`
column	Discontinued Column	`disabled_message`
column	Discontinued Column	`disabling_user`
column	Discontinued Column	`disabling_user_id`
column	Discontinued Column	`graph`
column	Discontinued Column	`last_check`
column	Discontinued Column	`priority`
column	New Column		`disabled_by_user_id`
column	Primary Key Change		`workspace_id` 🔑	New primary key
`MONITOR_CONTROL`
column	Discontinued Column	`activity`
column	Discontinued Column	`archived_at`
column	Discontinued Column	`question`
column	Discontinued Column	`slug`
column	New Column		`created_at`
column	New Column		`is_ready`
column	New Column		`updated_at`
column	Primary Key Change		`workspace_id` 🔑	New primary key
`MONITOR_INSTANCE`
column	Discontinued Column	`autopilot_task_type`
column	Discontinued Column	`check_frequency`
column	Discontinued Column	`enabled`
column	Discontinued Column	`evidence_collection_description`
column	Discontinued Column	`failed_test_description`
column	Discontinued Column	`remedy_description`
column	Discontinued Column	`url`
column	New Column		`collection_description`
column	Primary Key Change		`workspace_id` 🔑	New primary key
`MONITOR_INSTANCE_CHECK_TYPE`
table	Discontinued Table	`MONITOR_INSTANCE_CHECK_TYPE`
`MONITOR_INSTANCE_EXCLUSION`
column	Discontinued Column	`monitor_id` 🔑		No longer a primary key
column	Primary Key Change		`test_id` 🔑	New primary key
column	Primary Key Change		`workspace_id` 🔑	New primary key
`MONITOR_INSTANCE_METADATA`
table	Discontinued Table	`MONITOR_INSTANCE_METADATA`
`MONITOR_INSTANCE_METADATA_EXCLUSION`
table	Discontinued Table	`MONITOR_INSTANCE_METADATA_EXCLUSION`
`MONITOR_INSTANCE_METADATA_PASS_FAIL`
table	Discontinued Table	`MONITOR_INSTANCE_METADATA_PASS_FAIL`
`MONITORING_TEST_FAIL`
table	New Table		`MONITORING_TEST_FAIL`
`POLICY`
table	New Table		`POLICY`
`POLICY_CONTROL`
table	New Table		`POLICY_CONTROL`
`POLICY_GRACE_PERIOD_SLA`
table	New Table		`POLICY_GRACE_PERIOD_SLA`
`POLICY_GROUP`
table	New Table		`POLICY_GROUP`
`POLICY_P3_MATRIX_SLA`
table	New Table		`POLICY_P3_MATRIX_SLA`
`POLICY_VERSION`
table	New Table		`POLICY_VERSION`
`POLICY_VERSION_GRACE_PERIOD_SLA`
table	New Table		`POLICY_VERSION_GRACE_PERIOD_SLA`
`POLICY_VERSION_P3_MATRIX_SLA`
table	New Table		`POLICY_VERSION_P3_MATRIX_SLA`
`POLICY_VERSION_WEEK_TIME_FRAME_SLA`
table	New Table		`POLICY_VERSION_WEEK_TIME_FRAME_SLA`
`POLICY_WEEK_TIME_FRAME_SLA`
table	New Table		`POLICY_WEEK_TIME_FRAME_SLA`
`RISK`
table	New Table		`RISK`
`RISK_CATEGORY`
table	New Table		`RISK_CATEGORY`
`RISK_CONTROL`
table	New Table		`RISK_CONTROL`
`RISK_CUSTOM_FIELD`
table	New Table		`RISK_CUSTOM_FIELD`
`RISK_DOCUMENT`
table	New Table		`RISK_DOCUMENT`
`RISK_NOTE`
table	New Table		`RISK_NOTE`
`RISK_OWNER`
table	New Table		`RISK_OWNER`
`RISK_REGISTER`
table	New Table		`RISK_REGISTER`
`RISK_REGISTER_OWNER`
table	New Table		`RISK_REGISTER_OWNER`
`RISK_REVIEWER`
table	New Table		`RISK_REVIEWER`
`RISK_TASK`
table	New Table		`RISK_TASK`
`RISK_TICKET`
table	New Table		`RISK_TICKET`

Employment Hero

Effective June 5, 2026 we use a new June 2026 schema. Review the latest ERD to better understand the schema changes.

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

2 total changes • 0 possible breaking changes

Table/column	Change type	New name
`PAYSLIP_DISPLAYED_ACCRUED_LEAVE`
table	New Table	`PAYSLIP_DISPLAYED_ACCRUED_LEAVE`
`PAYSLIP_DISPLAYED_LEAVE_BALANCE`
table	New Table	`PAYSLIP_DISPLAYED_LEAVE_BALANCE`

Facebook Ads

We have deprecated the dma breakdown. Meta has removed it from their Ads Insights API. Custom reports that contain the dma breakdown will stop syncing.

We have deprecated the DEMOGRAPHICS_DMA_REGION prebuilt report because it relies on the dma breakdown. If you have this report configured, it will no longer sync data. We recommend switching to the DEMOGRAPHICS_COMSCORE_MARKET prebuilt report instead.

Forethought

We've added the following new tables:

WORKFLOW.
EVENT_CONFIGURATION.
PROPERTY.
AI_QA_INSIGHT.
CUSTOM_EVENT.
EMAIL_CONVERSATION.
TICKET_REPLY.

We have added new columns, detected_workflows, ending_sentiment_score, relevance_rating, relevance_reasoning, user_engagement, dropoff_reasoning, is_eligible, voice_metric_call_start_time, voice_metric_call_end_time, voice_metric_call_duration, voice_metric_sentiment, voice_metric_avg_response_time, and voice_metric_is_outbound, to the CONVERSATION_HISTORY table.

Front

We've added the following new tables:

MESSAGE_TEMPLATE
MESSAGE_TEMPLATE_ATTACHMENT
MESSAGE_TEMPLATE_FOLDER
MESSAGE_TEMPLATE_INBOX

Genesys

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

We are updating the connector schema to support feature enhancements.

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.

73 total changes • 50 possible breaking changes

Table/column	Change type	Old name	New name
`ACTIVITY_CODE`
table	New Table		`ACTIVITY_CODE`
`ACTIVITY_CODE_SECONDARY_PRESENCE`
table	New Table		`ACTIVITY_CODE_SECONDARY_PRESENCE`
`CONVERSATION`
table	Discontinued Table	`CONVERSATION`
`CONVERSATION_DIVISION`
table	Discontinued Table	`CONVERSATION_DIVISION`
`CONVERSATION_DIVISION_ENTITY`
table	Discontinued Table	`CONVERSATION_DIVISION_ENTITY`
`CONVERSATION_ID`
table	Discontinued Table	`CONVERSATION_ID`
`CONVERSATION_PARTICIPANT`
table	Discontinued Table	`CONVERSATION_PARTICIPANT`
`CONVERSATION_PARTICIPANT_CALL`
table	Discontinued Table	`CONVERSATION_PARTICIPANT_CALL`
`CONVERSATION_PARTICIPANT_CALL_DISCONNECT_REASON`
table	Discontinued Table	`CONVERSATION_PARTICIPANT_CALL_DISCONNECT_REASON`
`CONVERSATION_PARTICIPANT_CALL_SEGMENT`
table	Discontinued Table	`CONVERSATION_PARTICIPANT_CALL_SEGMENT`
`CONVERSATION_PARTICIPANT_CALL_WRAPUP_TAG`
table	Discontinued Table	`CONVERSATION_PARTICIPANT_CALL_WRAPUP_TAG`
`CONVERSATION_PARTICIPANT_CALLBACK`
table	Discontinued Table	`CONVERSATION_PARTICIPANT_CALLBACK`
`CONVERSATION_PARTICIPANT_CALLBACK_NUMBER`
table	Discontinued Table	`CONVERSATION_PARTICIPANT_CALLBACK_NUMBER`
`CONVERSATION_PARTICIPANT_CALLBACK_SEGMENT`
table	Discontinued Table	`CONVERSATION_PARTICIPANT_CALLBACK_SEGMENT`
`CONVERSATION_PARTICIPANT_CALLBACK_WRAPUP_TAG`
table	Discontinued Table	`CONVERSATION_PARTICIPANT_CALLBACK_WRAPUP_TAG`
`CONVERSATION_PARTICIPANT_CHAT`
table	Discontinued Table	`CONVERSATION_PARTICIPANT_CHAT`
`CONVERSATION_PARTICIPANT_CHAT_SEGMENT`
table	Discontinued Table	`CONVERSATION_PARTICIPANT_CHAT_SEGMENT`
`CONVERSATION_PARTICIPANT_CHAT_WRAPUP_TAG`
table	Discontinued Table	`CONVERSATION_PARTICIPANT_CHAT_WRAPUP_TAG`
`CONVERSATION_PARTICIPANT_CONVERSATION_COBROWSE_SESSION`
table	Discontinued Table	`CONVERSATION_PARTICIPANT_CONVERSATION_COBROWSE_SESSION`
`CONVERSATION_PARTICIPANT_CONVERSATION_COBROWSE_SESSION_CONTROLLING`
table	Discontinued Table	`CONVERSATION_PARTICIPANT_CONVERSATION_COBROWSE_SESSION_CONTROLLING`
`CONVERSATION_PARTICIPANT_CONVERSATION_COBROWSE_SESSION_SEGMENT`
table	Discontinued Table	`CONVERSATION_PARTICIPANT_CONVERSATION_COBROWSE_SESSION_SEGMENT`
`CONVERSATION_PARTICIPANT_CONVERSATION_COBROWSE_SESSION_WRAPUP_TAG`
table	Discontinued Table	`CONVERSATION_PARTICIPANT_CONVERSATION_COBROWSE_SESSION_WRAPUP_TAG`
`CONVERSATION_PARTICIPANT_CONVERSATION_ROUTING_DATA_SCORED_AGENT`
table	Discontinued Table	`CONVERSATION_PARTICIPANT_CONVERSATION_ROUTING_DATA_SCORED_AGENT`
`CONVERSATION_PARTICIPANT_CONVERSATION_ROUTING_DATA_SKILLS`
table	Discontinued Table	`CONVERSATION_PARTICIPANT_CONVERSATION_ROUTING_DATA_SKILLS`
`CONVERSATION_PARTICIPANT_EMAIL`
table	Discontinued Table	`CONVERSATION_PARTICIPANT_EMAIL`
`CONVERSATION_PARTICIPANT_EMAIL_DRAFT_ATTACHMENT`
table	Discontinued Table	`CONVERSATION_PARTICIPANT_EMAIL_DRAFT_ATTACHMENT`
`CONVERSATION_PARTICIPANT_EMAIL_SEGMENT`
table	Discontinued Table	`CONVERSATION_PARTICIPANT_EMAIL_SEGMENT`
`CONVERSATION_PARTICIPANT_EMAIL_WRAPUP_TAG`
table	Discontinued Table	`CONVERSATION_PARTICIPANT_EMAIL_WRAPUP_TAG`
`CONVERSATION_PARTICIPANT_EVALUATION`
table	Discontinued Table	`CONVERSATION_PARTICIPANT_EVALUATION`
`CONVERSATION_PARTICIPANT_EVALUATION_ANSWERS_QUESTION_GROUP_SCORE`
table	Discontinued Table	`CONVERSATION_PARTICIPANT_EVALUATION_ANSWERS_QUESTION_GROUP_SCORE`
`CONVERSATION_PARTICIPANT_EVALUATION_ANSWERS_TRANSCRIPT_TOPIC`
table	Discontinued Table	`CONVERSATION_PARTICIPANT_EVALUATION_ANSWERS_TRANSCRIPT_TOPIC`
`CONVERSATION_PARTICIPANT_EVALUATION_AUTHORIZED_ACTION`
table	Discontinued Table	`CONVERSATION_PARTICIPANT_EVALUATION_AUTHORIZED_ACTION`
`CONVERSATION_PARTICIPANT_EVALUATION_FORM_QUESTION_GROUP`
table	Discontinued Table	`CONVERSATION_PARTICIPANT_EVALUATION_FORM_QUESTION_GROUP`
`CONVERSATION_PARTICIPANT_EVALUATION_MEDIA_TYPE`
table	Discontinued Table	`CONVERSATION_PARTICIPANT_EVALUATION_MEDIA_TYPE`
`CONVERSATION_PARTICIPANT_MEDIA_ROLE`
table	Discontinued Table	`CONVERSATION_PARTICIPANT_MEDIA_ROLE`
`CONVERSATION_PARTICIPANT_MESSAGE`
table	Discontinued Table	`CONVERSATION_PARTICIPANT_MESSAGE`
`CONVERSATION_PARTICIPANT_MESSAGE_SEGMENT`
table	Discontinued Table	`CONVERSATION_PARTICIPANT_MESSAGE_SEGMENT`
`CONVERSATION_PARTICIPANT_MESSAGE_WRAPUP_TAG`
table	Discontinued Table	`CONVERSATION_PARTICIPANT_MESSAGE_WRAPUP_TAG`
`CONVERSATION_PARTICIPANT_SCREENSHARE`
table	Discontinued Table	`CONVERSATION_PARTICIPANT_SCREENSHARE`
`CONVERSATION_PARTICIPANT_SCREENSHARE_SEGMENT`
table	Discontinued Table	`CONVERSATION_PARTICIPANT_SCREENSHARE_SEGMENT`
`CONVERSATION_PARTICIPANT_SCREENSHARE_WRAPUP_TAG`
table	Discontinued Table	`CONVERSATION_PARTICIPANT_SCREENSHARE_WRAPUP_TAG`
`CONVERSATION_PARTICIPANT_SENT_MESSAGE`
table	Discontinued Table	`CONVERSATION_PARTICIPANT_SENT_MESSAGE`
`CONVERSATION_PARTICIPANT_SENT_MESSAGE_MEDIA`
table	Discontinued Table	`CONVERSATION_PARTICIPANT_SENT_MESSAGE_MEDIA`
`CONVERSATION_PARTICIPANT_SENT_MESSAGE_STICKER`
table	Discontinued Table	`CONVERSATION_PARTICIPANT_SENT_MESSAGE_STICKER`
`CONVERSATION_PARTICIPANT_SOCIAL_EXPRESSION`
table	Discontinued Table	`CONVERSATION_PARTICIPANT_SOCIAL_EXPRESSION`
`CONVERSATION_PARTICIPANT_SOCIAL_EXPRESSION_SEGMENT`
table	Discontinued Table	`CONVERSATION_PARTICIPANT_SOCIAL_EXPRESSION_SEGMENT`
`CONVERSATION_PARTICIPANT_SOCIAL_EXPRESSION_WRAPUP_TAG`
table	Discontinued Table	`CONVERSATION_PARTICIPANT_SOCIAL_EXPRESSION_WRAPUP_TAG`
`CONVERSATION_PARTICIPANT_VIDEO`
table	Discontinued Table	`CONVERSATION_PARTICIPANT_VIDEO`
`CONVERSATION_PARTICIPANT_VIDEO_MS_ID`
table	Discontinued Table	`CONVERSATION_PARTICIPANT_VIDEO_MS_ID`
`CONVERSATION_PARTICIPANT_VIDEO_WRAPUP_TAG`
table	Discontinued Table	`CONVERSATION_PARTICIPANT_VIDEO_WRAPUP_TAG`
`CONVERSATION_PARTICIPANT_WRAPUP_TAG`
table	Discontinued Table	`CONVERSATION_PARTICIPANT_WRAPUP_TAG`
`CONVERSATION_RECENT_TRANSFER`
table	Discontinued Table	`CONVERSATION_RECENT_TRANSFER`
`HEAD_COUNT_FORECAST_ENTITIES`
table	New Table		`HEAD_COUNT_FORECAST_ENTITIES`
`HISTORICAL_ADHERENCE`
table	New Table		`HISTORICAL_ADHERENCE`
`HISTORICAL_ADHERENCE_ACTUAL`
table	New Table		`HISTORICAL_ADHERENCE_ACTUAL`
`HISTORICAL_ADHERENCE_DAY_METRICS`
table	New Table		`HISTORICAL_ADHERENCE_DAY_METRICS`
`HISTORICAL_ADHERENCE_EXCEPTION_INFO`
table	New Table		`HISTORICAL_ADHERENCE_EXCEPTION_INFO`
`HISTORICAL_SHRINKAGE`
table	New Table		`HISTORICAL_SHRINKAGE`
`HISTORICAL_SHRINKAGE_ACTIVITY_CATEGORY`
table	New Table		`HISTORICAL_SHRINKAGE_ACTIVITY_CATEGORY`
`HISTORICAL_SHRINKAGE_FOR_ACTIVITY_CODE`
table	New Table		`HISTORICAL_SHRINKAGE_FOR_ACTIVITY_CODE`
`INTRADAY_PLANNING`
table	New Table		`INTRADAY_PLANNING`
`INTRADAY_PLANNING_ROUTEPATH`
table	New Table		`INTRADAY_PLANNING_ROUTEPATH`
`MANAGEMENT_UNIT`
table	New Table		`MANAGEMENT_UNIT`
`SCHEDULE`
table	New Table		`SCHEDULE`
`SCHEDULE_MANAGEMENT_UNIT`
table	New Table		`SCHEDULE_MANAGEMENT_UNIT`
`SCHEDULE_MANAGEMENT_UNIT_AGENT`
table	New Table		`SCHEDULE_MANAGEMENT_UNIT_AGENT`
`SCHEDULE_MESSAGE_SEVERITY_COUNT`
table	New Table		`SCHEDULE_MESSAGE_SEVERITY_COUNT`
`SPEECH_AND_TEXT_ANALYTICS`
table	New Table		`SPEECH_AND_TEXT_ANALYTICS`
`SPEECH_AND_TEXT_ANALYTICS_PARTICIPANT`
table	New Table		`SPEECH_AND_TEXT_ANALYTICS_PARTICIPANT`
`SPEECH_AND_TEXT_ANALYTICS_TRANSCRIPT`
table	New Table		`SPEECH_AND_TEXT_ANALYTICS_TRANSCRIPT`
`WORKFORCE_MANAGEMENT_INTRADAY`
table	New Table		`WORKFORCE_MANAGEMENT_INTRADAY`
`WORKFORCE_MANAGEMENT_INTRADAY_GROUP`
table	New Table		`WORKFORCE_MANAGEMENT_INTRADAY_GROUP`
`WORKFORCE_MANAGEMENT_UNIT_AGENT`
table	New Table		`WORKFORCE_MANAGEMENT_UNIT_AGENT`

GitHub

We have added two new columns, epss_percentage and epss_percentile, to the SECURITY_ADVISORY table.

Also, we've added the following new columns to the PULL_REQUEST_REVIEW_COMMENTS table:

line
original_line
start_line
original_start_line

GitLab

Effective June 16, 2026 we use a new June 2026 schema. Review the latest ERD to better understand the schema changes.

We are updating the connector schema to enhance its usability.

5 total changes • 0 possible breaking changes

Table/column	Change type	New name
`GROUPS_EPIC_BOARD`
table	New Table	`GROUPS_EPIC_BOARD`
`GROUPS_EPIC_BOARD_LABEL`
table	New Table	`GROUPS_EPIC_BOARD_LABEL`
`GROUPS_EPIC_BOARD_LIST`
table	New Table	`GROUPS_EPIC_BOARD_LIST`
`GROUPS_ISSUE`
table	New Table	`GROUPS_ISSUE`
`GROUPS_ITERATION`
table	New Table	`GROUPS_ITERATION`

Gladly

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

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

2 total changes • 0 possible breaking changes

Table/column	Change type	New name
`VOICE_TRANSCRIPT`
table	New Table	`VOICE_TRANSCRIPT`
`VOICE_TRANSCRIPT_PARAGRAPH`
table	New Table	`VOICE_TRANSCRIPT_PARAGRAPH`

GoFundMe Pro

Effective June 2, 2026 we use a new June 2026 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
`CAMPAIGN_SOURCE_TRACKING_CODE`
table	New Table		`CAMPAIGN_SOURCE_TRACKING_CODE`
`SOURCE_TRACKING_CODE`
table	Discontinued Table	`SOURCE_TRACKING_CODE`

Google Ads

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

logo_images
marketing_images
portrait_marketing_images
square_marketing_images

Google Calendar

Effective June 11, 2026 we use a new June 2026 schema. Review the latest ERD to better understand the schema changes.

We are updating the connector schema to support a feature enhancement. Trigger a re-sync to backfill the historical data for the new columns.

18 total changes • 0 possible breaking changes

Table/column	Change type	New name
`CALENDAR_LIST`
column	New Column	`data_owner`
`EVENT`
column	New Column	`birthday_properties_contact`
column	New Column	`birthday_properties_custom_type_name`
column	New Column	`birthday_properties_type`
column	New Column	`color_id`
column	New Column	`focus_time_properties_auto_decline_mode`
column	New Column	`focus_time_properties_chat_status`
column	New Column	`focus_time_properties_decline_message`
column	New Column	`out_of_office_properties_auto_decline_mode`
column	New Column	`out_of_office_properties_decline_message`
column	New Column	`working_location_properties_custom_location_label`
column	New Column	`working_location_properties_home_office`
column	New Column	`working_location_properties_office_location_building_id`
column	New Column	`working_location_properties_office_location_desk_id`
column	New Column	`working_location_properties_office_location_floor_id`
column	New Column	`working_location_properties_office_location_floor_section_id`
column	New Column	`working_location_properties_office_location_label`
column	New Column	`working_location_properties_type`

Healthie

Effective June 9, 2026 we use a new June 2026 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.

31 total changes • 29 possible breaking changes

Table/column	Change type	Old name	New name	Notes
`APPOINTMENT_TYPE_SETTING_CALENDAR_COLOR_SCHEME_COLOR_CODE`
column	Discontinued Column	`calendar_color_scheme_id` 🔑		No longer a primary key.
`CONVERSATION`
table	New Table		`CONVERSATION`
`CONVERSATION_MEMBERSHIP`
column	Discontinued Column	`conversation_closed_by_id`
column	Discontinued Column	`conversation_closed_date`
column	Discontinued Column	`conversation_community_chat_prefix`
column	Discontinued Column	`conversation_created_at`
column	Discontinued Column	`conversation_dietitian_id`
column	Discontinued Column	`conversation_includes_multiple_clients`
column	Discontinued Column	`conversation_is_hidden_for_client`
column	Discontinued Column	`conversation_last_message_content`
column	Discontinued Column	`conversation_last_note_viewed_id`
column	Discontinued Column	`conversation_name`
column	Discontinued Column	`conversation_owner_id`
column	Discontinued Column	`conversation_patient_id`
column	Discontinued Column	`conversation_updated_at`
column	Discontinued Column	`conversation_user_group_id`
`CONVERSATION_NOTE`
column	Discontinued Column	`attached_audio_url`
column	Discontinued Column	`attached_image_url`
column	Discontinued Column	`content`
column	Discontinued Column	`created_at`
column	Discontinued Column	`deleted_by_user`
column	Discontinued Column	`document_id`
column	Discontinued Column	`image_name`
column	Discontinued Column	`is_autoresponse`
column	Discontinued Column	`recipient_id`
column	Discontinued Column	`scheduled_at`
column	Discontinued Column	`task_id`
column	Discontinued Column	`updated_at`
column	Discontinued Column	`user_id`
column	Discontinued Column	`viewed`
`NOTE`
table	New Table		`NOTE`

Intercom

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

Iterable

We've added two new tables, CAMPAIGN_METRICS_WEEKLY and CAMPAIGN_METRICS_MONTHLY.

Jotform

Effective June 18, 2026 we use a new June 2026 schema. Review the latest ERD to better understand the schema changes.

We are updating the connector schema to resolve data integrity issues.

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

2 total changes • 2 possible breaking changes

Table/column	Change type	Old name	New name	Notes
`TEAM_SUBMISSION`
column	Primary Key Change	`form_id`	`form_id` 🔑	Added to the primary key.
`TEAM_SUBMISSION_ANSWER`
column	Primary Key Change	`form_id`	`form_id` 🔑	Added to the primary key.

Katana

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

We are updating the connector schema to prevent or resolve data integrity issues.

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

9 total changes • 5 possible breaking changes

Table/column	Change type	Old name	New name	Notes
`BOM_ROW`
table	New Table		`BOM_ROW`
`MATERIAL_SUPPLIER_ITEM_CODE`
column	Primary Key Change	`material_id` 🔑	`material_id`	No longer a primary key.
`OUTSOURCE_PURCHASE_BATCH_TRANSACTION`
column	Primary Key Change	`batch_id` 🔑	`batch_id`	No longer a primary key.
column	New Column		`index` 🔑
`PURCHASE_ORDER_ROW_BATCH_TRANSACTION`
column	Primary Key Change	`batch_id` 🔑	`batch_id`	No longer a primary key.
column	New Column		`index` 🔑
`RECIPE`
table	Discontinued Table	`RECIPE`
`STOCK_ADJUSTMENT_ROW_BATCH_TRANSACTION`
column	Primary Key Change	`batch_id` 🔑	`batch_id`	No longer a primary key.
column	New Column		`index` 🔑

LaunchDarkly

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

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

3 total changes • 0 possible breaking changes

Table/column	Change type	New name
`FEATURE_FLAG_STATUS`
table	New Table	`FEATURE_FLAG_STATUS`
`FLAG_EVENT`
table	New Table	`FLAG_EVENT`
`FLAG_EVENT_EXPERIMENT_ITEM`
table	New Table	`FLAG_EVENT_EXPERIMENT_ITEM`

Lever

We have added a new column, sourced_by, to the OPPORTUNITY table.

We have added a new column, department, to the REQUISITION table.

LinkedIn Ad Analytics

We've added the following new columns to the CAMPAIGN_HISTORY table:

connected_television_only
optimization_preference_frequency_optimization_preference_frequency
optimization_preference_frequency_optimization_preference_optimization_type
optimization_preference_frequency_optimization_preference_time_span_duration
optimization_preference_frequency_optimization_preference_time_span_unit

LinkedIn Company Pages

We have added the TIME_BOUND_VIDEO_ANALYTICS table which provides video performance metrics for video posts.

Lucca

Effective June 17, 2026 we use a new June 2026 schema. Review the latest ERD to better understand the schema changes.

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

2 total changes • 0 possible breaking changes

Table/column	Change type	New name
`USER_LOCATION`
table	New Table	`USER_LOCATION`
`WORK_CONTRACT`
table	New Table	`WORK_CONTRACT`

Effective June 24, 2026 we use a new June 2026 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
`LEAVE_ACCOUNT`
column	Discontinued Column		`leave_profile_entitlements`

MaintainX

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

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

7 total changes • 0 possible breaking changes

Table/column	Change type	New name
`ASSET`
column	New Column	`downtime_type`
column	New Column	`started_at`
column	New Column	`status`
column	New Column	`status_created_at`
column	New Column	`status_description`
column	New Column	`status_id`
column	New Column	`status_updated_at`

Maxio Chargify

Effective June 2, 2026 we use a new June 2026 schema. Review the latest ERD to better understand the schema changes.

We are updating the connector schema to resolve data integrity issues.

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

3 total changes • 2 possible breaking changes

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

Microsoft Advertising

We've added the following new columns to the AD_PERFORMANCE_DAILY_REPORT and AD_PERFORMANCE_HOURLY_REPORT tables:

average_cpv
average_watch_time_per_video_view
completed_video_views
total_watch_time_in_ms
video_completion_rate
video_views_at_25_percent
video_views_at_50_percent
video_views_at_75_percent
video_views
view_through_rate

We have added the following new tables:

PRODUCT_DIMENSION_IMPRESSION_PERFORMANCE_DAILY_REPORT_UPCOMING
PRODUCT_DIMENSION_IMPRESSION_PERFORMANCE_HOURLY_REPORT_UPCOMING
PRODUCT_DIMENSION_PERFORMANCE_DAILY_REPORT_UPCOMING
PRODUCT_DIMENSION_PERFORMANCE_HOURLY_REPORT_UPCOMING

Tables with the suffix, _UPCOMING, are new versions of existing tables. From June 10, 2026 through July 14, 2026, we will sync data to both the legacy tables and their corresponding new versions with the _UPCOMING suffix.

New tables use _fivetran_id as a primary key instead of the composite primary key in the legacy tables. For more information about primary keys and columns for this connector, see our Microsoft Ads Prebuilt Reports documentation.

The new tables with the _UPCOMING suffix will not count toward your paid MAR until July 14, 2026.

Microsoft Entra ID

Effective June 15, 2026 we use a new June 2026 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
`DEVICE_INSTALL_STATUS_BY_APP`
table	New Table			`DEVICE_INSTALL_STATUS_BY_APP`

Microsoft Teams

Effective June 22, 2026 we use a new June 2026 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.

3 total changes • 3 possible breaking changes

Table/column	Change type	Old name	New name	Notes
`SESSION`
column	Primary Key Change	`start_date_time`	`start_date_time` 🔑	Added to primary key
`SESSION_MEDIA`
column	Primary Key Change		`session_start_date_time` 🔑	New primary key
`SESSION_MEDIA_STREAM`
column	Primary Key Change		`session_start_date_time` 🔑	New primary key

MNTN

Effective June 11, 2026 we use a new June 2026 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.

17 total changes • 12 possible breaking changes

Table/column	Change type	Old name	New name
`ANALYTICS_BY_COUNTRY`
column	Discontinued Column	`cost_per_acquisition`
column	Discontinued Column	`return_on_ad_spend`
column	Discontinued Column	`return_on_investment`
`ANALYTICS_BY_STATE`
column	Discontinued Column	`cost_per_acquisition`
column	Discontinued Column	`return_on_ad_spend`
column	Discontinued Column	`return_on_investment`
`SEGMENT`
column	Discontinued Column	`cost_per_acquisition`
column	Discontinued Column	`return_on_ad_spend`
column	Discontinued Column	`return_on_investment`
column	New Column		`existing_site_visitor`
column	New Column		`existing_user_reached`
column	New Column		`new_site_visitor`
column	New Column		`new_user_reached`
column	New Column		`site_visitor`
`SEGMENT_INFO`
column	Discontinued Column	`cost_per_acquisition`
column	Discontinued Column	`return_on_ad_spend`
column	Discontinued Column	`return_on_investment`

Navan

Effective June 17, 2026 we use a new June 2026 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.

53 total changes • 43 possible breaking changes

Table/column	Change type	Old name	New name	Notes
`TRANSACTION`
column	Discontinued Column	`adjustment_description`
column	Discontinued Column	`admin_note`
column	Rename Column	`amount_rejected`	`rejected_amount`
column	Discontinued Column	`amount_repaid`
column	Discontinued Column	`billable_entity`
column	Discontinued Column	`card_nickname`
column	Discontinued Column	`card_owner`
column	Discontinued Column	`cardholder_guest`
column	Discontinued Column	`est_doc_date`
column	Discontinued Column	`est_doc_link`
column	Discontinued Column	`est_doc_number`
column	Discontinued Column	`hotel_payment_type`
column	Discontinued Column	`inviter_cost_center`
column	Discontinued Column	`inviter_department`
column	Discontinued Column	`inviter_email`
column	Discontinued Column	`inviter_employee_id`
column	Discontinued Column	`inviter_name`
column	Discontinued Column	`inviter_region`
column	Discontinued Column	`inviter_subsidiary`
column	Discontinued Column	`item_id` 🔑		Data is available in the `line_item_id` column of the `TRANSACTION_LINE_ITEM` table.
column	Primary Key Change	`item_id` 🔑		No longer a primary key.
column	Discontinued Column	`item_title`		Data is available in the `name` column of the `TRANSACTION_LINE_ITEM` table.
column	Rename Column	`legal_entity_amount`	`billable_entity_amount`
column	Rename Column	`legal_entity_currency`	`billable_entity_currency`
column	Discontinued Column	`net_amount`		Data is available in the `net_amount` column of the `TRANSACTION_LINE_ITEM` table.
column	Discontinued Column	`net_amount_1`		Data is available in the `net_amount` column of the `TRANSACTION_TAX_LINE_DETAIL` table.
column	Discontinued Column	`net_amount_2`		Data is available in the `net_amount` column of the `TRANSACTION_TAX_LINE_DETAIL` table.
column	Discontinued Column	`net_amount_3`		Data is available in the `net_amount` column of the `TRANSACTION_TAX_LINE_DETAIL` table.
column	Discontinued Column	`original_txn_id`
column	Discontinued Column	`requested_amount`
column	Discontinued Column	`ta_invoice`
column	Discontinued Column	`tax_amount_1`		Data is available in the `tax_amount` column of the `TRANSACTION_TAX_LINE_DETAIL` table.
column	Discontinued Column	`tax_amount_2`		Data is available in the `tax_amount` column of the `TRANSACTION_TAX_LINE_DETAIL` table.
column	Discontinued Column	`tax_amount_3`		Data is available in the `tax_amount` column of the `TRANSACTION_TAX_LINE_DETAIL` table.
column	Discontinued Column	`tax_total`		Data is available in the `total_amount` column of the `TRANSACTION_TAX_LINE_DETAIL` table.
column	Discontinued Column	`tax_type_1`		Data is available in the `tax_type` column of the `TRANSACTION_TAX_LINE_DETAIL` table.
column	Discontinued Column	`tax_type_2`		Data is available in the `tax_type` column of the `TRANSACTION_TAX_LINE_DETAIL` table.
column	Discontinued Column	`tax_type_3`		Data is available in the `tax_type` column of the `TRANSACTION_TAX_LINE_DETAIL` table.
column	Rename Column	`transaction_department`	`department`
column	Rename Column	`transaction_region`	`region`
column	Rename Column	`transaction_subsidiary`	`subsidiary`
column	Rename Column	`travelers_employee_id`	`traveler_employee_id`
column	Discontinued Column	`vcf_transaction_reference_number`
column	New Column		`card_program_name`
column	New Column		`detail_type`
column	New Column		`erp_effective_date`
column	New Column		`erp_sync_status`
column	New Column		`itemized`
column	New Column		`reverse_charge`
column	New Column		`transaction_date`
column	New Column		`transaction_type`
`TRANSACTION_LINE_ITEM`
table	New Table		`TRANSACTION_LINE_ITEM`
`TRANSACTION_TAX_LINE_DETAIL`
table	New Table		`TRANSACTION_TAX_LINE_DETAIL`

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

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

2 total changes • 0 possible breaking changes

Table/column	Change type	New name
`BOOKING_SEGMENT`
column	New Column	`cabin`
column	New Column	`cabin_purchased`

Okta

We've added the following new tables:

GROUP_PUSH_MAPPING
REALM
REALM_ASSIGNMENT

We've added the following new columns to the USERS table:

realm_id
profile_function
profile_bob_department
profile_internal_lifecycle_status.

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

risk_behaviors_condition
risk_score_level_condition
identity_provider_condition
platform_include_condition
platform_exclude_condition
user_identifier_patterns_condition
app_include_condition
app_exclude_condition
signon_factor_prompt_mode
signon_factor_lifetime
enroll_self
password_change_access
password_reset_access
password_reset_primary_methods
password_reset_stepup_required
password_unlock_access
idp_providers
idp_selection_type
idp_should_fallback_to_okta
profile_enrollment_access
profile_enrollment_unknown_user_action
profile_enrollment_activation_email_verification
profile_enrollment_ui_schema_id
profile_enrollment_progressive_profiling_action
profile_enrollment_pre_registration_inline_hooks
profile_enrollment_target_group_ids
profile_enrollment_profile_attributes
app_signon_access
app_signon_verification_factor_mode
app_signon_verification_type
app_signon_verification_reauthenticate_in
app_signon_verification_constraints

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

Ometria

Effective June 17, 2026 we use a new June 2026 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
`PROFILE`
column	New Column			`date_predicted_next_purchase`

PandaDoc

Effective June 8, 2026 we use a new June 2026 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 • 1 possible breaking changes

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

Pipedrive

We now sync the employee_count column of the ORGANIZATION table as LONG. Previously, we synced the column as INT.

PostgreSQL

For PostgreSQL connections using Query-Based incremental sync without delete capture, the _fivetran_deleted column now contains false instead of null.

Productboard

Effective June 2, 2026 we use a new June 2026 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
`COMPANY_CUSTOM_FIELD`
table	New Table			`COMPANY_CUSTOM_FIELD`

Pylon Support Platform

Effective June 18, 2026 we use a new June 2026 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
`ISSUE_THREAD`
table	New Table			`ISSUE_THREAD`

Recharge

We have added a new column, currency, to the CHARGE table.

We have added a new column, presentment_currency, to the SUBSCRIPTION table.

Reddit Ads

We've added the following new columns to the BUSINESS_ACCOUNT table:

app_attribution_type
app_click_attribution_window
app_view_attribution_window
primary_contact_member_id
spend_cap_type

Salesforce

We've added a new table, APEX_CODE_COVERAGE_AGGREGATE.

We're gradually rolling out this change to all connections.

Salesforce Marketing Cloud

We've added a new table, CLOUD_PAGE. The table contains Cloud Pages, which are web pages and microsites created and hosted in Salesforce Marketing Cloud. Syncing this table will count towards free MAR until June 21, 2026.

Salesloft

We have added a new table, CONVERSATION.

Salsify

We have added two new tables, ATTRIBUTE and ATTRIBUTE_VALUE. We are gradually rolling out this change to all existing connections.

SAP Concur

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

employee_bank_account_id
expense_type_code
form_id
has_applied_cash_advance
has_image
is_billable
journey_business_distance
journey_end_location
journey_number_of_passengers
journey_odometer_end
journey_odometer_start
journey_personal_distance
journey_start_location
journey_unit_of_measure
location_id
trip_id
vendor_list_item_id
vendor_list_item_name

We have added a new column, id, to the ENTRY_ATTENDEE_ASSOCIATION table.

We have added two new tables, LIST_ITEM and LIST_ITEM_MEMBER_LIST.

SAP SuccessFactors

We have added the following new tables:

CALIBRATION_SESSION
CALIBRATION_SESSION_SUBJECT
CALIBRATION_SUBJECT_RANK
CALIBRATION_TEMPLATE
EMP_JOB_RELATIONSHIP
FORM_AUDIT_TRAIL
FORM_BEHAVIOR_RATING_COMMENT
FORM_COMPETENCY_BEHAVIOR
FORM_CONTENT
FORM_HEADER
FORM_INTRODUCTION_SECTION
FORM_OBJ_COMP_SUMMARY_SECTION
FORM_OBJECTIVE
FORM_OBJECTIVE_COMMENT
FORM_OBJECTIVE_DETAILS
FORM_OBJECTIVE_OTHER_DETAILS_ITEM
FORM_OBJECTIVE_OTHER_DETAILS_ITEM_COL
FORM_OBJECTIVE_OTHER_DETAILS_ITEM_VALUE_CELL
FORM_OBJECTIVE_SECTION
FORM_PERF_POT_SUMMARY_SECTION
FORM_RATING_SCALE
FORM_RATING_SCALE_VALUE
FORM_REVIEW_FEEDBACK
FORM_SIGNATURE
FORM_SUMMARY_SECTION
FORM_USER_INFORMATION_SECTION
PER_ADDRESS_DEFLT
PER_EMERGENCY_CONTACT
PER_PERSON_RELATIONSHIP
PER_PHONE

Shopify

We've added the following new tables to sync Shopify Markets data:

MARKET
MARKET_CATALOG
MARKET_CONDITION
MARKET_CONDITION_COMPANY_LOCATION
MARKET_CONDITION_LOCATION
MARKET_CONDITION_REGION
MARKET_REGION

We have added the following new tables:

GIFT_CARD_TRANSACTION
GIFT_CARD_TRANSACTION_METAFIELD
ORDER_LINE_DUTY
ORDER_LINE_DUTY_TAX_LINE
PRICE_LIST
PRICE_LIST_PRICE
RETURN_EXCHANGE_LINE_ITEM
RETURN_EXCHANGE_LINE_ITEM_ORDER_LINE

The price_list_id column in the CATALOG table now has a foreign key relationship to the PRICE_LIST table.

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

restocking_fee_amount_set_pres_amount
restocking_fee_amount_set_pres_currency_code
restocking_fee_amount_set_shop_amount
restocking_fee_amount_set_shop_currency_code
restocking_fee_id
restocking_fee_percentage

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

currency_exchange_adjustment
currency_exchange_currency
currency_exchange_final_amount
currency_exchange_id
currency_exchange_original_amount

Showpad

Effective June 22, 2026 we use a new June 2026 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
`COMMENT`
table	New Table	`COMMENT`
`CRM_SHARE_RECORD`
table	New Table	`CRM_SHARE_RECORD`
`CRM_SHARED_SPACE_RECORD`
table	New Table	`CRM_SHARED_SPACE_RECORD`
`DIVISION_PERMISSION`
table	New Table	`DIVISION_PERMISSION`
`MAP`
table	New Table	`MAP`
`MAP_PARTICIPANT`
table	New Table	`MAP_PARTICIPANT`
`RECOMMENDATION_ASSET_NEW`
table	New Table	`RECOMMENDATION_ASSET_NEW`
`RECOMMENDATION_RULE`
table	New Table	`RECOMMENDATION_RULE`
`RECOMMENDATION_RULE_CONDITION`
table	New Table	`RECOMMENDATION_RULE_CONDITION`
`RECOMMENDATION_RULE_TAGS_ALL`
table	New Table	`RECOMMENDATION_RULE_TAGS_ALL`
`RECOMMENDATION_RULE_TAGS_ANY`
table	New Table	`RECOMMENDATION_RULE_TAGS_ANY`
`RECOMMENDATION_RULE_TAGS_NONE`
table	New Table	`RECOMMENDATION_RULE_TAGS_NONE`
`SHARED_SPACE_QUICK_ACTION`
table	New Table	`SHARED_SPACE_QUICK_ACTION`
`SHARED_SPACE_TEMPLATE`
table	New Table	`SHARED_SPACE_TEMPLATE`
`TICKET`
table	New Table	`TICKET`
`USER_PERMISSION`
table	New Table	`USER_PERMISSION`

Skilljar

Effective June 11, 2026 we use a new June 2026 schema. Review the latest ERD to better understand the schema changes.

We are updating the connector schema to enhance its usability.

2 total changes • 0 possible breaking changes

Table/column	Change type	New name
`COURSE`
column	New Column	`created_at`
column	New Column	`modified_at`

Effective June 25, 2026 we use a new June 2026 schema. Review the latest ERD to better understand the schema changes.

We are updating the connector schema to enhance its usability.

2 total changes • 0 possible breaking changes

Table/column	Change type	New name
`COURSE_SERIES_PUBLISHED_COURSE`
table	New Table	`COURSE_SERIES_PUBLISHED_COURSE`
`PATH_ITEM`
table	New Table	`PATH_ITEM`

Snapchat Ads

We have added the following new tables:

AD_SQUAD_DELIVERY_STATUS
AD_SQUAD_PLACEMENT_V2_PLATFORM
AD_SQUAD_PLACEMENT_V2_SNAPCHAT_POSITION

We have added two new columns, event_sources and placement_v2_config, to the AD_SQUAD_HISTORY table.

sticky.io

Effective June 11, 2026 we use a new June 2026 schema. Review the latest ERD to better understand the schema changes.

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

3 total changes • 0 possible breaking changes

Table/column	Change type	New name	Notes
`PROSPECT_VIEW`
table	New Table	`PROSPECT_VIEW`	To backfill the historical records, trigger a re-sync.
`PROSPECT_VIEW_CUSTOM_FIELD`
table	New Table	`PROSPECT_VIEW_CUSTOM_FIELD`	To backfill the historical records, trigger a re-sync.
`PROSPECT_VIEW_CUSTOM_FIELD_VALUE`
table	New Table	`PROSPECT_VIEW_CUSTOM_FIELD_VALUE`	To backfill the historical records, trigger a re-sync.

Stripe

We have added a new table, BILLING_METER. We are gradually rolling out this change to all existing connections.

We now sync discounts associated with subscription items to the DISCOUNT table.

We have added the following new tables to support Payment Links:

PAYMENT_LINK
PAYMENT_LINK_CUSTOM_FIELD
PAYMENT_LINK_CUSTOM_FIELD_DROPDOWN_OPTION
PAYMENT_LINK_INVOICE_CREATION_INVOICE_DATA_ACCOUNT_TAX
PAYMENT_LINK_INVOICE_CREATION_INVOICE_DATA_CUSTOM_FIELD
PAYMENT_LINK_LINE_ITEM
PAYMENT_LINK_PAYMENT_METHOD_TYPE
PAYMENT_LINK_SHIPPING_OPTION

Talkdesk

We've added a new table, ADVANCED_DIALER_CALL.

We have added a new column, team_name, to the USER_STATUS table. We are gradually rolling out this change to all existing connections.

Toggl Track

Effective June 8, 2026 we use a new Jun 2026 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
`TIME_ENTRY_TAG`
column	Primary Key Change	`time_entry_id` 🔑	`time_entry_id`	No longer a primary key.
column	New Column		`user_id`

Validio

Effective June 25, 2026 we use a new June 2026 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
`SOURCE`
column	Discontinued Column		`config_look_back_day`		Validio deprecated the column.

Visma

Effective June 10, 2026 we use a new June 2026 schema. Review the latest ERD to better understand the schema changes.

We are updating the connector schema to enhance its usability.

2 total changes • 0 possible breaking changes

Table/column	Change type	New name
`GENERAL_LEDGER_BALANCE`
column	New Column	`account_type`
`SUPPLIER_INVOICE_LINE`
column	New Column	`account_type`

Effective June 30, 2026 we use a new June 2026 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	New name	Notes
`JOURNAL_TRANSACTION`
column	Primary Key Change	`financial_period_id` 🔑	`financial_period_id`	No longer a primary key.
`JOURNAL_TRANSACTION_ATTACHMENT`
column	Primary Key Change	`financial_period_id` 🔑	`financial_period_id`	No longer a primary key.
`JOURNAL_TRANSACTION_LINE`
column	Primary Key Change	`financial_period_id` 🔑	`financial_period_id`	No longer a primary key.
`JOURNAL_TRANSACTION_LINE_ATTACHMENT`
column	Primary Key Change	`financial_period_id` 🔑	`financial_period_id`	No longer a primary key.
`JOURNAL_TRANSACTION_LINE_SUB_ACCOUNT_SEGMENT`
column	Primary Key Change	`financial_period_id` 🔑	`financial_period_id`	No longer a primary key.
`SUPPLIER`
column	Primary Key Change	`number` 🔑	`number`	No longer a primary key.
`SUPPLIER_INVOICE`
column	Primary Key Change	`_fivetran_id` 🔑	`_fivetran_id` 🔑	Primary key calculation change.

When I Work

Effective June 9, 2026 we use a new June 2026 schema. Review the latest ERD to better understand the schema changes.

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

2 total changes • 0 possible breaking changes

Table/column	Change type	New name
`SHIFT_BREAK_AUDIT`
column	New Column	`created_at`
column	New Column	`updated_at`

Workable

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

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

4 total changes • 0 possible breaking changes

Table/column	Change type	New name
`EMPLOYEE`
table	New Table	`EMPLOYEE`
`EMPLOYEE_DOCUMENT`
table	New Table	`EMPLOYEE_DOCUMENT`
`EMPLOYEE_FIELD`
table	New Table	`EMPLOYEE_FIELD`
`EMPLOYEE_FIELD_CHOICE`
table	New Table	`EMPLOYEE_FIELD_CHOICE`

Workday Financial Management

We have made the following changes to the ORGANIZATION table:

Added a new column, code, to store organization codes. Previously, we synced these codes into the organization_code column.
Stopped syncing organization codes into the organization_code column. The existing organization codes stored in this column are now available in the code column.

We have added the following new tables, BUSINESS_UNIT, BUSINESS_UNIT_HIERARCHY, and BUSINESS_UNIT_HIERARCHY_CONTAINS_BUSINESS_UNIT.

We have added the following new tables:

BANK_STATEMENT
BANK_STATEMENT_SUMMARY
BANK_STATEMENT_TRANSACTION
FUNDS_AVAILABILITY_DATA

We have added the following new fund management tables:

FUND
FUND_HIERARCHY
FUND_HIERARCHY_FUNDS_REFERENCE
FUND_TYPE

Xandr

Effective June 9, 2026 we use a new June 2026 schema. Review the latest ERD to better understand the schema changes.

We are updating the connector schema to fix a bug.

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	Notes
`BUDGET_INTERVAL_CREATIVE`
column	Discontinued Column	`line_item_insertion_order_id` 🔑	No longer a primary key.
`LINE_ITEM_INSERTION_ORDER_BUDGET_INTERVAL`
column	Discontinued Column	`line_item_insertion_order_id` 🔑	No longer a primary key.

Younium

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

We are updating the connector schema to enhance its usability.

2 total changes • 0 possible breaking changes

Table/column	Change type	New name
`SUBSCRIPTION_PRODUCT_CHARGE`
column	New Column	`deferred_revenue_account`
column	New Column	`recognized_revenue_account`

Zip

Effective June 9, 2026 we use a new June 2025 schema. Review the latest ERD to better understand the schema changes.

We are updating the connector schema to enhance its usability.

4 total changes • 0 possible breaking changes

Table/column	Change type	New name
`APPROVAL`
column	New Column	`active_duration_seconds`
column	New Column	`active_elapsed_seconds`
column	New Column	`total_duration_seconds`
column	New Column	`total_elapsed_seconds`

Zoho Recruit

Effective June 17, 2026 we use a new June 2026 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.

35 total changes • 12 possible breaking changes

Table/column	Change type	Old name	New name
`ACCOUNT`
table	Discontinued Table	`ACCOUNT`
`ACCOUNT_DRAFT`
table	New Table		`ACCOUNT_DRAFT`
`ACCOUNT_SAVE`
table	New Table		`ACCOUNT_SAVE`
`ACCOUNT_TAG`
table	Discontinued Table	`ACCOUNT_TAG`
`ACCOUNT_TAG_DRAFT`
table	New Table		`ACCOUNT_TAG_DRAFT`
`ACCOUNT_TAG_SAVE`
table	New Table		`ACCOUNT_TAG_SAVE`
`CANDIDATE`
table	Discontinued Table	`CANDIDATE`
`CANDIDATE_ASSOCIATE_TAG_DRAFT`
table	New Table		`CANDIDATE_ASSOCIATE_TAG_DRAFT`
`CANDIDATE_ASSOCIATE_TAG_SAVE`
table	New Table		`CANDIDATE_ASSOCIATE_TAG_SAVE`
`CANDIDATE_DRAFT`
table	New Table		`CANDIDATE_DRAFT`
`CANDIDATE_SAVE`
table	New Table		`CANDIDATE_SAVE`
`CANDIDATE_TAG`
table	Discontinued Table	`CANDIDATE_TAG`
`INTERVIEW`
table	Discontinued Table	`INTERVIEW`
`INTERVIEW_DRAFT`
table	New Table		`INTERVIEW_DRAFT`
`INTERVIEW_SAVE`
table	New Table		`INTERVIEW_SAVE`
`INTERVIEW_TAG`
table	Discontinued Table	`INTERVIEW_TAG`
`INTERVIEW_TAG_DRAFT`
table	New Table		`INTERVIEW_TAG_DRAFT`
`INTERVIEW_TAG_SAVE`
table	New Table		`INTERVIEW_TAG_SAVE`
`INTERVIEWER`
table	Discontinued Table	`INTERVIEWER`
`INTERVIEWER_DRAFT`
table	New Table		`INTERVIEWER_DRAFT`
`INTERVIEWER_SAVE`
table	New Table		`INTERVIEWER_SAVE`
`JOB_OPENING`
table	Discontinued Table	`JOB_OPENING`
`JOB_OPENING_ASSIGNED_RECRUITER`
table	Discontinued Table	`JOB_OPENING_ASSIGNED_RECRUITER`
`JOB_OPENING_ASSIGNED_RECRUITER_DRAFT`
table	New Table		`JOB_OPENING_ASSIGNED_RECRUITER_DRAFT`
`JOB_OPENING_ASSIGNED_RECRUITER_SAVE`
table	New Table		`JOB_OPENING_ASSIGNED_RECRUITER_SAVE`
`JOB_OPENING_DRAFT`
table	New Table		`JOB_OPENING_DRAFT`
`JOB_OPENING_SAVE`
table	New Table		`JOB_OPENING_SAVE`
`JOB_OPENING_TAG`
table	Discontinued Table	`JOB_OPENING_TAG`
`JOB_OPENING_TAG_DRAFT`
table	New Table		`JOB_OPENING_TAG_DRAFT`
`JOB_OPENING_TAG_SAVE`
table	New Table		`JOB_OPENING_TAG_SAVE`
`VENDOR`
table	Discontinued Table	`VENDOR`
`VENDOR_DRAFT`
table	New Table		`VENDOR_DRAFT`
`VENDOR_SAVE`
table	New Table		`VENDOR_SAVE`
`VENDOR_TAG`
table	Discontinued Table	`VENDOR_TAG`
`VENDOR_TAG_SAVE`
table	New Table		`VENDOR_TAG_SAVE`

Zoom

Effective June 30, 2026 we use a new June 2026 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.

14 total changes • 1 possible breaking changes

Table/column	Change type	Old name	New name
`PHONE_CALL_PATH`
column	Discontinued Column	`waiting_time`
column	New Column		`callee_did_number`
column	New Column		`callee_email`
column	New Column		`callee_ext_id`
column	New Column		`callee_ext_number`
column	New Column		`callee_ext_type`
column	New Column		`callee_name`
column	New Column		`caller_did_number`
column	New Column		`caller_email`
column	New Column		`caller_ext_number`
column	New Column		`caller_ext_type`
column	New Column		`caller_name`
column	New Column		`cost_center`
column	New Column		`wait_time`

Zuora

We have added the following tables for the connections configured with the Sync Zuora Billing and Sync both Billing and Revenue sync modes:

REVENUECONTRACTBILLSFACTS
REVENUECONTRACTVCFACTS
REVENUECONTRACTMJENTRIESFACTS
REVENUECONTRACTLINESFACTS
REVENUECONTRACTCOSTFACTS
REVENUECONTRACTAPPROVALS
REVENUECONTRACTCOSTDIMENSIONS
REVENUECONTRACTHOLDS
REVENUECONTRACTMJENTRIESDIMENSIONS
REVENUECONTRACTVCDIMENSIONS
REVENUECONTRACTNETTINGSTATUS
REVENUECALENDAR
REVENUECONTRACT
REVENUECONTRACTACCOUNTINGENTRIES
REVENUECONTRACTACCOUNTINGSEGMENTS
REVENUECONTRACTACCOUNTINGTYPE
REVENUECONTRACTACTIONS
REVENUECONTRACTBILLSDIMENSIONS
REVENUEPERIODS
REVENUECONTRACTLINESDIMENSIONS

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

We have added a new column, discountamount, to the INVOICE_ITEM table.

Improvements

360Learning

Due to 360Learning’s deprecation of API v1, we have removed API key authentication and updated this connector to support only OAuth 2.0. For more information on how to migrate from API v1 to API v2, see 360Learning's migration guides. If you have an existing connection that uses an API key, you must reconfigure it to use OAuth 2.0. For more information, see our setup guide.

Adobe Analytics Data Feed

The Adobe Analytics Data Feed connector now supports the Hybrid Deployment model. For more information, see our setup instructions.

Assembled

We have updated the sync strategy for the TIME_OFF_REQUEST and TIME_OFF_UPDATE tables. In addition to incremental syncs, we now re-import these tables weekly to capture updates and deletes. We are gradually rolling out this change to all existing connections.

AWS MSK

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

Azure DevOps

We have updated the sync strategy for the WORK_ITEM_REVISION table. We now incrementally sync work item revisions using a time-based cursor, so only new or updated revisions are fetched during each sync.

BigCommerce

We've updated the sync strategy for the ORDERS table to use a trailing cursor with a 12-hour offset. This ensures that recently modified orders are not missed due to upstream processing delays.

Billing Platform

We have updated our sync strategy and now incrementally sync the following tables:

ACCOUNT
ACCOUNT_PACKAGE
ACCOUNT_PRODUCT
ACTIVITY
ACTIVITY_COLLECTOR
BILLING_IDENTIFIER
BILLING_PROFILE
COLLECTOR_FIELD
CONTRACT
CONTRACT_CURRENCY
CONTRACT_RATE
DUNNING_INTERVAL
INVOICE
INVOICE_TEMPLATE
PAYMENT
REVREC_CONTRACT
TIME_ZONE
USERS

Previously, we re-imported these tables daily.

Bizzabo

We've improved the sync strategy for the REGISTRATION table to support delete detection. Registrations with a validity value of invalid are now captured as deleted records in your destination.

Ceridian Dayforce

We now sync future data for up to 6 months from the current date for the EMPLOYEE_MANAGER and WORK_ASSIGNMENT tables.

We have changed the sync strategy for the EMPLOYEE and EMPLOYEE_TIME_AWAY_FROM_WORK tables. We now perform a rollback sync for these tables during every sync. The rollback window is 30 days, allowing us to capture updates made within that period. Previously, we only incrementally synced them.

Cin7

We now incrementally sync the following tables and their child tables:

ADJUSTMENT
BOM_MASTER
BRANCH
CONTACT
CREDIT_NOTE
PAYMENT
PRODUCT
PRODUCTION_JOB
PURCHASE_ORDER
QUOTE
SALES_ORDER
STOCK

CockroachDB

We have made the following improvements to the CockroachDB connector:

We now support the GEOGRAPHY and GEOMETRY data types. We sync these values as GeoJSON.
We now support CockroachDB versions 22.1.0 - 26.2.0.
We now support syncing tables that use multiple column families.

Collibra

We now sync additional metadata fields for the ASSET and DOMAIN tables. Previously, we excluded these fields from the sync. These metadata fields will count towards your MAR.

Customer.io

We have reduced the rollback sync window for the MESSAGE table from 6 months to 3 months to improve sync reliability and performance.

Db2 for LUW

Our Db2 for LUW connector is now in beta. For more information, see our Db2 for LUW connector documentation.

Email

We have added a new field, Allowed Senders, to the connection setup form. You can now use this field to restrict file ingestion to approved email addresses or domains. If specified, the connector processes only emails from matching senders. For more information, see our documentation

External Logs

We've improved external log service management with setup status visibility and on-demand setup testing.

Setup status in the dashboard

The log connectors dashboard now displays a status badge for each configured log service:

Connected — the log service is reachable and working correctly.
Broken — the log service configuration has errors that prevent log delivery. Log events are not forwarded while the log service is in this state.
Incomplete — the log service is configured but setup has not been completed. Log events are not forwarded while the log service is in this state.

Log services that were configured before this change have no status yet and are treated as Connected by default. No setup test run is required for existing log services.

Setup testing via the API

You can now trigger setup tests when creating or updating a log service by passing "run_setup_tests": true in the request body. The test results are returned immediately in the setup_tests field of the response.

A dedicated endpoint is also available to run setup tests on demand without modifying the log service configuration:

Group-level: POST /v1/external-logging/{logId}/test
Account-level: POST /v1/external-logging/account/test

Setup state in the API response

Log service endpoints return a status object when one exists. The status.setup_state field reflects the current state — connected, broken, or incomplete — and status.tasks lists any configuration issues that need attention. Log services created before this feature was introduced will not include a status field until their status is first set.

Gong

We have fixed a bug that prevented syncing the custom base URL in our Gong connector. To improve connector reliability, we have added a new field, API base URL, to the connection setup form. We will discontinue the Base URL field on July 8, 2026. For more information, see our setup instructions.

We have updated the sync strategy for the CALL table. We now replay the last 2 days of data on a daily basis to capture late-arriving updates such as transcripts and scores.

Greenhouse

We now use a 6-hour lookback window during incremental syncs for the CANDIDATE table to capture delayed updates from Greenhouse. We are gradually rolling out this change to all existing connections.

Healthie

We have added an optional field, Shard authorization ID, in the setup form to allow you to connect your data if it is stored in a shard.

High-Volume Agent SAP ECC on Oracle

Our HVA SAP ECC on Oracle connector is now generally available.

Read our High-Volume Agent SAP ECC on Oracle documentation.

High-Volume Agent SAP ECC on Oracle with NetWeaver

Our HVA SAP ECC on Oracle with NetWeaver connector is now generally available.

Read our High-Volume Agent SAP ECC on Oracle with NetWeaver documentation.

High-Volume Agent SAP ECC on SQL Server

Our HVA SAP ECC on SQL Server connector is now generally available.

Read our High-Volume Agent SAP ECC on SQL Server documentation.

HubSpot

We have updated our sync strategy and now incrementally sync the MARKETING_CAMPAIGN_CONTACT table and its child tables. Previously, we re-imported this table. As part of this change, we no longer capture deletes for this table.

HVA SAP ECC on Oracle

We've added support for the Proxy Agent connection method to the HVA SAP ECC on Oracle and HVA SAP ECC on Oracle with NetWeaver connectors. You can now use Proxy Agent to connect to your SAP ECC on Oracle instance without opening inbound firewall ports.

For more information, see our HVA SAP ECC on Oracle documentation, HVA SAP ECC on Oracle setup guide, HVA SAP ECC on Oracle with NetWeaver documentation, and HVA SAP ECC on Oracle with NetWeaver setup guide.

Iterable

Fivetran adds support for token-based webhook authentication, Basic and OAuth 2.0, for new Iterable connections. When you set up a new connection, you can choose a Webhook Authentication method for incoming webhook events. We generate a secret token that you configure in your Iterable webhook settings.

The selected authentication method is permanent and cannot be changed after the connection is created. All existing connections default to No Auth.

Khoros Communities

We have upgraded the Khoros Communities connector to use the Bulk Data API v3. As part of this upgrade, Khoros Communities connections now use OAuth 2.0 Authorization Code authentication instead of HTTP Basic authentication. To continue syncing data, re-authenticate your existing Khoros Communities connections using the new authentication method. For more information, see our setup instructions.

Kisi

We have improved sync reliability for the ROLE_ASSIGNMENT table. Previously, syncs failed when a Kisi account contained more than 20,000 role assignments because the connection attempted to paginate beyond the Kisi API limit. Kisi connections now sync up to 20,000 role assignment records and skip any additional records beyond the API limit. We complete the sync and display a warning when the connection skip records.

Klarna

Effective July 4, 2026, you can specify the delimiter used in your Klarna settlement reports to improve sync reliability for reports that use a delimiter other than the default value. To support this enhancement, we have made the following changes:

Added a new field, CSV delimiter, to the connection setup form
Added a new API parameter, csv_delimiter, to the Fivetran REST API

We will automatically migrate the current delimiter values for all existing connections.

Lever

We have updated the sync strategy for the POSTING_TAG_ALL and POSTING_TAG_WITH_PARAM tables and their child tables. We now incrementally sync them. Previously, we re-imported these tables during every sync. We are gradually rolling out this change to all existing connections.

Lob

We have changed the sync strategy for the the LETTER table. We now re-import this table daily to capture updates and deletes. Previously, we re-imported it weekly.

Microsoft Lists

We have added support for history mode in our Microsoft Lists connector. You can now enable history mode for individual user-created lists from the Schema tab.

For more information, see our History Mode documentation.

OpenAI

We have changed the connector type of our OpenAI connector from Lite to Standard.

The OpenAI connector can now sync Codex Enterprise Analytics API data from a specific ChatGPT workspace. To support this enhancement, we have made the following changes:

Added two new fields, Codex Enterprise Analytics API key and Workspace ID, to the connection setup form
Added two new parameters, api_key_3 and workspace_id, to the Fivetran REST API

Outreach

The Outreach connector now supports priority-first sync. Priority-first syncs fetch your most recent data first so that it's quickly ready for you to use. Outreach's priority-first syncs fetch the most recent 30 days' worth of data from all tables except the following tables:

COMPLIANCE_REQUEST
CUSTOM_FIELD
DUTY
EMAIL_ADDRESS
PHONE_NUMBER
PROFILE
RECIPIENT
ROLE
SEQUENCE_TEMPLATE
TEAM

To learn more, see our priority-first sync documentation.

Pendo

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

Pinpoint

We have fixed an issue that prevented syncing the stage_id column to the INTERVIEW table.

PostgreSQL

We now support syncing the xid8 data type as LONG.

Qualtrics

We have discontinued syncing data into the CORE_CONTACT, CORE_MAILING_LIST, and CORE_SAMPLE tables since Qualtrics is deprecating its legacy Research Core Contacts endpoints. We have replaced these tables with the DIRECTORY_CONTACT, DIRECTORY_MAILING_LIST, and DIRECTORY_SAMPLE, respectively. We now sync data into these corresponding XM Directory tables.

Salesforce

As of June 24, 2026, Fivetran's Salesforce connected app complies with Salesforce's mandatory security updates for connected apps. The app supports Proof Key for Code Exchange (PKCE), Refresh Token Rotation (RTR), Refresh Token Expiry (RTE), and enforces refresh token IP allowlisting.

To ensure uninterrupted syncs, perform the following steps:

Allowlist Fivetran's IP addresses in your Salesforce instance.
Disable session IP locking in your Salesforce instance.

These steps are required for all Salesforce connections using Fivetran's connected app. You can check the Salesforce app type on the connection settings page.

Samsara

The Samsara connector now supports priority-first sync for the following tables:

AUX_INPUT_1
AUX_INPUT_2
AUX_INPUT_3
BATTERY_MILLI_VOLT
DEFECT
DRIVER_HOS_VIOLATION
DRIVER_VEHICLE_ASSIGNMENT
DVIR
ENGINE_STATE
FAULT_CODE
FORM_SUBMISSION_STREAM
FUEL_ENERGY_BY_DRIVER_REPORT
FUEL_ENERGY_BY_VEHICLE_REPORT
FUEL_PERCENT
GPS
GPS_DISTANCE_METER
GPS_ODOMETER
HOS_LOG
OBD_ODOMETER
OBD_ENGINE_SECOND
SAFETY_EVENT
STREAM_DVIR
SYNTHETIC_ENGINE_SECOND
VEHICLE_IDLING_REPORT

To learn more, see our priority-first sync documentation.

SAP ERP on HANA

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

We have added new RFC-enabled function /FIVETRAN/POKE that will be used to reset timer in source system and to let data retrieval job run longer when needed.

We have fixed a bug with regex that could cause unhandled runtime expression in source during data validation runs.

SAP SuccessFactors

We've improved sync reliability for the FO_BUSINESS_UNIT table by adding a 1-day replay window to the incremental sync strategy. This ensures that records with delayed timestamps are captured and not missed during incremental syncs.

SharePoint

We have fixed the behavior of the File Pattern field in our SharePoint connector. You no longer need to include the base folder in your regex. Previously, the regex you entered in the File Pattern field applied to the complete file path, including the base folder. New connections created on or after June 29, 2026, must now enter the file pattern relative to the base folder path and not the complete file path.

For connections created between October 17, 2025, and June 29, 2026, we will automatically update the file pattern to match this behavior. For more information, see our setup instructions.

Skilljar

The Skilljar connector no longer supports the Hybrid Deployment model.

Snyk

We have fixed a bug in the JIRA_ISSUE table that prevented syncing Jira issues linked to your Snyk project.

StarRez

We have changed our sync strategy for the ROOMSPACE_CLOSED table. We now incrementally sync the table and also re-import it once a week to capture deletes.

Tableau

We have implemented a daily lookback window to ensure integrity for the PROJECT and DATA_SOURCE tables.

WooCommerce

We have fixed a bug where we didn't sync the following tables:

SUBSCRIPTION
SUBSCRIPTION_LINE_ITEM
SUBSCRIPTION_SHIPPING_LINE
SUBSCRIPTION_TAX_LINE

Workday Financial Management

We now support syncing Organization Reference IDs from Workday. We sync these IDs into the code column of the ORGANIZATION table.

REST API Improvements

Connect Card all_fields parameter

The Connect Card configuration now supports the all_fields parameter. When set to true, Connect Card displays all available setup fields for a connection, including fields that are hidden by default for certain connectors.

Proxy Agent Management API changes

The group_region field in the Create a Proxy Agent endpoint is now optional. Previously, omitting group_region returned a 400 Bad Request error. You can now create a proxy agent without specifying a region. A regionless proxy agent is not tied to any specific region and can serve connections in any region.

Read endpoints require Account Read permission

The following endpoints now require the Account Read permission instead of Account Destination Create:

Strict integer validation for API key endpoints

Fivetran REST API endpoints now correctly reject floating-point values for integer fields.

Previously, sending a floating-point number for an integer field would silently truncate it to the nearest integer and succeed. The request now returns a 400 Bad Request error, consistent with the integer type declared for those fields.

June 2026

Connector SDK

fivetran-connector-sdk PyPI package

Lite Connectors

Managed Data Lake Service

Quickstart Package Updates

Quickstart data model package updates

v1.8.1

Under the Hood

v2.6.1

Bug Fixes

v1.6.1

Bug Fix

v1.6.3

Bug Fix

v1.6.2

Bug Fix

v1.0.1

Bug Fix

v0.9.2

Bug Fix

v1.4.0

Under the Hood

v1.10.0

Under the Hood

v1.4.0

Under the Hood

v1.4.0

Under the Hood

v1.4.0

Under the Hood

v1.4.0

Under the Hood

v1.8.0

Under the Hood

v1.4.0

Under the Hood

v1.7.0

Under the Hood

v1.5.0

Under the Hood

v1.7.0

Under the Hood

v1.5.0

Under the Hood

v1.4.0

Under the Hood

v1.3.0

Under the Hood

v0.17.0

Under the Hood

v1.4.0

Under the Hood

v0.2.0

Under the Hood

v1.4.0

Under the Hood

v0.4.0

Under the Hood

v0.5.0

Under the Hood

v1.8.2

Schema/Data Change

Bug Fix

v1.10.1

Bug Fix

v1.4.0

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

Under the Hood

v1.4.0

Under the Hood

v1.8.0

Schema/Data Change

v1.5.0

Breaking Changes

Under the Hood

v1.3.0

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

Feature Updates

Upstream Dependency Changes

`fivetran-connector-sdk` PyPI package