November 2026
Connector SDK
fivetran-connector-sdk-core PyPI package
We have released version 0.2.1 of the fivetran-connector-sdk-core PyPI package. This release includes the following updates:
- Added validation that rejects connectors that mix multiple-schema and single-schema declarations, and raises a clear error.
- Minor enhancements and improvements.
We have released version 0.2.0 of the fivetran-connector-sdk-core PyPI package. This release includes the following updates:
- Logs a warning when the core changes a value, such as storing a
NaNor a number with too many digits asNULL, or removing null characters from text. - Improved the error messages of
fivetran runfor an Iceberg catalog, so that they say which setting or table to fix.
Fivetran Connector SDK
We now soft delete any previous records that your connection didn't send again when a re-sync is triggered from the Fivetran dashboard. For more information, see re-syncs and deletions.
We now support deferred truncate for Connector SDK connections. Refer to deferred truncate for more details.
When you update a connection's credentials through the REST API or by redeploying with a new configuration.json, only the keys you include are changed. Keys you don't include keep their existing value instead of being removed. To delete a credential, set its value to null. For more information, see Updating credentials.
You can now disable code download for a Connector SDK package by setting download_enabled = false in the [tool.package-metadata] section of your pyproject.toml file. For more information, see Disable code download.
fivetran-connector-sdk PyPI package
We have released version 3.1.1 of the fivetran-connector-sdk PyPI package. This release includes the following updates:
- Released record and replay regression testing in Public Preview. Use the
@actiondecorator to mark your source-reading functions, record a scenario withfivetran debug --record <scenario>, and replay it to catch changes in the data your connector delivers. - Improved the connection setup form experience.
- Minor enhancements and improvements.
We have released version 3.1.0 of the fivetran-connector-sdk PyPI package. This release includes the following updates:
- Added support for deferred truncate, which marks a table's existing rows as deleted only after the sync completes successfully, ensuring that existing data is preserved if the sync fails.
- Added support for reading package defaults from
pyproject.tomlwhen resolving deployment values from multiple sources. For more information, see field resolution order. - Improved the fivetran run command with bug fixes and enhanced logging.
- Improved template search and overwrite prompts for the fivetran init command.
- Minor enhancements and improvements.
Managed Data Lake Service
Managed Data Lake Service
The Update BigQuery Metastore option for GCS data lakes is deprecated, and no longer available for newly created Managed Data Lake destinations. For existing destinations, this toggle is now read-only, and those that already use it will continue to work. To query your data lake in BigQuery, set up a BigQuery destination that uses Iceberg tables.
We have deprecated the Retain All Snapshots option for the Snapshot Retention Period setting in the destination setup form. You can no longer select it for new destinations, and you can't switch an existing destination to it in the setup form or with the REST API. If your destination already uses Retain All Snapshots, you don't need to do anything. Otherwise, select another retention period.
We are gradually rolling out this change to all existing Managed Data Lake destinations. For more information, see our snapshot retention period documentation.
Transformations for dbt
Upcoming end of support for dbt versions 1.0, 1.1, and 1.2
We will end support for dbt versions 1.0, 1.1, and 1.2. These versions run only on Python 3.9, which reached end of life in October 2025, so we can no longer apply security fixes to their dependencies.
If your projects use dbt version 1.0, 1.1, or 1.2, we will automatically migrate them to the latest patch release of dbt version 1.3. We will communicate the exact date of the migration by email. Migration to dbt version 1.3 might impact the execution of dbt transformations.
To upgrade a project yourself before the migration, select dbt version 1.10.20 or later in the dbt Version drop-down menu of the project's connection settings.
New connectors
Guidewire Cloud Data Access
Guidewire Cloud Data Access (CDA) streams raw InsuranceSuite data and changes as Parquet files for downstream analytics and integrations. Read our Guidewire Cloud Data Access connector documentation.
Schema changes
Amazon Ads
Amazon has deprecated the searchTermImpressionRank and searchTermImpressionShare metrics in the Sponsored Brands v2 keyword and search term reports. As of November 10, 2026, we no longer sync new values for the search_term_impression_rank and search_term_impression_share columns in the SB_KEYWORD_REPORT and SB_SEARCH_TERM_REPORT tables. The values we already synced for earlier report dates stay in your destination, except for the last few days before November 10, 2026. If you re-sync these tables, the columns become NULL for report dates in the last 60 days, because Amazon keeps Sponsored Brands v2 report data for only 60 days.
See more information in the Amazon documentation.
commercetools
We have added a new column, purchase_order_number, to the ORDERS table.
Concord
| Table/column | Change type | Old name | New name | Notes | |
|---|---|---|---|---|---|
AGREEMENT_PROPERTY | |||||
| table | New Table | AGREEMENT_PROPERTY | |||
Dixa
| Table/column | Change type | Old name | New name | Notes | |
|---|---|---|---|---|---|
END_USER | |||||
| column | New Column | external_id | |||
Freshdesk
We've added a new table, TICKET_SUMMARY.
GoCardless
| Table/column | Change type | Old name | New name | Notes | |
|---|---|---|---|---|---|
EVENT | |||||
| column | Discontinued Column | links_installment_schedule | |||
| column | New Column | link_installment_schedule | |||
PAYMENT | |||||
| column | Discontinued Column | links_installment_schedule | |||
| column | New Column | link_installment_schedule | |||
HubSpot
We have added the following new tables:
APPOINTMENTAPPOINTMENT_COMPANYAPPOINTMENT_CONTACTAPPOINTMENT_DEALAPPOINTMENT_ENGAGEMENTAPPOINTMENT_PIPELINEAPPOINTMENT_PIPELINE_STAGEAPPOINTMENT_PROJECTAPPOINTMENT_PROPERTY_HISTORYAPPOINTMENT_TICKET
Intercom
We have added the following new tables:
COMPANY_NOTE_HISTORYCONTACT_MERGECONVERSATION_EXTERNAL_REFERENCECONVERSATION_MONITOR_EVALUATIONCONVERSATION_SCORECARDDATA_CONNECTORDATA_CONNECTOR_EXECUTIONSIDE_CONVERSATION_PART
We have added the following new columns:
| Table | Columns |
|---|---|
ARTICLE_HISTORY | ai_chatbot_availability, ai_copilot_availability, ai_sales_agent_availability, body_markdown, created_by_id, exclude_from_article_suggestions, help_center_audience, scheduled_publish_at, scheduled_unpublish_at, and updated_by_id |
CONTACT_HISTORY | email_domain |
CONVERSATION_HISTORY | channel_current, channel_initial, sales_agent_outcome, sales_agent_participated, sales_agent_routing_outcome, source_email_message_metadata_history, source_email_message_metadata_message_id, and source_email_message_metadata_subject |
EMAIL_ADDRESS_HEADER | drop_reason |
TICKET_HISTORY | previous_ticket_state_id |
Ivanti
| Table/column | Change type | Old name | New name | Notes | |
|---|---|---|---|---|---|
FRS_COMPOSITE_CONTRACT_MAPPING | |||||
| column | Primary Key Change | rec_id 🔑 | rec_id | No longer a primary key. | |
| column | Primary Key Change | id 🔑 | New primary key. | ||
FRS_DATA_ENCRYPTION_KEYS | |||||
| column | Primary Key Change | rec_id 🔑 | rec_id | No longer a primary key. | |
| column | Primary Key Change | name 🔑 | New primary key. | ||
FRS_DATA_ENCRYPTION_PUBLICKEYS | |||||
| column | Primary Key Change | rec_id 🔑 | rec_id | No longer a primary key. | |
| column | Primary Key Change | name 🔑 | New primary key. | ||
FRS_SURVEY | |||||
| column | Primary Key Change | rec_id 🔑 | rec_id | No longer a primary key. | |
| column | Primary Key Change | id 🔑 | New primary key. | ||
FRS_SURVEY_ANSWER | |||||
| column | Primary Key Change | rec_id 🔑 | rec_id | No longer a primary key. | |
| column | Primary Key Change | id 🔑 | New primary key. | ||
FRS_SURVEY_CHOICE | |||||
| column | Primary Key Change | rec_id 🔑 | rec_id | No longer a primary key. | |
| column | Primary Key Change | id 🔑 | New primary key. | ||
FRS_SURVEY_QUESTION | |||||
| column | Primary Key Change | rec_id 🔑 | rec_id | No longer a primary key. | |
| column | Primary Key Change | id 🔑 | New primary key. | ||
FRS_SURVEY_QUESTION_CATEGORY | |||||
| column | Primary Key Change | rec_id 🔑 | rec_id | No longer a primary key. | |
| column | Primary Key Change | id 🔑 | New primary key. | ||
FRS_SURVEY_SESSION | |||||
| column | Primary Key Change | rec_id 🔑 | rec_id | No longer a primary key. | |
| column | Primary Key Change | id 🔑 | New primary key. | ||
LOGS | |||||
| column | Primary Key Change | rec_id 🔑 | rec_id | No longer a primary key. | |
| column | Primary Key Change | log_entry_id 🔑 | New primary key. | ||
Lightspeed Retail X-Series
| Table/column | Change type | Old name | New name | Notes | |
|---|---|---|---|---|---|
REGISTER | |||||
| table | New Table | REGISTER | |||
Paddle
| Table/column | Change type | Old name | New name | Notes | |
|---|---|---|---|---|---|
ADJUSTMENT | |||||
| column | New Column | payout_total_retained_fee | |||
| column | New Column | total_retained_fee | |||
Personio
| Table/column | Change type | Old name | New name | Notes | |
|---|---|---|---|---|---|
ATTRIBUTE | |||||
| table | New Table | ATTRIBUTE | |||
ATTRIBUTE_OPTION | |||||
| table | New Table | ATTRIBUTE_OPTION | |||
Phoenix Ads
| Table/column | Change type | Old name | New name | Notes | |
|---|---|---|---|---|---|
REPORT | |||||
| column | New Column | ad_group_id | |||
| column | New Column | ad_group_name | |||
| column | New Column | ad_id_2_0 | |||
| column | New Column | ad_name_2_0 | |||
| column | New Column | campaign_id_2_0 | |||
| column | New Column | campaign_name_2_0 | |||
| column | New Column | is_new_system | |||
Productive
| Table/column | Change type | Old name | New name | Notes | |
|---|---|---|---|---|---|
EXPENSE | |||||
| column | Deprecated Column | service_id | |||
FOLDER | |||||
| table | New Table | FOLDER | |||
TASK_LIST | |||||
| column | Deprecated Column | board_id | |||
| column | New Column | folder_id | Data is available in the folder_id column of the TASK_LIST table. | ||
TIME_ENTRY_VERSION | |||||
| column | New Column | deal_id | Data is available in the deal_id column of the TIME_ENTRY_VERSION table. | ||
| column | New Column | person_id | Data is available in the person_id column of the TIME_ENTRY_VERSION table. | ||
SAP Concur
We have added a new table, EXPENSE_NO_SHOW_ATTENDEE, which contains the number of no-show attendees for each expense. We sync this table only for connections that use company-level OAuth.
To populate the table with data from existing reports, re-sync the REPORT table or any of its child tables. The first re-sync you trigger before February 2, 2027 will not contribute to your MAR for those tables.
SAP SuccessFactors
| Table/column | Change type | Old name | New name | Notes | |
|---|---|---|---|---|---|
JOB_APPLICATION_STATUS_AUDIT_TRAIL | |||||
| column | New Column | job_app_status_id | |||
| column | New Column | job_app_status_set_id | |||
| column | New Column | job_application_id | |||
ShipHero
| Table/column | Change type | Old name | New name | Notes | |
|---|---|---|---|---|---|
ORDER_LINE_ITEM | |||||
| column | Primary Key Change | line_item_id | line_item_id 🔑 | Added to primary key. | |
| column | Primary Key Change | sku 🔑 | sku | No longer a primary key. | |
ORDERS | |||||
| column | New Column | shipping_line_carrier | |||
| column | New Column | shipping_line_method | |||
| column | New Column | shipping_line_price | |||
| column | New Column | shipping_line_title | |||
ORDERS_TAG | |||||
| table | New Table | ORDERS_TAG | |||
| column | New Column | order_id | |||
| column | New Column | tag_name | |||
PACK_PER_DAY | |||||
| column | New Column | user_first_name | |||
| column | New Column | user_id | |||
| column | New Column | user_last_name | |||
PRODUCT_VENDOR | |||||
| table | New Table | PRODUCT_VENDOR | |||
| column | New Column | price | |||
| column | New Column | product_id | |||
| column | New Column | vendor_id | |||
| column | New Column | vendor_sku | |||
SHIPMENT_LINE_ITEM | |||||
| column | Primary Key Change | id | id 🔑 | Added to primary key. | |
| column | Primary Key Change | line_item_id 🔑 | line_item_id | No longer a primary key. | |
| column | New Column | line_item_id | |||
| column | New Column | partner_line_item_id | |||
| column | New Column | price | |||
| column | New Column | shipping_label_id | |||
| column | New Column | sku | |||
SHIPMENT_SHIPPING_LABEL | |||||
| column | New Column | alternate_tracking_id | |||
| column | New Column | image_location | |||
| column | New Column | paper_pdf_location | |||
| column | New Column | pdf_location | |||
| column | New Column | thermal_pdf_location | |||
| column | New Column | tracking_url | |||
WAREHOUSE_INVENTORY_METRIC | |||||
| column | Primary Key Change | warehouse_product_product_id 🔑 | warehouse_product_product_id | No longer a primary key. | |
Snapchat Ads
We've added a new table, AD_REVIEW_STATUS_REASON, which captures each review status reason for an ad.
We've discontinued support for the review_status_reason column in the AD_HISTORY table. This data is now available in the new AD_REVIEW_STATUS_REASON table.
Talkdesk
We have changed the primary key of the ADVANCED_DIALER_CALL table from interaction_id to _fivetran_id.
The Trade Desk
We have added two new columns, country_short_name and country_long_name, to the ADVERTISER table.
Validio
| Table/column | Change type | Old name | New name | Notes | |
|---|---|---|---|---|---|
VALIDATOR | |||||
| column | Discontinued Column | stats_last_artifact_at | Validio has discontinued the column. | ||
Walmart DSP
We have added two new columns, country_short_name and country_long_name, to the ADVERTISER table.
Workday HCM
We have added the following new tables:
JOB_POSTINGJOB_POSTING_ADDITIONAL_JOB_PROFILEJOB_POSTING_ADDITIONAL_LOCATIONJOB_POSTING_CERTIFICATIONJOB_POSTING_CERTIFICATION_SPECIALTYJOB_POSTING_CERTIFICATION_SUBSPECIALTYJOB_POSTING_COMPETENCYJOB_POSTING_DOCUMENT_FIELDJOB_POSTING_EDUCATIONJOB_POSTING_JOB_FAMILYJOB_POSTING_LANGUAGEJOB_POSTING_LANGUAGE_ABILITYJOB_POSTING_REQUIREMENT_ADDITIONAL_JOB_POSTING_LOCATIONJOB_POSTING_REQUIREMENT_ADDITIONAL_LOCATIONJOB_POSTING_RESPONSIBILITYJOB_POSTING_SIMILAR_JOBJOB_POSTING_SKILLJOB_POSTING_TRAININGJOB_POSTING_WORK_EXPERIENCE
Zoho Books
| Table/column | Change type | Old name | New name | Notes | |
|---|---|---|---|---|---|
JOURNAL_LINE_ITEM | |||||
| table | New Table | JOURNAL_LINE_ITEM | |||
JOURNAL_LINE_ITEM_TAG | |||||
| table | New Table | JOURNAL_LINE_ITEM_TAG | |||
Zoho CRM
We are migrating the Zoho CRM connector from API v2 to API v8. New connections created on or after October 15, 2026, use API v8. We will migrate existing connections in January 2027. The API v8 migration makes the following changes to the Zoho CRM connector schema. To review the complete set of changes, compare your current schema with the upcoming API v8 schema in our Zoho CRM schema information.
New tables
We've added a new table, WORKFLOW. The table contains your workflow rule definitions, including the module each rule applies to and when it runs.
We've added a new table, WORKFLOW_FIELD_UPDATE. The table contains the field update actions that your workflow rules perform.
We now also sync your Zoho CRM linking modules. Each linking module syncs to its own table, named after the module.
Removed columns
API v8 records are synced using Zoho's query API (COQL), which doesn't return Zoho system fields. System fields have API names that start with $. Some columns that come from system fields have the custom_ prefix, for example custom_layout_id, which comes from the $layout_id system field.
If your destination already contains the following columns, we leave them in place but no longer update them. They keep the values from your last API v2 sync, and are NULL in rows we add or update from now on.
The following system field columns are removed from every table that contains them. In custom module and subform tables, these columns are prefixed with an underscore, for example _approval_state:
approval_approveapproval_delegateapproval_rejectapproval_resubmitapproval_stateapprovedcurrency_symboleditablein_mergeorchestrationprocess_flowreview_process_approvereview_process_delegatereview_process_rejectreview_process_resubmit
The following system field columns are also removed. In custom module and subform tables, they are prefixed with an underscore instead of custom_, for example _layout_id:
| System field | Column | Tables |
|---|---|---|
$approval | _approval | Subform tables |
$is_duplicate | custom_is_duplicate | ACCOUNT, CONTACT |
$layout_id | custom_layout_id | Any table that contains the field |
$line_tax | custom_line_tax | INVOICE, PURCHASE_ORDER, QUOTE, SALES_ORDER |
$locked_for_me | custom_locked_for_me | Any table that contains the field |
$state | custom_state | Any table that contains the field |
$zia_owner_assignment | custom_zia_owner_assignment | Any table that contains the field |
The following columns are removed from the specified tables:
| Table | Columns |
|---|---|
CALL | calendar_booking_call, custom_cti_entry |
CASE_MODULE | custom_comments |
DEAL | followed, custom_stage_modified_time |
DEAL_STAGE_HISTORY | duration_days |
EVENT | calendar_booking_event, recurrence_id, send_notification |
NOTE | editable, is_shared_to_client, size, state, voice_note |
PRODUCT | taxable |
PURCHASE_ORDER | state |
ROLE | admin_user |
SALES_ORDER | state |
SOLUTION | custom_comments |
TASK | u_id, custom_best_time |
API v8 doesn't return values for the following columns. The columns remain in your destination, but their values are NULL:
| Table | Columns |
|---|---|
EVENT_PARTICIPANT | invited, status |
LEAD | converted_detail_converted_by |
NOTE | se_module |
TERRITORY | criteria |
New columns
API v8 returns some Zoho fields that API v2 doesn't, so you may see new columns prefixed with custom_, such as custom_change_log_time_s and custom_pipeline in the DEAL table.
| Table | Columns |
|---|---|
ACCOUNT | custom_change_log_time_s |
CALL | custom_scheduled_in_crm |
CONTACT | custom_change_log_time_s |
DEAL | custom_change_log_time_s, custom_pipeline |
EVENT | custom_meeting_venue_s |
EVENT_PARTICIPANT | subordinates |
LEAD | custom_change_log_time_s, custom_enrich_status_s, custom_lead_conversion_time |
ORGANIZATION | created_time, deletable_org_account, hierarchy_preferences_type, hipaa_compliance_enabled, license_details_portal_users_license_purchased, lite_users_enabled, type |
PROFILE | api_name, type |
ROLE | api_name, created_by_email, created_by_id, created_by_name, created_time, modified_by_email, modified_by_id, modified_by_name, modified_time |
TAGS | color_code |
TERRITORY | api_name, permission_type |
USERS | profile_id, profile_name |
| Standard module tables | custom_record_status_s |
| Custom module tables | record_status_s |
| Subform tables | created_by, modified_time, linking_module_<number>_serial_number |
We also now flag deleted records in the NOTE and DEAL_STAGE_HISTORY tables, as we do in most other Zoho CRM tables. Both tables have a new _fivetran_deleted column. When a note or a deal stage history record no longer exists in Zoho, we set _fivetran_deleted to true instead of removing the row from your destination. For notes, we flag deleted records when we re-import the table, for example after a table resync. For deal stage history, we flag the records of deleted deals.
Changed column types
We have changed the type of the custom_reminder column in the CALL table from UTC_DATETIME to NAIVE_DATETIME.
API v8 query limitations
COQL has the following limitations that affect the synced data. For more information, see Zoho's COQL limitations documentation.
- COQL doesn't return system fields, whose API names start with
$. - COQL doesn't return multi-select lookup, file upload, and image upload fields.
- COQL doesn't return the
Commentsfield in the Cases and Solutions modules, theCTI Entryfield in the Calls module, or theStage Modified Timefield in the Deals module. - COQL doesn't return composite Address fields or their Coordinates sub-field. We still sync the individual parts of the address, such as street, city, state, zip, country, latitude, and longitude, each in its own column. We no longer sync the column that held the combined address value or the combined coordinates value.
- COQL doesn't return the Zoho
Distancefield (nearby_distance__s), which Zoho adds automatically to modules that have Coordinates.
Zuora
We no longer sync indirectly related object IDs for the CREDIT_TAXATION_ITEM and CREDIT_MEMO_APPLICATION_ITEM tables. To identify indirect relationships, check the direct-relationship field in the Zuora API response.
You can retrieve these IDs by joining related tables in your destination.
Improvements
Adyen
We no longer sync manually generated reports for the Adyen connector. We identified that syncing these reports caused duplicate records in the destination. The connector continues to sync supported, automatically generated reports for your selected tables.
AI Connector Agent
The AI Connector Agent is now generally available.
Read our AI Connector Agent documentation.
Apple Search Ads
You can now authenticate your Apple Search Ads connections with Sign in with Apple. Instead of inviting an API user and uploading a public key, you sign in with your Apple ID and authorize Fivetran to access your Apple Search Ads account. Existing connections that use an API user continue to work without changes.
For more information, see our Apple Search Ads setup guide.
Auth0
We have changed the connector type of our Auth0 connector from Lite to Standard.
Azure DevOps
We have made the following changes to improve incremental syncs for the COMMIT table:
- We now maintain a separate sync cursor for each repository, which reduces unnecessary re-fetching of historical commits.
- We now send the cursor to Azure DevOps in 24-hour UTC format with an explicit
Ztimezone designator. Previously, the cursor used a 12-hour format without a timezone, which could cause Fivetran to request commits up to 12 hours earlier or later than intended.
BigQuery
The BigQuery connector now supports the Hybrid Deployment model. For more information, see our setup instructions.
BigQuery destination
We now support using Managed Data Lake as the storage layer for BigQuery destinations, allowing you to store your data as Apache Iceberg™ tables in a Fivetran-managed data lake and query those tables using BigQuery. When you set up a new BigQuery destination, you can choose this option instead of native tables. This feature is available for SaaS Deployment only and is currently in beta.
To support this feature, we have added the following fields to the BigQuery destination setup form:
- Table Type: Allows you to select how Fivetran stores the destination data, either in BigQuery native tables or as Iceberg tables in an associated Managed Data Lake destination.
- Storage Configuration: Allows you to select an existing Managed Data Lake destination to use as the storage layer or create a new data lake.
When you store destination data in Iceberg format, Fivetran loads the data into the associated Managed Data Lake destination. After each successful connection sync, Fivetran creates or refreshes external Iceberg tables in BigQuery so that the corresponding tables reflect the latest data.
For more information, see our BigQuery setup guide.
Apache Iceberg is a trademark of the Apache Software Foundation.
Coupa
We now sync custom field values for order line changes and their account allocations to the existing custom_fields columns in the ORDER_LINE_CHANGE and ORDER_LINE_CHANGE_ALLOCATION tables. To populate values for existing records, re-sync the ORDER_HEADER_CHANGE table.
Db2 for LUW
We have released a new version of the Db2 for LUW stored procedures package. The fivetran_get_data_blocks procedure now returns transaction log data in a single, larger buffer, so the procedure has one fewer output parameter. The package includes shared library binaries for Db2 10.5, 11.1, 11.5, and 12.1 on Linux, AIX/Unix, and Windows. Download the updated package from the Downloads page, and create the procedures using the updated statements in our setup guide. Existing installations of the previous stored procedures continue to work.
Facebook Ads
We've upgraded our Facebook Ads connector to version 26.0 of the Facebook API. For more information, see the Meta summary of Graph API v26.0 and Marketing API v26.0.
Gong
We now sync the ENGAGE_FLOW and TASK tables once a day instead of on every sync. This change reduces the number of API calls we make to Gong and helps you stay within Gong's rate limits.
Google Cloud Storage
We now support AI-generated table extraction patterns in the connection setup form for Dynamically extract tables. You can now click Auto-generate to have Fivetran use AI to generate a pattern based on your file paths. Review and adjust the pattern before saving it. For more information, see our setup guide.
Guided Migration to Apache Iceberg™ Tables
You can now use a guided migration experience in the Fivetran dashboard to migrate a connection from a Snowflake destination that uses Native tables to Apache Iceberg tables in a Managed Data Lake destination.
The guided experience walks you through selecting or creating the required Managed Data Lake destination and associated Snowflake destination that uses Iceberg tables, reviewing data type changes, starting the migration, and monitoring its progress.
For more information, see Migrate from Snowflake Native Tables to Apache Iceberg™ Tables.
Apache Iceberg is a trademark of the Apache Software Foundation.
Intercom
We have made the following changes to support Intercom API v2.16:
- Changed the data type of the
admin_idcolumn of theCONTACT_HISTORYtable from LONG to STRING, because the correspondingowner_idAPI field now returns a string. - Updated the
assignee_idandteam_assignee_idcolumns of theCONVERSATION_HISTORYtable to contain0instead ofNULLfor unassigned conversations, matching the values returned by the correspondingadmin_assignee_idandteam_assignee_idAPI fields. - Stopped populating the
parent_idandparent_typecolumns of theARTICLE_HISTORYtable for new data because Intercom removed these fields from the Articles API response.
Navan
We have fixed an issue that caused the credit_exchange_fee_usd column of the BOOKING_CREDIT table to always be NULL. The column now contains the value returned by the source.
Oracle
Active Data Guard standby database support for the Binary Log Reader incremental sync method is now generally available.
We support Active Data Guard standby databases only in read-only mode. However, we still need to connect to the primary database to manage directory objects. For more information about the required settings, see our Binary Log Reader setup instructions.
Oracle Fusion Cloud Applications
We have added a new toggle, Disable Effective Date Filtering, to the connection setup form to support the extraction of historical data without applying any filters for an effective date. You must set the toggle to ON if you want to disable Oracle BICC effective date filtering and include records outside Oracle's default effective date range across all datastores in the connection.
This configuration option is available only for new connections. Be sure to modify your configuration before creating a connection.
QuickBooks
We have fixed an issue that incorrectly deleted records in the TAX_RATE_DETAIL table when either the sales or purchase tax rate list associated with a tax code was empty. By default, we will re-sync the TAX_CODE and TAX_RATE_DETAIL tables to restore these records. This re-sync counts toward free Monthly Active Rows (MAR). We are gradually rolling out this enhancement to all existing connections.
Row filtering support for combining conditions with AND or OR
Row filtering now supports combining multiple conditions using the OR logical operator, in addition to AND. A row passes an OR filter if it matches at least one condition, rather than requiring every condition to match.
All conditions in a filter must use the same logical operator. You can’t combine AND and OR within the same filter.
For more information, see our row filtering documentation.
Salesforce
You can now use JWT Bearer authentication with your Salesforce external client app. This flow uses a private key and a pre-authorized Salesforce integration user without requiring a client secret. For setup instructions, see our Salesforce setup guide.
JWT Bearer authentication is available only if you have access to the External Client App (ECA) flow. To enable the ECA flow for your connection, contact Fivetran Support.
SAP ECC on Oracle
A new version of the Fivetran NetWeaver API is now available for download: v1900338.
- We fixed an issue that prevented the Fivetran NetWeaver API from working on SAP ABAP 7.4 because it used the INT8 data type.
- We improved the performance of the
/FIVETRAN/CONFIGtransaction.
SAP ERP on HANA
A new version of the Fivetran NetWeaver API is now available for download: v1900338.
- We fixed an issue that prevented the Fivetran NetWeaver API from working on SAP ABAP 7.4 because it used the INT8 data type.
- We improved the performance of the
/FIVETRAN/CONFIGtransaction.
SAP OData
We have improved how the connector reports SAP server errors. When the SAP system returns a non-retryable server error (for example, the internal server error described in SAP Note 1797736), the connector now raises an alert in your Fivetran dashboard. The alert includes the SAP error message and SAP Note reference, plus guidance to check transaction /IWFND/ERROR_LOG on the SAP Gateway hub system. Other tables continue syncing, and we raise the alert at the end of the sync.
We have also improved the SAP OData sync failure message. When individual endpoints fail during a sync, the message now includes the failure reason for up to three affected endpoints, instead of only listing the endpoint names.
SFTP
We now support decrypting PGP-encrypted files that use a shared passphrase (symmetric encryption). To configure decryption, select Shared Passphrase (Symmetric) in the PGP decryption method drop-down menu in the connection setup form, then enter the passphrase used to encrypt your files. For more information, see our setup guide.
We now support AI-generated table extraction patterns in the connection setup form for Dynamically extract tables. You can now click Auto-generate to have Fivetran use AI to generate a pattern based on your file paths. Review and adjust the pattern before saving it. For more information, see our setup guide.
Slack
For CHANNEL_MEMBER, we now sync members from all channels to the existing table. Previously, we synced only members from channels where the app is installed.
Snowflake destination
Apache Iceberg™ tables for the Snowflake destination are now generally available.
For more information, see our Snowflake documentation.
Apache Iceberg is a trademark of the Apache Software Foundation.
Splunk
We now support the Hybrid Deployment model for the Splunk connector. Learn more in our Splunk setup guide.
SQL Server
Windows Authentication for SQL Server connections is now generally available. This feature lets you authenticate using a Windows or Active Directory identity through the Windows Authentication Server, a Windows service that runs inside your network.
For setup instructions, see our Generic SQL Server setup guide.
We have fixed an issue in the SQL Server Binary Log Reader that affected hosts running multiple SQL Server instances with Transparent Data Encryption (TDE). Previously, the instances shared a single key container, so they could not each use their own TDE certificate. Each instance now uses its own key container.
To apply this fix, update the Fivetran CLR component to version 1.1.20 on each affected SQL Server instance.
TikTok Organic
We have added a new field, TikTok API rate limit tier, to the connection setup form. The field lets you match the connector's request rate to the rate limit tier TikTok has approved for your developer app (Basic, Advanced, Premium, or Ultimate), so that your syncs can run faster if your app has a higher tier.
The field defaults to Basic, so existing connections continue to sync at the same rate. Select a higher tier only if TikTok has approved your app for it. If you select a tier that your app has not been granted, your syncs may fail with rate-limit errors.
We have also added a new parameter, api_rate_limit_tier, to the Fivetran REST API.
Xero
We have updated the sync strategy for the ALLOCATION table to improve data accuracy and consistency. We now capture deletes for the ALLOCATION table when allocations are removed from the CREDIT_NOTE, OVERPAYMENT, or PREPAYMENT tables. To support this enhancement, we have made the following schema changes:
- Changed the primary key from a combination of
allocation_idandindexcolumns tocredit_note_id,overpayment_id,prepayment_id, andindexcolumns in theALLOCATIONtable. - Removed the
allocation_idcolumn from theALLOCATIONtable.
Be sure to update your downstream queries to reflect these changes. We are gradually rolling out these enhancements to all existing connections.
REST API Improvements
Connector SDK Package ID Removed from Connection Details
The connector_sdk_package_id field is no longer returned by the Retrieve Connection Details endpoint.
Use config.package_id instead. It contains the same package ID, and it is also the field you use to set the package when you create or update a Connector SDK connection.
Log Service Metadata REST API
We added two REST API endpoints that describe the log service types you can create and the configuration each one accepts:
- Retrieve Log Service Types (
GET /v1/metadata/log-service-types) returns a paginated list of the log service types you can create, with their name, description, icons, documentation link, and availability status. - Retrieve Log Service Type Metadata (
GET /v1/metadata/log-service-types/{service}) returns the details of one log service type, including aconfigobject that describes its configuration fields. For each field, the object shows its data type, its allowed values, and whether the field is read-only, immutable, or nullable. Fields that hold secrets, such as API keys, are marked with"format": "password".
Use these endpoints to find out which fields a log service type accepts before you add a group log service or add an account log service. You can also use them to build or validate log service configuration in your tooling instead of hard-coding the fields for each service.
You don't need to change anything in your existing integrations.
Modify Destination Schema Names Before the Initial Sync
The Update a Connection endpoint now accepts the destination_schema_names parameter. Previously, the endpoint ignored this parameter, so you could change the setting only in the dashboard.
You can set destination_schema_names to FIVETRAN_NAMING or SOURCE_NAMING only before the connection's initial sync. After the initial sync starts, you can only send the value that's already set. Attempting to change it returns an error.
Retrieve Connection Errors REST API Endpoint
We added a new REST API endpoint, Retrieve Connection Errors (GET /v1/connections/{connectionId}/errors), that returns all active errors for a connection. Each error corresponds to a task type currently active for the connection and includes a machine-readable type, a human-readable title, a short reason summary, a plain-text message with remediation guidance, and the created_at timestamp of the most recent occurrence. The response is paginated with the cursor and limit query parameters. If no errors are currently active, the endpoint returns an empty items array.