September 2026

Connection Cron Scheduling

Connection cron scheduling is now in beta. You can define one or more cron expressions to control exactly when your connection syncs. For more information, see our Sync Frequency and Scheduling documentation.

Connector SDK

fivetran-connector-sdk PyPI package

We have released version 2.12.1 of the fivetran-connector-sdk PyPI package. This release updates grpcio and grpcio-tools dependency version to 1.80.0.

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

• fivetran debug now generates a crash report when your connector code fails, capturing the exception, handler, configuration, and SDK version to help diagnose the failure.
• Memory usage logging now reports the memory consumed by your connector code.
• Improved CLI log output. fivetran debug now aligns log levels and sources and drops the date, while other CLI commands print concise messages.
• The local connector tester binary downloaded by fivetran debug is now cached in .fivetran/connector_sdk/tester in your home directory, replacing the previous .ft_sdk_connector_tester folder.
• Dependency validation is now added to non-interactive flows, previously it was skipped.
• fivetran init --template now supports nested prefix search under examples/.
• Minor enhancements and improvements.
• Updated testers.

Fivetran Proxy Agent

Version 1.2.6

We have released Fivetran Proxy Agent version 1.2.6. This release includes fixes for the following CVEs:

• CVE-2026-59902
• CVE-2026-75595
• CVE-2026-62243

You can download the updated package from the Downloads page.

Logs

Schema field in alter_table log event for column operations

The alter_table log event now includes the schema field for column operations (add column, drop column, and alter column). This provides the schema name along with the table name, giving you complete context when tracking column modifications across different database schemas.

Transformations for dbt

dbt version support

We have added support for dbt version 1.11.15 for the following destinations:

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

We have added support for dbt version 1.12.4 for the following destinations:

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

Transformations for dbt Core is now Transformations for dbt

Fivetran has updated the name of Transformations for dbt Core to Transformations for dbt.

This change is a naming change only. Your transformations, dbt projects, schedules, and connection settings behave exactly as they did before. API endpoint paths, field names, and field values, including the DBT_CORE transformation type, also stay the same.

Learn more in our Transformations for dbt documentation.

Schema changes

Adyen

We have made the following changes:

• Renamed the RECEIVED_PAYMENTS_REPORT_INCOMING table to RECEIVED_PAYMENTS_REPORT. This is now the only table we sync.
• Renamed the previous RECEIVED_PAYMENTS_REPORT table to RECEIVED_PAYMENTS_REPORT_BACKUP_21_09_2026. We no longer sync data to this table.

Be sure to update your downstream queries to reflect these changes. To backfill historical data,re-sync the RECEIVED_PAYMENTS_REPORT table.

Amazon Selling Partner

Amazon is discontinuing its Finance Events API and replacing it with the Transactions API. To support the Transactions API, we have added the following tables:

• TRANSACTION
• TRANSACTION_BREAKDOWN
• TRANSACTION_CONTEXT
• TRANSACTION_ITEM
• TRANSACTION_ITEM_BREAKDOWN
• TRANSACTION_ITEM_CONTEXT
• TRANSACTION_ITEM_RELATED_IDENTIFIER
• TRANSACTION_RELATED_IDENTIFIER

These tables will not contribute to your MAR until October 31, 2026.

We will continue syncing data into the existing Finance Events API tables until December 16, 2026. On that date, we will permanently discontinue these tables, including all child tables of FINANCE_EVENT.

To prepare for this change, be sure to do the following:

• Set your connection's schema change handling setting to Allow all new data to ensure that Fivetran syncs the new Transactions API tables to your destination.
• Update your downstream queries to use the new tables. Failing to do so may lead to missing or incomplete data in your data pipelines.
• If you use the Amazon Selling Partner dbt package in your own dbt environment, upgrade to the latest version of the amazon_selling_partner package for compatibility with the new tables. We will update Fivetran-managed transformations to support the new tables.

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

AppsFlyer

We have added three new tables, SSOT_UNIFIED, SSOT_RETARGETING, and SSOT_USER_ACQUISITION, for connections configured to sync Data Locker events.

Braintree

We have added Table Level Resync for Braintree connector.

Clari

commercetools

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

• discounted_price_cent_amount
• discounted_price_currency_code
• discounted_price_fraction_digits
• discounted_price_id
• discounted_price_type
• discounted_price_type_id

Fivetran Platform Connector

We've added a new column, schedule, to the CONNECTION table.

Freshdesk

We have added the following new tables:

• SOLUTION_ARTICLES
• SOLUTION_CATEGORY
• SOLUTION_FOLDER

Google Ads

We have a new column, ai_max_ad_group_setting_disable_search_term_matching, to the AD_GROUP_HISTORY table.

We've added a new table, CAMPAIGN_ASSET_AUTOMATION_SETTING_HISTORY. The table contains the asset automation type and status (such as Final URL Expansion opt-in/opt-out) configured for each campaign.

HiBob

HubSpot

We have added a new table, PAYMENT_TICKET, to store the association between payments and tickets. When you first include this table in your sync, Fivetran automatically re-syncs its parent table, PAYMENT.

Jira

We have added a new column, sla_name, to the SLA table.

Katana

Kustomer

We have added the following tables:

• AUDIT_LOGS to capture administrative and user actions performed in your Kustomer account
• AUDIT_LOG_ATTRIBUTE_CHANGE to capture attribute-level changes associated with each audit log entry
• AUDIT_LOG_RELATIONSHIP_CHANGE to capture relationship-level changes associated with each audit log entry

Navan

OpenAI

We've added a new table, COST_API_KEY.

Persona

Recurly

We have added a new column, unique_coupon_code_id, to the COUPON_REDEMPTION_HISTORY table.

Reddit Ads

We have added a new column, optimization_goal, to the AD_GROUP table.

We have removed the optimization_strategy_type column from the AD_GROUP table, as Reddit has deprecated this field.

We have added 78 new columns to the CUSTOM_REPORT table:

• app_install_reddit_ad_click_count
• app_install_reddit_ad_click_cvr
• app_install_reddit_ad_click_ecpa
• app_install_reddit_ad_view_count
• app_install_reddit_ad_view_cvr
• app_install_reddit_ad_view_ecpa
• app_install_reddit_add_payment_info_count
• app_install_reddit_add_payment_info_cvr
• app_install_reddit_add_payment_info_ecpa
• app_install_reddit_add_to_cart_count
• app_install_reddit_add_to_cart_cvr
• app_install_reddit_add_to_cart_ecpa
• app_install_reddit_add_to_wishlist_count
• app_install_reddit_add_to_wishlist_cvr
• app_install_reddit_add_to_wishlist_ecpa
• app_install_reddit_app_launch_count
• app_install_reddit_app_launch_cvr
• app_install_reddit_app_launch_ecpa
• app_install_reddit_checkout_count
• app_install_reddit_checkout_cvr
• app_install_reddit_checkout_ecpa
• app_install_reddit_completed_tutorial_count
• app_install_reddit_completed_tutorial_cvr
• app_install_reddit_completed_tutorial_ecpa
• app_install_reddit_first_time_purchase_count
• app_install_reddit_first_time_purchase_cvr
• app_install_reddit_first_time_purchase_ecpa
• app_install_reddit_install_count
• app_install_reddit_install_cvr
• app_install_reddit_install_ecpa
• app_install_reddit_level_achieved_count
• app_install_reddit_level_achieved_cvr
• app_install_reddit_level_achieved_ecpa
• app_install_reddit_login_count
• app_install_reddit_login_cvr
• app_install_reddit_login_ecpa
• app_install_reddit_onboard_completed_count
• app_install_reddit_onboard_completed_cvr
• app_install_reddit_onboard_completed_ecpa
• app_install_reddit_onboard_started_count
• app_install_reddit_onboard_started_cvr
• app_install_reddit_onboard_started_ecpa
• app_install_reddit_purchase_count
• app_install_reddit_purchase_cvr
• app_install_reddit_purchase_ecpa
• app_install_reddit_rate_count
• app_install_reddit_rate_cvr
• app_install_reddit_rate_ecpa
• app_install_reddit_reinstall_count
• app_install_reddit_reinstall_cvr
• app_install_reddit_reinstall_ecpa
• app_install_reddit_revenue
• app_install_reddit_roas
• app_install_reddit_search_count
• app_install_reddit_search_cvr
• app_install_reddit_search_ecpa
• app_install_reddit_sign_up_count
• app_install_reddit_sign_up_cvr
• app_install_reddit_sign_up_ecpa
• app_install_reddit_spend_credits_count
• app_install_reddit_spend_credits_cvr
• app_install_reddit_spend_credits_ecpa
• app_install_reddit_start_trial_count
• app_install_reddit_start_trial_cvr
• app_install_reddit_start_trial_ecpa
• app_install_reddit_subscribe_count
• app_install_reddit_subscribe_cvr
• app_install_reddit_subscribe_ecpa
• app_install_reddit_total_conversions
• app_install_reddit_total_install_count
• app_install_reddit_total_install_cvr
• app_install_reddit_total_install_ecpa
• app_install_reddit_unlock_achievement_count
• app_install_reddit_unlock_achievement_cvr
• app_install_reddit_unlock_achievement_ecpa
• app_install_reddit_view_content_count
• app_install_reddit_view_content_cvr
• app_install_reddit_view_content_ecpa

We have removed the THIRD_PARTY_TRACKER and CLICK_TRACKER tables from the AD entity. Reddit has deprecated these fields and is no longer returning data for them. As an alternative, use the EVENT_TRACKER table.

We have removed the is_processing and search_term columns from the AD table, as Reddit no longer returns these fields.

Salesforce

We have made the following changes to Salesforce system tables in Managed Data Lake Service destinations:

• We have added a new column, query_engine, to the FIVETRAN_FORMULA_MODEL table.
• We now use object and query_engine as the composite primary key of the FIVETRAN_FORMULA_MODEL table.
• We have added a new column, query_engine, to the FIVETRAN_FORMULA_FAILURE_REASON table.

Shopify

We have added the following new tables:

• DRAFT_ORDER_PAYMENT_SCHEDULE
• DRAFT_ORDER_PAYMENT_TERM
• INVENTORY_TRANSFER
• INVENTORY_TRANSFER_LINE_ITEM
• ORDER_LINE_DUTY
• ORDER_LINE_DUTY_TAX_LINE
• ORDER_PAYMENT_SCHEDULE
• ORDER_PAYMENT_TERM
• TRANSLATABLE_RESOURCE
• TRANSLATABLE_RESOURCE_TRANSLATABLE_CONTENT
• TRANSLATABLE_RESOURCE_TRANSLATION

Snapchat Ads

We've added a new column, url_macro_parameters, to the CREATIVE_HISTORY table.

Square

We have made the following changes to the ORDER_FULFILLMENT table:

• Changed the primary key from _fivetran_id to uid
• Added the following new columns:
  • shipment_detail_cancel_reason
  • shipment_detail_canceled_at
  • shipment_detail_carrier
  • shipment_detail_expected_shipped_at
  • shipment_detail_failed_at
  • shipment_detail_failure_reason
  • shipment_detail_in_progress_at
  • shipment_detail_packaged_at
  • shipment_detail_placed_at
  • shipment_detail_recipient_address_address_line_1
  • shipment_detail_recipient_address_address_line_2
  • shipment_detail_recipient_address_address_line_3
  • shipment_detail_recipient_address_administrative_district_level_1
  • shipment_detail_recipient_address_administrative_district_level_2
  • shipment_detail_recipient_address_administrative_district_level_3
  • shipment_detail_recipient_address_country
  • shipment_detail_recipient_address_first_name
  • shipment_detail_recipient_address_last_name
  • shipment_detail_recipient_address_locality
  • shipment_detail_recipient_address_organization
  • shipment_detail_recipient_address_postal_code
  • shipment_detail_recipient_address_sublocality
  • shipment_detail_recipient_address_sublocality_2
  • shipment_detail_recipient_address_sublocality_3
  • shipment_detail_recipient_customer_id
  • shipment_detail_recipient_display_name
  • shipment_detail_recipient_email_address
  • shipment_detail_recipient_phone_number
  • shipment_detail_shipped_at
  • shipment_detail_shipping_note
  • shipment_detail_shipping_type
  • shipment_detail_tracking_number
  • shipment_detail_tracking_url

We will re-sync the ORDER_FULFILLMENT table at no additional cost to apply the new primary key and backfill historical data for the new columns. 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.

TestRail

TikTok Ads

We have added three new columns, campaign_name, adgroup_name, and campaign_automation_type, to the AD_HISTORY table. We have added the following new columns to the AD_HISTORY table:

• adgroup_name
• campaign_automation_type
• campaign_name

We have added support for Custom Creative Reports in the TikTok Ads connector, providing detailed performance insights into creative elements using TikTok's upgraded Smart+ Creative Overview reporting API.

You can now create custom reports for four creative report levels:

1. Advertiser Creative Report (advertiser_creative_report) - requires advertiser_id
2. Campaign Creative Report (campaign_creative_report) - requires campaign_id
3. Ad Group Creative Report (ad_group_creative_report) - requires adgroup_id
4. Smart Plus Ad Creative Report (smart_plus_ad_creative_report) - requires smart_plus_ad_id

Dimension Requirements:

• Exactly 2 dimensions required
• One ID dimension (specific to report type) + one creative dimension:
  • main_material_id
  • ad_text_entity_id
  • call_to_action_entity_id
  • interactive_add_on_entity_id

Aggregations: daily or lifetime

Metrics: 880+ creative performance metrics available

For more information, see TikTok's documentation: https://business-api.tiktok.com/portal/docs/run-an-upgraded-smart-creative-overview-report/v1.3

GMV Max Reports Migration

We have migrated from TikTok's deprecated GMV reporting endpoint to the new GMV Max reporting API. This migration provides enhanced e-commerce metrics and better support for TikTok Shop campaigns.

We have added a new table:

• SHOP - Contains information about GMV Max eligible stores associated with your advertisers

Deprecated Tables:

The following tables are deprecated and will be replaced by the new GMV reports:

• GMV_ADVERTISER_COUNTRY_REPORT_DAILY
• GMV_CAMPAIGN_COUNTRY_REPORT_DAILY

Note: Historical data from these tables will be preserved. The old tables will stop receiving new data once the migration is complete.

New GMV Report Tables:

We have added two new GMV report tables with improved metrics:

1. GMV_ADVERTISER_REPORT_DAILY

Provides advertiser-level GMV metrics aggregated daily.

Primary Keys: advertiser_id, stat_time_day, store_id

New Metrics:

• cost - Total campaign cost
• orders - Number of orders generated
• cost_per_order - Average cost per order
• gross_revenue - Total revenue before deductions
• roi - Return on investment
• net_cost - Net cost after adjustments

2. GMV_CAMPAIGN_REPORT_DAILY

Provides campaign-level GMV metrics aggregated daily, split by promotion type (Product vs Live Shopping).

Primary Keys: campaign_id, stat_time_day, store_id, promotion_type

New Metrics:

• All metrics from advertiser-level report, plus:
• operation_status - Current operational status
• bid_type - Type of bidding strategy
• schedule_type - Campaign scheduling type
• schedule_start_time - Campaign start time
• schedule_end_time - Campaign end time
• target_roi_budget - Target ROI budget setting
• max_delivery_budget - Maximum delivery budget

Promotion Types:

• PRODUCT - Product-focused GMV Max campaigns
• LIVE - Live shopping GMV Max campaigns

Key Differences from Old Reports:

1. Store-level granularity: New reports require a gmv eligible store ID for each record, so connecting stores to advertisers is necessary for accurate reporting
2. Promotion type tracking: Campaign-level reports include promotion_type to distinguish between product and live shopping campaigns
3. Enhanced metrics: New reports include additional metrics like ROI, net cost, and campaign scheduling information
4. No country breakdown: The new reports do not include country-level dimensions

We have added a new column, tiktok_item_id, to the CREATIVE_HISTORY table.

Vonage Contact Center

WooCommerce

Workday Financial Management

We have added the following new tables:

• INVENTORY_PAR_LOCATION
• INVENTORY_PAR_LOCATION_DOCUMENT_STATUS
• INVENTORY_PAR_LOCATION_LINE
• INVENTORY_PAR_LOCATION_LINE_BIN
• INVENTORY_PAR_LOCATION_LINE_BIN_REFERENCE
• INVENTORY_PAR_LOCATION_LINE_SPLIT
• INVENTORY_PAR_LOCATION_LINE_SPLIT_WORKTAG
• INVENTORY_PAR_LOCATION_LINE_WORKTAG
• INVENTORY_PAR_LOCATION_WORKTAG

We have added three new tables, GIFT_HIERARCHY, GIFT_HIERARCHY_GIFT, and GIFT_HIERARCHY_CHILDREN.

We have added two new tables, GRANT_HIERARCHY and GRANT_HIERARCHY_INCLUDED_GRANT.

Zendesk Support

We have added two new tables, CUSTOM_OBJECT_FIELD and CUSTOM_OBJECT_RECORD. The CUSTOM_OBJECT_FIELD table contains the field definitions for your custom objects, so you can understand the structure of your custom data. The CUSTOM_OBJECT_RECORD table contains the individual records created for each custom object type you define in Zendesk, so you can analyze custom business data alongside your support tickets.

We have added a new table, POST_CONTENT_TAG, to store the content tags associated with each community post. We are gradually rolling out this change to all existing connections.

Improvements

Adobe Workfront

We have improved sync reliability for the PORTFOLIO table and its child tables. In addition to incremental syncs, we now re-import these tables once a week to capture updates and deletes.

ADP Workforce Now

We no longer fail a sync if ADP reports that a webhook is active for your application.

Because ADP disables event notifications in this configuration, we use the daily historical sync to update worker data rather than during incremental syncs.

To restore immediate updates, remove the webhook subscription in ADP or use a separate application for Fivetran.

Amazon S3

Our Amazon S3 connector now allows you to sync XLS/XLSX/XLSM files by manually specifying the sheet name and starting cell. To support this enhancement, we have made the following changes:

• Added a new field, Cell, where you can specify the starting cell.
• Added a new field, Sheet name, where you can specify the sheet name.

For more information, see our setup instructions.

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

AppsFlyer

We now support table-level resyncs for the AppsFlyer connector. You can trigger a resync for an individual table without affecting the sync progress of other tables.

Azure Blob Storage

We have added a new configuration option, Private Key Passphrase, to support Client certificate authentication using encrypted private keys. For more information, see our setup instructions and REST API Configuration.

Our Azure Blob Storage connector now allows you to sync XLS/XLSX/XLSM files by manually specifying the sheet name and starting cell. To support this enhancement, we have made the following changes:

• Added a new field, Cell, where you can specify the starting cell.
• Added a new field, Sheet name, where you can specify the sheet name.

For more information, see our setup instructions.

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

BigQuery destination

BigQuery destinations now support column names that contain characters unsupported by Avro, such as column names that start with a number. Previously, Fivetran excluded these columns from syncs. To backfill historical data for these newly supported columns, re-sync your connections. We are gradually rolling out this change to all existing destinations.

We have improved how Fivetran handles large rows in BigQuery. We now evaluate the total row size before applying column-level limits. If the row is under approximately 100 MB, we sync the full values without truncation. If the row exceeds approximately 100 MB, we apply an 8 MB limit to each variable-length column (STRING, JSON, BINARY, and XML) to help reduce the row size.

Previously, we applied the 8 MB per-column limit regardless of the total row size. This change allows tables with fewer columns to sync larger individual values while staying within BigQuery row size limits.

Box

Our Box connector now allows you to sync XLS/XLSX/XLSM files by manually specifying the sheet name and starting cell. To support this enhancement, we have made the following changes:

• Added a new field, Cell, where you can specify the starting cell.
• Added a new field, Sheet name, where you can specify the sheet name.

For more information, see our setup instructions.

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

Ceridian Dayforce

We now sync future data up to 12 months from the current date for the EMPLOYEE_TIME_AWAY_FROM_WORK table.

Culture Amp

We have changed our sync strategy for the MANAGER_REVIEW table. In addition to incremental syncs, we now re-import this table once a day to capture updates and deletes.

Databricks destination

All new connections set up on or after October 5, 2026 preserve the original JSON representation when storing JSON values in STRING columns. Previously, JSON string values such as "true", "null", and "123" could lose their enclosing quotes, potentially changing their meaning in the destination.

Dropbox

Our Dropbox connector now allows you to sync XLS/XLSX/XLSM files by manually specifying the sheet name and starting cell. To support this enhancement, we have made the following changes:

• Added a new field, Cell, where you can specify the starting cell.
• Added a new field, Sheet name, where you can specify the sheet name.

For more information, see our setup instructions.

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

Elasticsearch

We now support Elastic Cloud Serverless as a new service type for our Elasticsearch connector. Learn more in our Elastic Cloud Serverless setup guide.

Email

Our Email connector now allows you to sync XLS/XLSX/XLSM files by manually specifying the sheet name and starting cell. To support this enhancement, we have made the following changes:

• Added a new field, Cell, where you can specify the starting cell.
• Added a new field, Sheet name, where you can specify the sheet name. For more information, see our setup instructions.

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

Facebook Ads

We now fetch additional creatives for an ad account using Meta's /adcreatives endpoint, rather than only those linked to ads and ad images. This may result in higher data volume for the CREATIVE_HISTORY table.

We now support the following fields in our custom report tables:

• converted_product_app_custom_event_fb_mobile_purchase
• converted_product_app_custom_event_fb_mobile_purchase_value
• converted_product_offline_purchase
• converted_product_offline_purchase_value
• converted_product_omni_purchase
• converted_product_omni_purchase_values
• converted_product_website_pixel_purchase
• converted_product_website_pixel_purchase_value
• converted_promoted_product_app_custom_event_fb_mobile_purchase
• converted_promoted_product_app_custom_event_fb_mobile_purchase_value
• converted_promoted_product_offline_purchase
• converted_promoted_product_offline_purchase_value
• converted_promoted_product_omni_purchase
• converted_promoted_product_omni_purchase_values
• converted_promoted_product_website_pixel_purchase
• converted_promoted_product_website_pixel_purchase_value
• product_content_id
• product_name
• product_retailer_id

FTP

We now support Connect via Proxy Agent as a connection method. You can use the Fivetran Proxy Agent to connect to an FTP or FTPS server in a private network without exposing the server directly to the internet. To learn more, see our setup guide.

Our FTP connector now allows you to sync XLS/XLSX/XLSM files by manually specifying the sheet name and starting cell. To support this enhancement, we have made the following changes:

• Added a new field, Cell, where you can specify the starting cell.
• Added a new field, Sheet name, where you can specify the sheet name.

For more information, see our setup instructions.

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

GitLab

We have improved sync reliability for the PROJECT_VULNERABILITY table. We now re-import this table once a week to capture updates and deletes. We are gradually rolling out this change to all existing connections.

Google Cloud Storage

Our Google Cloud Storage connector now allows you to sync XLS/XLSX/XLSM files by manually specifying the sheet name and starting cell. To support this enhancement, we have made the following changes:

• Added a new field, Cell, where you can specify the starting cell.
• Added a new field, Sheet name, where you can specify the sheet name.

For more information, see our setup instructions.

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

Greenhouse

We have made the following schema changes as part of the migration of Greenhouse connections from Harvest API V1 and V2 to V3:

• Added the _V_1 suffix to all table names that contain data from Harvest API V1 and V2
• Removed the _V_3 suffix from all table names that contain data from Harvest API V3

We will continue syncing tables with the _V_1 suffix for as long as Greenhouse provides data through Harvest API V1 and V2. 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.

High-Volume Agent Db2 for i

We have updated the connection setup form with the following changes:

• Renamed the Use database name for table filtering toggle to Use schema and table name for filtering.
• Added a Schema Name Filter field that accepts a SQL LIKE pattern. For example, ABC matches the exact schema name, ABC% matches schema names that start with ABC, and %ABC% matches schema names that contain ABC. For existing connections with the toggle enabled, we automatically populate this field with the value configured in the Named Database field to preserve the existing discovery behavior.
• Added a new Table Name Filter field that accepts a SQL LIKE pattern with the same syntax.

Impact Brand

We have added a new authentication method for our Impact Brand connector. You can now use OAuth 2.0 authentication to connect your Impact Brand account with Fivetran. To support this enhancement, we have added a new field, Authentication type, to the connection setup form, that allows you to select between the Basic and OAuth 2.0 authentication methods.

For more information, see our setup instructions.

Managed Data Lake Service

All new connections set up on or after October 5, 2026 preserve the original JSON representation when storing JSON values in STRING columns. Previously, JSON string values such as "true", "null", and "123" could lose their enclosing quotes, potentially changing their meaning in the data lake.

Maxio Chargify

You can now select the Maxio Chargify domain whose data you want to sync. To support this change, we have added a new drop-down menu, Domain, to the connection setup form.

For more information, see our setup instructions.

Maxio SaaSOptics

We have added a new drop-down, Application domain, to the connection setup form. You can now select the domain that matches your Maxio SaaSOptics account hostname.

For more information, see our Maxio SaaSOptics setup guide.

Oracle destination

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

Pardot

We have added External Client App as a new authentication method for the Pardot and Pardot Sandbox connectors. To support this enhancement, we have made the following changes:

• Added External Client App as a new option in the Auth Type field on the connection setup form.
• Added two new fields, Client ID and Client Secret, to the connection setup form. These fields appear only when you select External Client App authentication and allow you to provide your Salesforce External Client App credentials.
• Added a new field, My Domain URL, to the connection setup form. This field appears only when you select External Client App authentication and allows you to specify your Salesforce domain URL.
• Added the following parameters to the Fivetran REST API: clientId, clientSecret, and myDomainUrl.

For more information, see our setup instructions.

PostgreSQL

PostgreSQL connections that use Query-Based incremental sync method now support the DDL statement ALTER TABLE ... ADD COLUMN ... DEFAULT .... For more information, see our PostgreSQL documentation.

Pylon Support Platform

We have added a new drop-down, Region, to the connection setup form. You can now select either US or EU, depending on the region where your Pylon Support Platform account resides.

For more information, see our Pylon Support Platform setup guide.

Row filtering support for Float, Double, and BigDecimal data types

Row filtering now supports the Float, Double, and BigDecimal data types. You can enter values in standard decimal notation (1.23, -0.005) or scientific notation (1.23e-4, -4.5e10), and use these types with all supported operators, including In.

Float and Double values must fall within their respective IEEE 754 range limits. BigDecimal values are stored and compared as arbitrary-precision decimals with no enforced range limit.

For more information, see our row filtering documentation.

S3-Compatible Storage

The S3-Compatible Storage connector is now generally available.

Read our S3-Compatible Storage connector documentation.

Our S3-Compatible Storage connector now allows you to sync XLS/XLSX/XLSM files by manually specifying the sheet name and starting cell. To support this enhancement, we have made the following changes:

• Added a new field, Cell, where you can specify the starting cell.
• Added a new field, Sheet name, where you can specify the sheet name.

For more information, see our setup instructions.

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

Salesforce

We now support Salesforce formula field translations for Managed Data Lake Service destinations.

To use translated formula fields with a Managed Data Lake Service destination, use version 0.12.0 or later of the fivetran/salesforce_formula_utils dbt package.

For more information, see our supported SQL dialects documentation.

SAP ERP on HANA

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

• We have added new RFC-enabled functions to read application server files through NetWeaver.
• We now support SAP HANA 2.0 SPS 03 or later.
• We have fixed an issue that was causing silent data loss for LOB columns longer than 32 KB.
• We have fixed a cursor leak that was causing exceptions during mass trigger re-creation activity.

SAP SuccessFactors

We have improved sync reliability for the FO_DEPARTMENT and EMPLOYEE_PAY_COMP_RECURRING tables by using a 2-day lookback window during incremental syncs.

SFTP

Our SFTP connector now allows you to sync XLS/XLSX/XLSM files by manually specifying the sheet name and starting cell. To support this enhancement, we have made the following changes:

• Added a new field, Cell, where you can specify the starting cell.
• Added a new field, Sheet name, where you can specify the sheet name.

For more information, see our setup instructions.

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

We now support Connect via Proxy Agent as a connection method. You can use the Fivetran Proxy Agent to connect to an SFTP server in a private network without configuring an SSH tunnel or exposing the server directly to the internet. To learn more, see our setup guide.

We have added a new authentication method, Customer-supplied key, for our SFTP connector. You can now authenticate Fivetran to your SFTP server using your own SSH private key in OpenSSH or PEM format (RSA 2048-bit minimum, ED25519, or ECDSA). To support this feature, we have added the following fields to the connection setup form:

• Customer-supplied key
• Private Key
• Passphrase

For more information, see our setup instructions.

SharePoint

We have added a new configuration option, Private Key Passphrase, to support Client certificate authentication using encrypted private keys. For more information, see our setup instructions and REST API Configuration.

Our SharePoint connector now allows you to sync XLS/XLSX/XLSM files by manually specifying the sheet name and starting cell. To support this enhancement, we have made the following changes:

• Added a new field, Cell, where you can specify the starting cell.
• Added a new field, Sheet name, where you can specify the sheet name.

For more information, see our setup instructions.

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

Snowflake

We have fixed a bug where the "Enable change streams" warning could continue to show after its table or view was removed from the source, deselected from the sync, or had change tracking enabled.

Stripe

Our Stripe connector can now capture updates to the hosted_invoice_url and invoice_pdf columns. We now re-sync the INVOICE table weekly to capture updates to these columns. To support this enhancement, we have added a new toggle, Resync Invoice table weekly, to the connection setup form. You can enable this feature by setting the toggle to ON. For more information, see our setup instructions. We are gradually rolling out this enhancement to all existing connections.

Workday RaaS

Our Workday RaaS connector now supports a new query mode, WQL. WQL queries fetch report data in paginated ranges, allowing us to sync large reports incrementally without exceeding Workday's report size limit. To support this query mode, we have added the following fields to the connection setup form:

• Query Mode
• WQL QUERY
• Enable Incremental Filter
• Select Report Incremental Date Field
• Select incremental start date

Xero

We now support syncing Journals data for Xero connections. To support this enhancement, we have added a new toggle, Sync Journal Data, to the setup form. New Xero connections created after September 22, 2026, using Web app can enable this option during configuration. This feature is available only for Xero accounts on the Advanced or Enterprise tiers. We are gradually rolling out this feature to all existing connections. For more information, see our setup instructions.

REST API Improvements

Connection Warnings REST API Private Preview

You can now retrieve and dismiss warnings for a connection using the REST API:

• The Retrieve Connection Warnings endpoint returns all active warnings for a connection, grouped by destination table. Each warning includes the warning code, message, error details, and creation timestamp.

• The Dismiss Connection Warnings endpoint allows you to dismiss all active instances of a specific warning type for a connection, mirroring the dismissal functionality in the dashboard. This enables programmatic warning management for customers with large numbers of tables.

NOTE: This feature is currently in private preview. Please submit a support ticket if you would like to try out this feature.