November 2026
Connector SDK
Fivetran Connector SDK
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.
fivetran-connector-sdk PyPI package
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.
Schema changes
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 | |||
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 |
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 | |||
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 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 removed the review_status_reason column from 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.
Improvements
AI Connector Agent
The AI Connector Agent is now generally available.
Read our AI Connector Agent documentation.
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 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.
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.
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.
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.
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.
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.
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.
REST API Improvements
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.