July 2026

Connector SDK

fivetran-connector-sdk PyPI package

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

• Added validation for unique field names within a table.
• Improved fivetran init behavior.
• Improved error detection for connector object issues in the tester.

We have released version 2.10.1 of the fivetran-connector-sdk PyPI package. This release supersedes the yanked 2.10.0 release and includes the following updates:

• Fixed an issue with downloading the stable updated testers.
• Added validation for empty table names.
• Improved logging for agent plugins.
• Minor enhancements and improvements.

(Yanked: Tester Version Mismatch) We have released version 2.10.0 of the fivetran-connector-sdk PyPI package. This release includes the following updates:

• Added validation for empty table names.
• Improved logging for agent plugins.
• Minor enhancements and improvements.
• Updated testers.

Lite Connectors

Lite connectors are now available for the following sources:

• Deel
• Profound
• Sevdesk

Logs

Dynatrace External Logging

We now support Dynatrace as an external logging service. You can connect Dynatrace at both the account and destination levels to collect and query your Fivetran logs. We are gradually rolling out this feature to all accounts.

To set up the Dynatrace logging service, go to Account Settings > General> External Logging, or go to your destination settings in your Fivetran dashboard. For more information, see our Dynatrace Setup Guide.

Managed Data Lake Service

Effective July 22, 2026 we preserve null byte characters in string values for data lakes managed by Managed Data Lake Service. Previously, we removed null byte characters before writing string values to the data lake, which could cause differences between the source and destination data.

Partner SDK

Partner SDK Tester

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

• Updated the connector tester to use a form field's default value when no input is provided during Partner SDK configuration prompts.
• Added a message that shows when the connector tester uses a default value.

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

• Updated the destination tester to get the batch file format from the Capabilities RPC instead of defaulting to CSV.
• Added validation for unsupported batch file formats returned by the Capabilities RPC.

Sunset Connectors

AVEVA PI

We have sunset the AVEVA PI connector.

Effective July 1, 2026, we no longer support the creation of new AVEVA PI connections. Existing AVEVA PI connections will stop syncing on July 23, 2026.

Delighted

We have sunset the Delighted connector due to the deprecation of the Delighted API.

Effective July 1, 2026, we no longer support the creation of new Delighted connections. Existing Delighted connections will be paused.

Transformations for dbt Core

Automatic dbt deps setting

We've added a new Automatically run dbt deps toggle to the Transformations for dbt Core setup form. The setting is enabled by default.

When enabled, Fivetran automatically runs the dbt deps service command before transformation runs if your dbt project contains a packages.yml or dependencies.yml file. When disabled, Fivetran skips the automatic dbt deps service command. Explicit dbt deps commands in your transformation jobs still run.

You can disable this setting if you manage dbt packages manually or need custom workarounds for package issues at any time. To disable the setting:

1. In the Fivetran dashboard, click Transformations.
2. Click Manage projects.
3. In the transformation list, click the three dots on the right side of the relevant dbt project.
4. Click Edit connection settings.
5. Set the Automatically run dbt deps toggle to off.
6. Click Save & Test.

Schema changes

AdRoll

We have added new dimension columns to the ALL_ADS, ALL_ADGROUPS, ALL_CAMPAIGNS, and ALL_ADVERTISABLES report types. These columns contain additional dimension fields returned by the AdRoll API and can be selected in your connection's Dimensions configuration.

Algolia

Amazon DSP

We added the ADVERTISER_ID column to the MEASUREMENT_STUDY table.

Braze

We have added a new table, CANVAS_STEP_PROGRESSION_EVENT.

Buildkite

Cornerstone

FireHydrant

Front

We have added new custom_* columns to the following tables to sync data from custom fields:

• CONVERSATION
• INBOX
• TEAMMATE

GitLab

Gladly

Intercom

We have added two new tables, MESSAGE_OPEN and SERIES_DISENGAGEMENT.

Ironclad

Jira

We now capture deletes for the ASSET_OBJECT table using the _fivetran_deleted column. Perform a resync to backfill historical data.

LinkedIn Ad Analytics

We've added a new table, DOCUMENT. The table contains document media assets referenced by posts, including the download URL, its expiration time, owner, and processing status.

Loopio

Microsoft Teams

OpenAI

We have added the following new tables to store Codex Enterprise Analytics API data:

• CODEX_CODE_REVIEW
• CODEX_CODE_REVIEW_RESPONSE
• CODEX_USAGE
• CODEX_USAGE_CLIENT
• CODEX_USAGE_MODEL

PagerDuty

Personio

Picqer

Planhat

Reddit Ads

We've added a new table, CLICK_URL_QUERY_PARAMETER. The table contains user-defined query parameters that are appended to the ad's click URL when users click on ads.

Shopify

We now sync company metafields into the existing metafield table (where owner_resource = 'COMPANY').

Square

We have added the following new tables:

• DEVICE
• DEVICE_COMPONENT
• TEAM_MEMBER
• TEAM_MEMBER_ASSIGNED_LOCATION
• TEAM_MEMBER_WAGE
• TIMECARD
• TIMECARD_BREAK

We have deprecated the following tables as Square has deprecated the associated objects from its API:

We are gradually rolling out these changes to all existing connections. Be sure to update your downstream queries to align with these changes. Failing to do so may lead to missing or incomplete data in your data pipelines. To backfill historical data into the new tables and columns, re-sync the affected tables.

TikTok Ads

We have deprecated the following prebuilt Reservation Ads report tables because TikTok removed the Reservation report type from their API:

• RESERVATION_CAMPAIGN_REPORT_DAILY
• RESERVATION_ADGROUP_REPORT_DAILY
• RESERVATION_AD_REPORT_DAILY
• RESERVATION_CAMPAIGN_REPORT_HOURLY
• RESERVATION_ADGROUP_REPORT_HOURLY
• RESERVATION_AD_REPORT_HOURLY

These tables will no longer sync data. We have also removed the ability to create custom Reservation Ads reports, and any existing custom Reservation Ads reports will stop syncing. TikTok recommends using Auction Ads reports instead, which include data for both auction and reservation ad accounts.

We have added the following metrics to custom audience reports:

• Attribute Metrics:
  • delivery_type
  • adgroup_display_name
  • adgroup_schedule
  • optimization_preference
  • image_info
  • ad_display_name
  • identity_type

Workday Financial Management

We've added a new table, ALLOCATION_POOL_HIERARCHY. The table contains allocation pool hierarchy definitions used for organizing and categorizing allocation pools.

We've added a new table, ALLOCATION_POOL_HIERARCHY_POOL. The table contains the allocation pool members that belong to each allocation pool hierarchy.

We've added the following new tables:

• ALLOCATION_POOL_WORKTAG_OVERRIDE_RULE
• ALLOCATION_POOL_WORKTAG_OVERRIDE_RULE_WORKTAG
• ALLOCATION_POOL_WORKTAG_OVERRIDE_RULE_CONDITION

We've added new tables, ALLOCATION_PLAN, ALLOCATION_PLAN_TIER, ALLOCATION_PLAN_BOOK_CODES_MAPPING, RESTRICTED_TO_JOURNAL_SOURCE, RESTRICTED_TO_POOL_COMPANY, RESTRICTED_TO_LEDGER_TYPE, EXCLUDED_JOURNAL_SOURCE, RESTRICTED_TO_SOURCE_COMPANY, RESTRICTED_TO_LEDGER_ACCOUNT_TYPE, and DEFAULT_OPTIONAL_BALANCING_WORKTAG.

Workday HCM

We have added a new column, city, to the CANDIDATE table.

We have stopped syncing data into the costing_override_worktag_ids column of the WORKER_COSTING_ALLOCATION_DETAIL table since we sync the same data in the id column of the WORKER_COSTING_ALLOCATION_DETAIL_WORKTAG table. You can now discontinue using the costing_override_worktag_ids column in your downstream transformation, and remove it from your destination.

Improvements

Adyen

We have fixed a bug that prevented the exchange_rate_platform_settlement and valid_from columns from syncing in the EXCHANGE_RATE_REPORT table. By default, we will re-sync the EXCHANGE_RATE_REPORT table to backfill the historical data for these columns. This table re-sync will count towards free MAR.

Amazon Selling Partner

We now support table re-sync for our Amazon Selling Partner connector. Previously, we only supported connection-level re-syncs.

Apollo

We have updated the sync strategy for the CONTACT table. We now re-import the table every week to capture updates and deletes. Previously, we only incrementally synced the table to capture new records and updates.

BigQuery destination

Effective July 22, 2026 we preserve null byte characters in string values for all BigQuery destinations. Previously, we removed null byte characters before writing string values to the destination, which could cause differences between the source and destination data.

Clari

We now use the Export API to sync the data for the following tables and their child tables:

• FIELD
• FORECAST_ENTRY
• TIME_FRAME
• TIME_PERIOD
• USERS

We are gradually rolling out this improvement to all existing connections. This migration requires no action on your part.

Confluent Cloud

We now support OAuth 2.0 authentication for the Confluent Cloud connector. You can select your authentication method (API Key or OAuth 2.0) using either one of the following:

• Connection setup form: Use the new Authentication method field.
• Fivetran REST API: Specify either API_KEY or OAUTH in the new auth_method parameter.

For more information, see our setup guide and Fivetran REST API.

Databricks destination

Effective July 22, 2026 we preserve null byte characters in string values for Databricks destinations. Previously, we removed null byte characters before writing string values to the destination, which could cause differences between the source and destination data.

Expensify

We have improved data integrity for the REPORT_ACTION_LIST and REPORT_APPROVER tables. We now use a 31-day lookback window during incremental syncs for these tables.

FTP

We have added a new feature, Dynamically extract tables. You can now define a single regex pattern with a named capture group, (?<table>...), to automatically extract table names from file paths. This feature automatically creates and maps destination tables based on your file naming patterns, eliminating the need for manual intervention.

To support this feature, we have made the following changes to the connection setup form:

• Added a new option, File mapping, that allows you to choose between Define per table and Dynamically extract tables.
• Added a new field, Table extraction pattern, to specify your own regex pattern.
• Added a new button, Preview, to validate the specified regex pattern.

Key benefits include:

• Simplified configuration: Avoids repetitive setup for multiple entities.
• Automatic table creation: Captures new entities as they appear in your source, without additional configuration.

For more information, see our Dynamic Table Mapping tutorial and setup instructions.

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

We now support specifying custom primary keys for tables created through dynamic table mapping.

Mambu

We have changed our sync strategy for the DEPOSIT_TRANSACTION table. We now incrementally sync the table.

MySQL

We now support AWS IAM database authentication for connections using AWS PrivateLink. To use IAM authentication with AWS PrivateLink, provide your database's Database Endpoint in the connection setup form. For more information, see the Amazon Aurora MySQL setup guide and the RDS MySQL setup guide.

MySQL destination

Effective July 22, 2026 we preserve null byte characters in string values for all MySQL implementations. Previously, we removed null byte characters before writing string values to the destination, which could cause differences between the source and destination data.

Oracle

We now support syncing XMLType columns using the Binary Log Reader incremental sync method in Private Preview.

We only support the binary XML storage model. Supplemental logging for primary key columns or all columns must be enabled on the table. Learn more in our Oracle connector documentation.

Qualtrics

We now capture deletes for the SURVEY_RESPONSE table. We perform a re-sync of the SURVEY_RESPONSE table every week to capture the deleted records. Previously, we only incrementally synced this table to capture updates.

Snowflake destination

Effective July 22, 2026 we preserve null byte characters in string values for Snowflake destinations. Previously, we removed null byte characters before writing string values to the destination, which could cause differences between the source and destination data.

SQL Server

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

SQL Server destination

Effective July 22, 2026 we preserve null byte characters in string values for all SQL Server implementations. Previously, we removed null byte characters before writing string values to the destination, which could cause differences between the source and destination data.

REST API Improvements

Move Connection REST API (Beta)

You can now move connections from one destination group to another using the Move a Connection (Beta) REST API endpoint.