May 2025

Connector SDK

`fivetran-connector-sdk` PyPI package

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

Support for arm64 architecture on Linux and MacOS.
Minor improvements and bug fixes.
Updated tester.

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

Improved arguments for the --python-version CLI command that specifies the Python version to be used at runtime. Now you need to pass the Python version as 3.12, 3.11, 3.10 or 3.9 instead of 3.12.x, 3.11.x, 3.10.x or 3.9.x.
Improved logging.
Minor improvements and bug fixes.

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

As part of the existing --force (-f) flag, we've added the option to bypass the required dependencies check. This enhancement allows you to skip the validation process and use the requirements.txt file you provide.
We no longer block you if you reply No to any of the existing prompts. The Connector SDK execution will continue without interruption.
Minor improvements and bug fixes.
Updated tester.

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

Minor improvements in requirements.txt validations.
Updated tester.

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

Support for colored output in the command line for errors and warnings.
A fix to skip validation of requirements.txt due to connection errors with PyPI.
Minor improvements and bug fixes.

Fivetran Azure Switzerland Servers

We have added new servers in the Azure Switzerland North (Zurich) region.

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

For more information, see our data residency documentation.

Lite Connectors

Lite connectors are now available for the following sources:

Transformations for dbt Core

New transformation run status

We added a new transformation run status Partially Succeeded. This status means that the job has failed but at least one model completed successfully

* dbt Core is a trademark of dbt Labs, Inc. All rights therein are reserved to dbt Labs, Inc. Fivetran Transformations is not a product or service of or endorsed by dbt Labs, Inc.

Support of ClickHouse Cloud for dbt Core version 1.9.4

We now support ClickHouse Cloud destination for dbt Core* version 1.9.4. You can use it to run your projects.

NOTE: For this dbt Core version, we don't support MySQL, SQL Server and Azure Synapse destinations. These destinations are not currently supported by custom dbt Core adapters.

* dbt Core is a trademark of dbt Labs, Inc. All rights therein are reserved to dbt Labs, Inc. Fivetran Transformations is not a product or service of or endorsed by dbt Labs, Inc.

Schema changes

Algolia

Effective May 26, 2025 we use a new May 2025 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migration article for more details.

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.

11 total changes • 10 possible breaking changes

Table/column	Change type	Old name	New name	Notes
`CLICK_POSITION`
column	Primary Key Change	`_fivetran_id` 🔑	`_fivetran_id` 🔑	Primary key calculation change.
column	Primary Key Change	`index_name` 🔑	`index_name`	No longer a primary key.
column	New Column		`position`
`CLICK_POSITION_POSITION`
table	Discontinued Table	`CLICK_POSITION_POSITION`
`COUNTRY`
column	Primary Key Change	`start_date`	`start_date` 🔑	Added to primary key.
`FILTER`
column	Primary Key Change	`start_date`	`start_date` 🔑	Added to primary key.
`HIT`
column	Primary Key Change	`_fivetran_id` 🔑	`_fivetran_id` 🔑	Primary key calculation change.
`SEARCH`
column	Primary Key Change	`_fivetran_id` 🔑	`_fivetran_id` 🔑	Primary key calculation change.
`SEARCH_COUNT`
column	Primary Key Change	`_fivetran_id` 🔑	`_fivetran_id` 🔑	Primary key calculation change.
`SEARCH_NO_CLICK`
column	Primary Key Change	`_fivetran_id` 🔑	`_fivetran_id` 🔑	Primary key calculation change.
`SEARCH_NO_RESULT`
column	Primary Key Change	`_fivetran_id` 🔑	`_fivetran_id` 🔑	Primary key calculation change.

Alida

Effective May 15, 2025 we use a new May 2025 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migration article for more details.

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.

4 total changes • 4 possible breaking changes

Table/column	Change type	Old name	New name	Notes
`PROFILE_FIELD`
column	Primary Key Change	`profile_id` 🔑	`profile_id`	No longer a primary key.
`PROFILE_FIELD_TYPE_VALUE`
column	Primary Key Change	`profile_id` 🔑	`profile_id`	No longer a primary key.
`PROFILE_RECORD`
column	Primary Key Change	`profile_id` 🔑	`profile_id`	No longer a primary key.
`PROFILE_RECORD_FIELD`
column	Primary Key Change	`profile_id` 🔑	`profile_id`	No longer a primary key.

Amazon Ads

We've upgraded Bid Recommendation tables from version 3.0 to version 5.0. As part of the upgrade, we've made the following changes:

We've deprecated the following tables:

AD_GROUP_BID_RECOMMENDATION_CLICK
AD_GROUP_BID_RECOMMENDATION_ORDER
ASIN_BID_RECOMMENDATION_CLICK
ASIN_BID_RECOMMENDATION_ORDER

We've backed up the following tables and rebuilt them with new primary keys:

AD_GROUP_BID_RECOMMENDATION_VALUE
AD_GROUP_THEME_BASED_BID_RECOMMENDATION
ASIN_BID_RECOMMENDATION_VALUE
ASIN_THEME_BASED_BID_RECOMMENDATION

We've added the following tables:

AD_GROUP_BID_ANALYSIS
ASIN_BID_ANALYSIS

All changes will be gradually rolled out starting on May 13, 2025.

Until June 14, 2025, all usage generated by the *_ANALYSIS tables will count towards free MAR.

Apple App Store

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

free_trial_win_back_offers
pay_up_front_win_back_offers
pay_as_you_go_win_back_offers

Start a historical re-sync for your connection to backfill the historical data for the new columns, or contact Fivetran's support team to re-sync them for you.

Asana

We have added a new column, start_on, to the PROJECT table.

Chargebee Product Catalog 2.0

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

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.

15 total changes • 14 possible breaking changes

Table/column	Change type	Old name	New name	Notes
`CONTRACT_TERM`
table	New Table		`CONTRACT_TERM`
`INVOICE_LINE_ITEM`
column	Primary Key Change	`invoice_id`	`invoice_id` 🔑	Added to primary key.
`SUBSCRIPTION`
column	Discontinued Column	`contract_term_action_at_term_end`
column	Discontinued Column	`contract_term_billing_cycle`
column	Discontinued Column	`contract_term_cancellation_cutoff_period`
column	Discontinued Column	`contract_term_contract_end`
column	Discontinued Column	`contract_term_contract_start`
column	Discontinued Column	`contract_term_created_at`
column	Discontinued Column	`contract_term_id`
column	Discontinued Column	`contract_term_object`
column	Discontinued Column	`contract_term_remaining_billing_cycles`
column	Discontinued Column	`contract_term_status`
column	Discontinued Column	`contract_term_total_contract_value`
column	Discontinued Column	`contract_term_total_contract_value_before_tax`
column	Rename Column	`monthly_reccuring_revenue`	`monthly_recurring_revenue`

Coupa

We have added the uom_id column to the INVOICE_LINE table and the currency_id column to the ORDER_LINE table.

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

We now support CP_PAYMENT table and its child table.

For information, see our Coupa documentation.

We have added two new columns, adjuster_id and adjuster_type, to the BUDGET_LINE_ADJUSTMENT_TABLE. To backfill historical data for these columns, re-sync the table or contact Fivetran Support to re-sync it for you.

Dropbox Sign

Effective May 7, 2025 we use a new May 2025 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migration article for more details.

We are updating the connector schema to improve data management.

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

6 total changes • 5 possible breaking changes

Table/column	Change type	Old name	New name	Notes
`SIGNATURE_REQUEST_CUSTOM_FIELD`
column	Discontinued Column	`id` 🔑		No longer a primary key.
column	New Column		`api_id`
column	Primary Key Change		`index` 🔑	New primary key.
`SIGNATURE_RESPONSE`
column	Primary Key Change	`field_id` 🔑	`field_id`	No longer a primary key.
column	Primary Key Change	`signature_id` 🔑	`signature_id`	No longer a primary key.
column	Primary Key Change		`index` 🔑	New primary key.

EasyPost

Effective May 12, 2025 we use a new May 2025 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migration article for more details.

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

3 total changes • 0 possible breaking changes

Table/column	Change type	New name
`CASH_FLOW_REPORT`
table	New Table	`CASH_FLOW_REPORT`
`PAYMENT_LOG_REPORT`
table	New Table	`PAYMENT_LOG_REPORT`
`SHIPMENT_INVOICE_REPORT`
table	New Table	`SHIPMENT_INVOICE_REPORT`

Factbird

Effective May 8, 2025 we use a new May 2025 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migration article for more details.

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

9 total changes • 0 possible breaking changes

Table/column	Change type	New name
`BATCH_STOP_CAUSE`
table	New Table	`BATCH_STOP_CAUSE`
`BATCH_STOP_CAUSE_META`
table	New Table	`BATCH_STOP_CAUSE_META`
`STOP`
column	New Column	`standalone_exclude_production`
column	New Column	`target`
column	New Column	`target_current_shift`
column	New Column	`target_next_batch`
column	New Column	`target_previous_batch`
column	New Column	`time_range_from`
column	New Column	`time_range_to`

Fivetran Platform Connector

We've discontinued support and stopped syncing the following columns:

type from the DESTINATION metadata table
connector_id from the INCREMENTAL_MAR metadata table
integration_id from the RESOURCE_MEMBERSHIP metadata table

We have added the new AUDIT_TRAIL table. It enables users to track important actions and changes across their Fivetran account, providing a comprehensive history of user interactions and data modifications.

GitHub

We now support Workflow_run_jobs in our GitHub connector. We are gradually rolling out this change to all existing connecions. We have added new tables, WORKFLOW_RUN_JOB and WORKFLOW_RUN_JOB_STEP.

Greenhouse

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

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
`SCHEDULED_INTERVIEWER`
column	New Column			`response_status`	Available only for connections created on or after July 18, 2024.

HiBob

Effective May 14, 2025 we use a new May 2025 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migration article for more details.

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

2 total changes • 0 possible breaking changes

Table/column	Change type	New name
`EMPLOYEE`
column	New Column	`ethnicity`
column	New Column	`legal_sex`

Jamf

Effective May 7, 2025 we use a new May 2025 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migration article for more details.

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.

10 total changes • 2 possible breaking changes

Table/column	Change type	Old name	New name	Notes
`COMPUTER_INVENTORY`
column	New Column		`disk_encryption_file_vault_2_enabled`
column	New Column		`security_attestation_status`
column	New Column		`security_last_attestation_attempt`
column	New Column		`security_last_successful_attestation`
`COMPUTER_INVENTORY_ALERT`
column	New Column		`class_name`
column	New Column		`post_date`
`COMPUTER_INVENTORY_CONFIGURATION_PROFILE`
column	Primary Key Change	`id` 🔑	`id`	No longer primary key
column	Primary Key Change		`index` 🔑	New primary key
`MOBILE_DEVICE_DETAIL`
column	New Column		`last_attestation_attempt_date`
column	New Column		`last_successful_attestation_date`

Mailgun

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

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	New name	Notes
`INBOX_READY_DOMAIN`
column	Primary Key Change	`id` 🔑	`id`	No longer a primary key.
column	Primary Key Change		`_fivetran_id` 🔑	New primary key.

Microsoft Entra ID

Effective May 16, 2025 we use a new May 2025 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migration article for more details.

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
`ON_PREMISE_ATTRIBUTE_CUSTOM`
column	Rename Column	`users_id` 🔑	`user_id` 🔑	Updated to adhere to standard naming conventions.
`USER_REGISTRATION_DETAIL`
table	New Table		`USER_REGISTRATION_DETAIL`

Navan

We now prefix column names for custom fields in the TRANSACTION table with custom_ to ensure accurate identification and handling.

OnceHub

Effective May 29, 2025 we use a new May 2025 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migration article for more details.

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
`BOOKING`
column	Rename Column		`form_submission_custom_*`	`form_submission_custom_field`

Persona

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

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.

4 total changes • 2 possible breaking changes

Table/column	Change type	Old name	New name	Notes
`INQUIRY`
column	New Column		`tags`
`INQUIRY_TAG`
table	Discontinued Table	`INQUIRY_TAG`		Data is available as a JSON object in the `tags` column of the `INQUIRY` table.
`VERIFICATION`
column	New Column		`checks`
`VERIFICATION_CHECK`
table	Discontinued Table	`VERIFICATION_CHECK`		Data is available as a JSON object in the `checks` column of the `VERIFICATION` table.

Proofpoint Security Awareness

Effective May 1, 2025 we use a new May 2025 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migration article for more details.

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.

1 total changes • 1 possible breaking changes

Table/column	Change type		Old name	New name	Notes
`PHISHING_EXTENDED`
column	Primary Key Change		`_fivetran_id` 🔑	`_fivetran_id` 🔑	Primary key calculation change.

Rippling

Effective May 13, 2025 we use a new May 2025 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migration article for more details.

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.

35 total changes • 34 possible breaking changes

Table/column	Change type	Old name	New name	Notes
`WORKER`
column	Discontinued Column	`annual_compensation_currency_type`		Data is available in the `WORKER_DETAILS` table.
column	Discontinued Column	`annual_compensation_value`		Data is available in the `WORKER_DETAILS` table.
column	Discontinued Column	`compensation_annual_salary_equivalent`		Data is available in the `WORKER_DETAILS` table.
column	Discontinued Column	`compensation_bonus_schedule`		Data is available in the `WORKER_DETAILS` table.
column	Discontinued Column	`compensation_created_at`		Data is available in the `WORKER_DETAILS` table.
column	Discontinued Column	`compensation_id`		Data is available in the `WORKER_DETAILS` table.
column	Discontinued Column	`compensation_payment_term`		Data is available in the `WORKER_DETAILS` table.
column	Discontinued Column	`compensation_payment_type`		Data is available in the `WORKER_DETAILS` table.
column	Discontinued Column	`compensation_target_annual_bonus_percent`		Data is available in the `WORKER_DETAILS` table.
column	Discontinued Column	`compensation_updated_at`		Data is available in the `WORKER_DETAILS` table.
column	Discontinued Column	`compensation_worker_id`		Data is available in the `WORKER_DETAILS` table.
column	Discontinued Column	`custom_fields`		Data is available in the `WORKER_CUSTOM_FIELD` table.
column	Discontinued Column	`employment_type_amount_worked`		Data is available in the `WORKER_DETAILS` table.
column	Discontinued Column	`employment_type_compensation_time_period`		Data is available in the `WORKER_DETAILS` table.
column	Discontinued Column	`employment_type_created_at`		Data is available in the `WORKER_DETAILS` table.
column	Discontinued Column	`employment_type_id`		Data is available in the `WORKER_DETAILS` table.
column	Discontinued Column	`employment_type_label`		Data is available in the `WORKER_DETAILS` table.
column	Discontinued Column	`employment_type_name`		Data is available in the `WORKER_DETAILS` table.
column	Discontinued Column	`employment_type_type`		Data is available in the `WORKER_DETAILS` table.
column	Discontinued Column	`employment_type_updated_at`		Data is available in the `WORKER_DETAILS` table.
column	Discontinued Column	`hourly_wage_currency_type`		Data is available in the `WORKER_DETAILS` table.
column	Discontinued Column	`hourly_wage_value`		Data is available in the `WORKER_DETAILS` table.
column	Discontinued Column	`monthly_compensation_currency_type`		Data is available in the `WORKER_DETAILS` table.
column	Discontinued Column	`monthly_compensation_value`		Data is available in the `WORKER_DETAILS` table.
column	Discontinued Column	`on_target_commission_currency_type`		Data is available in the `WORKER_DETAILS` table.
column	Discontinued Column	`on_target_commission_value`		Data is available in the `WORKER_DETAILS` table.
column	Discontinued Column	`relocation_reimbursement_currency_type`		Data is available in the `WORKER_DETAILS` table.
column	Discontinued Column	`relocation_reimbursement_value`		Data is available in the `WORKER_DETAILS` table.
column	Discontinued Column	`signing_bonus_currency_type`		Data is available in the `WORKER_DETAILS` table.
column	Discontinued Column	`signing_bonus_value`		Data is available in the `WORKER_DETAILS` table.
column	Discontinued Column	`target_annual_bonus_currency_type`		Data is available in the `WORKER_DETAILS` table.
column	Discontinued Column	`target_annual_bonus_value`		Data is available in the `WORKER_DETAILS` table.
column	Discontinued Column	`weekly_compensation_currency_type`		Data is available in the `WORKER_DETAILS` table.
column	Discontinued Column	`weekly_compensation_value`		Data is available in the `WORKER_DETAILS` table.
`WORKER_DETAILS`
table	New Table		`WORKER_DETAILS`

Rocketlane

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

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_FIELD`
table	New Table	`USER_FIELD`
`USERS`
table	New Table	`USERS`

Salesforce Commerce Cloud

We have removed the PRODUCT_VARIANT table because the Products API response does not include product variant data.

Simplecast

Effective May 15, 2025 we use a new May 2025 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migration article for more details.

We are updating the connector schema to improve schema usability.

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

16 total changes • 3 possible breaking changes

Table/column	Change type	Old name	New name	Notes
`APPLICATION`
table	New Table		`APPLICATION`
`AVERAGE_DOWNLOAD`
table	New Table		`AVERAGE_DOWNLOAD`
`BROWSER`
table	New Table		`BROWSER`
`DEVICE`
table	New Table		`DEVICE`
`DEVICE_CLASS`
table	New Table		`DEVICE_CLASS`
`HOURS_LISTENED`
table	New Table		`HOURS_LISTENED`
`LAST_SEVEN`
table	New Table		`LAST_SEVEN`
`LISTENER_PODCAST`
table	New Table		`LISTENER_PODCAST`
`LISTENING_METHOD`
table	New Table		`LISTENING_METHOD`
`NETWORK_TYPE`
table	New Table		`NETWORK_TYPE`
`OPERATING_SYSTEM`
table	New Table		`OPERATING_SYSTEM`
`PODCAST_ANALYTICS_1`
table	Discontinued Table	`PODCAST_ANALYTICS_1`		Data is available in the `AVERAGE_DOWNLOAD` and `HOURS_LISTENED` tables.
`PODCAST_ANALYTICS_2`
table	Discontinued Table	`PODCAST_ANALYTICS_2`		Data is available in the `LAST_SEVEN` and `LISTENER_PODCAST` tables.
`PROVIDER`
table	New Table		`PROVIDER`
`SYSTEM_DATA`
table	Discontinued Table	`SYSTEM_DATA`		Data is available in the `APPLICATION`, `BROWSER`, `DEVICE_CLASS`, `DEVICE`, `LISTENING_METHOD`, `NETWORK_TYPE`, `OPERATING_SYSTEM`, `PROVIDER`, and `WEB_PLAYER` tables.
`WEB_PLAYER`
table	New Table		`WEB_PLAYER`

SolarWinds Service Desk

Effective May 26, 2025 we use a new May 2025 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migration article for more details.

We are updating the connector schema to enhance its usability.

5 total changes • 0 possible breaking changes

Table/column	Change type	New name
`INCIDENT`
column	New Column	`subcategory_default_assignee_id`
column	New Column	`subcategory_default_tag`
column	New Column	`subcategory_deleted`
column	New Column	`subcategory_id`
column	New Column	`subcategory_name`

Split

Effective May 26, 2025 we use a new May 2025 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migration article for more details.

We are updating the connector schema to adhere to standard naming conventions.

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

4 total changes • 3 possible breaking changes

Table/column	Change type	Old name	New name	Notes
`CHANGE_REQUEST_COMMENT`
column	Primary Key Change	`_fivetran_id` 🔑	`_fivetran_id` 🔑	Primary key calculation change.
column	Rename Column	`timestamp` 🔑	`time_stamp` 🔑
column	Rename Column	`user` 🔑	`users` 🔑
`SPLIT_DEFINITION_RULE_BUCKET`
table	New Table		`SPLIT_DEFINITION_RULE_BUCKET`

Tableau

Effective May 27, 2025 we use a new May 2025 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migration article for more details.

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

Workday Financial Management

We have added the following new tables to support the Workday Financial_Management module:

ACCOUNT_POSTING_RULE
ACCOUNT_POSTING_RULE_CONDITION
ACCOUNT_POSTING_RULE_CONDITION_VALUE_GROUP
ACCOUNT_POSTING_RULE_SET
CUSTOMER_ADDRESS_LEVEL_TAX_DETAILS
CUSTOMER_TAX_ENTITY_ACTIVITY_CODE
RESOURCE_CATEGORY
RESOURCE_CATEGORY_ALLOWED_WORKTAGS
RESOURCE_CATEGORY_RELATED_WORKTAGS
UNSPC_CODE_RANGE

We have added the support for following new tables:

AUDIT_TAG
AUDIT_TAG_SEGMENT
COST_CENTER
COST_CENTER_ALLOWED_WORKTAG
COST_CENTER_CONTAINER_ORGANIZATION
COST_CENTER_RELATED_WORKTAG
COST_CENTER_RESTRICTED
CURRENCY_RATE_TYPE
ORGANIZATION_ASSIGNMENT
ORGANIZATION_DOCUMENT_FIELD_RESULT
ORGANIZATION_HIERARCHY_DETAIL
ORGANIZATION_JOB_FAMILY
ORGANIZATION_JOB_PROFILE
ORGANIZATION_JOB_PROFILE_EXEMPT
ORGANIZATION_LEADER
ORGANIZATION_POSITION_GROUP_POSITION
ORGANIZATION_ROLE
ORGANIZATION_ROLE_WORKER
SUPERVISORY_ORGANIZATION_LOCATION

We are gradually rolling out these changes to all existing connections. For more information, see the Workday Financial Management ERD.

Workday HCM

We have made the following schema changes to the connector:

Table Name(s)	Deprecated Primary Key Column(s)
`WORKER_COSTING_ALLOCATION_INTERVAL`	`id`
`WORKER_COSTING_ALLOCATION_DETAIL`	`worker_costing_allocation_interval_id`
`SALARY_OVER_THE_CAP_COSTING_ALLOCATION_DETAIL`	`worker_costing_allocation_interval_id`

Table Name(s)	New Primary Key Column(s)
`WORKER_COSTING_ALLOCATION_INTERVAL`	`index`
`WORKER_COSTING_ALLOCATION_DETAIL`	`worker_costing_allocation_interval_index`
`SALARY_OVER_THE_CAP_COSTING_ALLOCATION_DETAIL`	`worker_costing_allocation_interval_index`

Table Name	New Column
`WORKER_COSTING_ALLOCATION_INTERVAL`	`costing_override_code`

Improvements

Additional PostgreSQL Authentication Mechanisms

We now support the Client Certificate authentication mechanism for the Google Cloud PostgreSQL and Heroku PostgreSQL connectors.

We now support the Microsoft Entra ID authentication mechanism for the Azure Database for PostgreSQL connector.

Amazon DSP

We now perform rollback syncs with a one-day window to capture all the updates made to the INVENTORY table. This addresses the issue where delays from the source lead to some data inaccuracies.

Bizzabo

The Bizzabo connector now supports priority-first sync for the CONTACT table.

Coupa

We now support table-level re-syncs for Coupa connections.

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

Cvent

We now re-import the EVENT table in each sync to capture updates and deletes.

We now incrementally sync the EVENT_TRANSACTION table to capture updates.

Db2 for LUW

The Db2 for LUW connector now supports the Hybrid Deployment model. For more information, see our Db2 for LUW setup guide.

EasyPost

The EasyPost 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. EasyPost's priority-first syncs fetch the past 30 days' worth of data from the following tables:

CASH_FLOW_REPORT
PAYMENT_LOG_REPORT
SHIPMENT_INVOICE_REPORT

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

Fivetran Platform Connector

Metadata sharing tables in our Fivetran Platform Connector are now generally available for all accounts on the Enterprise and Business Critical plans:

These tables provide access to metadata for the data synced by Fivetran, which helps you understand the mapping between the source and the destination. The data retrieved can be easily consumed in BI tools, data catalogs, or through direct SQL queries.

Functions

We have updated the sync strategy of our connectors to prevent the functions from running indefinitely. We now terminate the function connection if we detect more than 10 consecutive empty responses from the function. Make sure to set the hasMore field correctly. For more information, see our response format documentation.

Google Analytics 4

Google Analytics 4 now supports multi-filtering for custom reports.

Google Drive

We now support syncing files to multiple destination tables and handling file patterns. To support these features, we have made the following changes to the connector setup form:

Added the Files field and sub-fields Table name and File pattern, in the connector setup form that enables you to define destination tables and specify the file pattern names.
Renamed the Destination table field to Table group name to enable unique identification of connections that share the same destination schema name.

Also, we have discontinued the table and pattern configuration parameters for all Google Drive connections and will delete them by August 31, 2025.

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

Ivanti

The CI table now supports priority-first sync. Priority-first syncs fetch your most recent data first so that it's quickly ready for you to use.

MySQL

If your connection uses Fivetran Teleport Sync as its incremental update method, we now automatically exclude tables that exceed the 20 million row limit for MySQL and MariaDB connectors.

If your connector uses Fivetran Teleport Sync as its incremental update method, we now support syncing tables with primary keys of DATE and DATETIME types for MySQL and MariaDB connectors.

MySQL destination

We now convert the LOCALDATETIME data type to DATETIME(6) in your destination, instead of DATETIME. This change increases timestamp precision from seconds to microseconds, helping us store more accurate date and time values.

This change applies to all new connections created on or after May 7, 2025. To upgrade the mapping for an existing connection, contact our support team.

NICE

We now use Admin API v32.0 to sync data into the following tables:

AGENT
AGENT_SKILL
GROUPS
GROUP_AGENT
SKILL
TEAM

Recharge

We can no longer retrieve the charge records processed over 90 days ago because Recharge has changed its API. Effective March 19, 2025, Recharge introduced a 90-day lookback restriction on the retrieve and list charge endpoints for API versions 2021-01 and 2021-11.

As a result of this change, Fivetran can't retrieve records from the Charges API endpoints with a processed_at date older than 90 days for processed charges whose status equals success, refunded, or partially refunded.

If you perform a historical re-sync, we can't retrieve charge records with a status of success, refunded, or partially refunded that were processed over 90 days ago. We won't mark these records as deleted unless we receive a delete webhook event.

Rootly

We now support incremental sync for the following tables and their child tables:

ENVIRONMENT
FUNCTIONALITY
INCIDENT_TYPE
POST_MORTEM
TEAM
SERVICE
SEVERITY
USERS

We also re-import these tables and their child tables once a week to capture updates and deletes.

Sage Intacct

We now sync GL_DETAIL table as a child of GL_BATCH this is to capture deletes for GL_DETAIL table. We have also introduced configurable look back window for GL_BATCH and its child endpoints.

We are gradually rolling out these changes to all customers.

Salesforce

We have upgraded our Salesforce connector from version 62.0 to 63.0 of the Salesforce REST API. For more information, see Salesforce's changelog.

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

Snyk

We've enhanced the Snyk connector by adding the US region also as a selectable option in the region drop-down menu.

SQL Server destination

We now support the Fivetran Proxy agent connection method for SQL Server destinations. We are gradually rolling out this feature to all existing destinations.

Stripe

Stripe doesn't incrementally sync the times_redeemed column in the COUPON table. To ensure data accuracy, we re-import this every Saturday.

Talkdesk

We now incrementally sync the RECORD table to capture updates.

Tracksuit

The Tracksuit connector is now in beta. Connect Tracksuit to your Fivetran destination to start syncing data.

Read our Tracksuit connector documentation.

Workday Financial Management

We have added the support for following new tables:

HEADCOUNT_PLAN
HEADCOUNT_PLAN_LINE
HEADCOUNT_PLAN_LINES_WORKTAG
INCLUDED_SPEND_CATEGORIES
SPEND_CATEGORY_HIERARCHY

We are gradually rolling out these changes to all existing connectors. For more information, see the Workday Financial Management ERD.

Wrike

We have changed the sync strategy for our Wrike connector. We now re-import the FOLDER_PROJECT table during every sync to capture updates and deletes.

We have added a new drop-down menu, Plan, to the connection setup form. For more information, see our setup guide.

We have also added a new parameter, plan, to the API connection configuration.

YouGov Sport

We now re-import the following tables once a week to capture updates:

DIGITAL_STREAMING
EVENT
LINEAR_TV
ONLINE_PRESS
SOCIAL_MEDIA
SOCIAL_MEDIA_VIDEO

REST API Improvements

The `groupId` parameter is optional in the Hybrid Deployment Agent API resource

The groupId parameter is now optional when creating a Hybrid Deployment Agent using our REST API. If not provided, Fivetran sets its value to null, allowing for more flexible agent management.

As a result, We made the following updates to our Role-Based Access Control model:

In the REST API, the DESTINATION_CONNECTION_MANAGE permission is replaced by the ACCOUNT_DESTINATION_CREATE permission for the following endpoints:
The System Keys rules are now managed at the account level.

May 2025

Connector SDK

fivetran-connector-sdk PyPI package

Fivetran Azure Switzerland Servers

Lite Connectors

Transformations for dbt Core

New transformation run status

Support of ClickHouse Cloud for dbt Core version 1.9.4

Schema changes

Algolia

Alida

Amazon Ads

Apple App Store

Asana

Chargebee Product Catalog 2.0

Coupa

Dropbox Sign

EasyPost

Factbird

Fivetran Platform Connector

GitHub

Greenhouse

HiBob

Jamf

Mailgun

Microsoft Entra ID

Navan

OnceHub

Persona

Proofpoint Security Awareness

Rippling

Rocketlane

Salesforce Commerce Cloud

Simplecast

SolarWinds Service Desk

Split

Tableau

Workday Financial Management

Workday HCM

Improvements

Additional PostgreSQL Authentication Mechanisms

Amazon DSP

Bizzabo

Coupa

Cvent

Db2 for LUW

EasyPost

Fivetran Platform Connector

Functions

Google Analytics 4

Google Drive

Ivanti

MySQL

MySQL destination

NICE

Recharge

Rootly

Sage Intacct

Salesforce

Snyk

SQL Server destination

Stripe

Talkdesk

Tracksuit

Workday Financial Management

Wrike

YouGov Sport

REST API Improvements

The groupId parameter is optional in the Hybrid Deployment Agent API resource

`fivetran-connector-sdk` PyPI package

The `groupId` parameter is optional in the Hybrid Deployment Agent API resource