October 2025
Connector SDK
fivetran-connector-sdk PyPI package
We have released version 2.3.1 of the fivetran-connector-sdk PyPI package. This release adds the following:
- Previously, list objects required an explicit type definition within the
schema()method. This release removes that limitation. Now, we automatically infer thelisttype values toJSON. - Minor improvements and enhancements.
We have released version 2.3.0 of the fivetran-connector-sdk PyPI package. This release adds the following:
- Timeout handling for connector operations.
- Minor improvements and enhancements.
Fivetran Connector SDK
The latest sync log events are now displayed at the top of the list on the Connector SDK Logs tab of the Connection Details page in the dashboard.
Lite Connectors
Lite connectors are now available for the following sources:
Logs
Extract Summary Event Now Includes SQL Query Count
The extract_summary log event for database connectors now includes SQL query count information, in addition to the API call count for API-based connectors. We are gradually rolling out this change to all existing connections.
See our extract_summary event documentation for more details.
Referencing users by ID instead of email address
We now reference users by unique ID instead of email address to improve data security. We updated the relevant BigQuery and Snowflake sample queries that join the LOG and USER tables.
Splunk Logging
We've updated the following field names in log messages we send to Splunk:
connector_idhas been renamed toconnection_idconnector_namehas been renamed toconnection_name
Partner SDK
SingleStore destination is in beta
The SingleStore destination is now in beta. For more information, see the Singlestore destination documentation.
Transformations for dbt Core
Fivetran data model consolidation
We unified each connector’s pre-built dbt Core*–compatible data models into a single model. It standardizes and documents the Fivetran schemas created in your destination and outputs analytics-ready tables. Previously, most connectors used distinct source and transform models.
* dbt Core is a trademark of dbt Labs, Inc. All rights therein are reserved to dbt Labs, Inc. Fivetran Transformations is not a product or service of or endorsed by dbt Labs, Inc.
Schema changes
Adobe Workfront
| Table/column | Change type | Old name | New name | Notes | |
|---|---|---|---|---|---|
TASK_CUSTOM_VALUE | |||||
| table | New Table | TASK_CUSTOM_VALUE | |||
Amazon Selling Partner
We have added the MARKETPLACE_PARTICIPATION table.
We are gradually rolling out this change to all connections.
Azure DevOps
We have added the following new tables:
INSTALLED_EXTENSION_CONTRIBUTION_AUTHENTICATION_SCHEMAINSTALLED_EXTENSION_CONTRIBUTION_CONSTRAINTINSTALLED_EXTENSION_CONTRIBUTION_RESTRICTEDINSTALLED_EXTENSION_CONTRIBUTION_TARGETINSTALLED_EXTENSION_CONTRIBUTION_TYPEINSTALLED_EXTENSION_CONTRIBUTIONINSTALLED_EXTENSION_FILEINSTALLED_EXTENSION_SCOPEINSTALLED_EXTENSIONPROCESS_WORK_ITEM_TYPE_STATEPROCESS_WORK_ITEM_TYPEPROCESSWORK_ITEM_RELATION
We have added the following new columns to the USERS table:
access_level_account_license_typeaccess_level_assignment_sourceaccess_level_git_hub_license_typeaccess_level_license_display_nameaccess_level_licensing_sourceaccess_level_msdn_license_typeaccess_level_status_messageaccess_level_status
Braze
We've added a new column, preheader, to the MESSAGE_VARIATION table. We've also added a new table, USER_PUSH_TOKEN.
CallRail
| Table/column | Change type | Old name | New name | Notes | |
|---|---|---|---|---|---|
CALL | |||||
| column | New Column | campaign | |||
| column | New Column | company_id | |||
| column | New Column | created_at | |||
| column | New Column | custom_* | |||
| column | New Column | device_type | |||
| column | New Column | first_call | |||
| column | New Column | first_touch_ad_position | |||
| column | New Column | first_touch_campaign | |||
| column | New Column | first_touch_device | |||
| column | New Column | first_touch_event_date | |||
| column | New Column | first_touch_keywords | |||
| column | New Column | first_touch_landing | |||
| column | New Column | first_touch_landing_page_url_params | |||
| column | New Column | first_touch_match_type | |||
| column | New Column | first_touch_medium | |||
| column | New Column | first_touch_referrer | |||
| column | New Column | first_touch_referrer_url_params | |||
| column | New Column | first_touch_session_browser | |||
| column | New Column | first_touch_source | |||
| column | New Column | first_touch_url_utm_params | |||
| column | New Column | formatted_business_phone_number | |||
| column | New Column | formatted_call_type | |||
| column | New Column | formatted_customer_location | |||
| column | New Column | formatted_customer_name | |||
| column | New Column | formatted_customer_name_or_phone_number | |||
| column | New Column | formatted_customer_phone_number | |||
| column | New Column | formatted_duration | |||
| column | New Column | formatted_tracking_phone_number | |||
| column | New Column | formatted_tracking_source | |||
| column | New Column | formatted_value | |||
| column | New Column | ga | |||
| column | New Column | good_lead_call_id | |||
| column | New Column | good_lead_call_time | |||
| column | New Column | highlights | |||
| column | New Column | keypad_entry_* | |||
| column | New Column | keywords | |||
| column | New Column | keywords_spotted | |||
| column | New Column | landing_page_url | |||
| column | New Column | last_requested_url | |||
| column | New Column | last_touch_ad_position | |||
| column | New Column | last_touch_campaign | |||
| column | New Column | last_touch_device | |||
| column | New Column | last_touch_event_date | |||
| column | New Column | last_touch_keywords | |||
| column | New Column | last_touch_landing | |||
| column | New Column | last_touch_landing_page_url_params | |||
| column | New Column | last_touch_match_type | |||
| column | New Column | last_touch_medium | |||
| column | New Column | last_touch_referrer | |||
| column | New Column | last_touch_referrer_url_params | |||
| column | New Column | last_touch_session_browser | |||
| column | New Column | last_touch_source | |||
| column | New Column | last_touch_url_utm_params | |||
| column | New Column | lead_created_ad_position | |||
| column | New Column | lead_created_campaign | |||
| column | New Column | lead_created_device | |||
| column | New Column | lead_created_event_date | |||
| column | New Column | lead_created_keywords | |||
| column | New Column | lead_created_landing | |||
| column | New Column | lead_created_landing_page_url_params | |||
| column | New Column | lead_created_match_type | |||
| column | New Column | lead_created_medium | |||
| column | New Column | lead_created_referrer | |||
| column | New Column | lead_created_referrer_url_params | |||
| column | New Column | lead_created_session_browser | |||
| column | New Column | lead_created_source | |||
| column | New Column | lead_created_url_utm_params | |||
| column | New Column | lead_status | |||
| column | New Column | medium | |||
| column | New Column | note | |||
| column | New Column | person_id | |||
| column | New Column | prior_calls | |||
| column | New Column | qualified_ad_position | |||
| column | New Column | qualified_campaign | |||
| column | New Column | qualified_device | |||
| column | New Column | qualified_event_date | |||
| column | New Column | qualified_keywords | |||
| column | New Column | qualified_landing | |||
| column | New Column | qualified_landing_page_url_params | |||
| column | New Column | qualified_match_type | |||
| column | New Column | qualified_medium | |||
| column | New Column | qualified_referrer | |||
| column | New Column | qualified_referrer_url_params | |||
| column | New Column | qualified_session_browser | |||
| column | New Column | qualified_source | |||
| column | New Column | qualified_url_utm_params | |||
| column | New Column | referrer_domain | |||
| column | New Column | referring_url | |||
| column | New Column | sentiment | |||
| column | New Column | session_uuid | |||
| column | New Column | source | |||
| column | New Column | source_name | |||
| column | New Column | speaker_percent_agent | |||
| column | New Column | speaker_percent_customer | |||
| column | New Column | summary | |||
| column | New Column | tags | |||
| column | New Column | timeline_url | |||
| column | New Column | total_calls | |||
| column | New Column | tracker_id | |||
| column | New Column | transcription | |||
| column | New Column | type | |||
| column | New Column | utm_campaign | |||
| column | New Column | utm_content | |||
| column | New Column | utm_medium | |||
| column | New Column | utm_source | |||
| column | New Column | utm_term | |||
| column | New Column | value | |||
| column | New Column | voice_assist_message | |||
| column | New Column | zip_code | |||
Centra
| Table/column | Change type | Old name | New name | Notes | |
|---|---|---|---|---|---|
RETURN | |||||
| column | Discontinued Column | status | |||
Cin7 Core
| Table/column | Change type | Old name | New name | Notes | |
|---|---|---|---|---|---|
SALE | |||||
| column | New Column | customer_reference | |||
Cloudflare Analytics
| Table/column | Change type | Old name | New name | Notes | |
|---|---|---|---|---|---|
REQUEST_GROUP | |||||
| column | Primary Key Change | client_country_name | client_country_name 🔑 | Added to primary key. | |
| column | Discontinued Column | index 🔑 | No longer a primary key. | ||
Coupa
We have added a new column, kind, to the PURPOSE table.
We have added the following new columns to the SUPPLIER_INFORMATION_ADDRESS table:
account_type_itemaddress_namebank_account_numberbank_addressbank_citybank_codebank_fax_phone_area_codebank_fax_phone_country_codebank_fax_phone_extensionbank_fax_phone_idbank_fax_phone_numberbank_postal_codebank_routing_numberbank_state_regionbank_work_phone_area_codebank_work_phone_country_codebank_work_phone_extensionbank_work_phone_idbank_work_phone_numberbank_country_idbicbic_routing_codebsb_numbercsp_rta_idcustom_field_1custom_field_2custom_field_3custom_field_4custom_field_5custom_field_6custom_field_7custom_field_8custom_field_9custom_field_10custom_field_11custom_field_12custom_field_13custom_field_14custom_field_15custom_field_16custom_field_17custom_field_18custom_field_19custom_field_20emailiban_numberifscintermediary_bank_nameinternational_bank_account_numberkindname_on_bank_accountpayment_method_itempo_boxpo_box_postal_codesort_codestate_regionstreet_addressstreet_address2street_address3street_address4supplier_information_idswift_codetransit_number_and_institution_numbervirtual_card_emailwire_routing_number
We have discontinued the following columns from the SUPPLIER_INFORMATION_ADDRESS table:
attentionbusiness_group_namecustom_fieldsexternal_src_nameexternal_src_reflocal_tax_numbernamestatestreet_1street_2street_3street_4vat_country_idvat_number
Customer.io
We have added the transactional_message_id column to the EMAIL_EVENT table.
We have added the following new columns to the MESSAGE table:
metrics_human_clickedmetrics_human_openedmetrics_prefetch_clickedmetrics_prefetch_opened
Delighted
We have added a new table unsubscribed_people.
Dialpad
| Table/column | Change type | Old name | New name | Notes | |
|---|---|---|---|---|---|
CALL_TRANSCRIPT | |||||
| table | New Table | CALL_TRANSCRIPT | |||
Eventbrite
| Table/column | Change type | Old name | New name | Notes | |
|---|---|---|---|---|---|
EVENT_TEAM | |||||
| table | Discontinued Table | EVENT_TEAM | |||
EVENT_TEAM_CREATOR_EMAIL | |||||
| table | Discontinued Table | EVENT_TEAM_CREATOR_EMAIL | |||
STRUCTURE_CONTENT_PUBLISHED | |||||
| table | Discontinued Table | STRUCTURE_CONTENT_PUBLISHED | |||
STRUCTURE_CONTENT_PUBLISHED_MODULE | |||||
| table | Discontinued Table | STRUCTURE_CONTENT_PUBLISHED_MODULE | |||
STRUCTURE_CONTENT_PUBLISHED_WIDGET_TAB | |||||
| table | Discontinued Table | STRUCTURE_CONTENT_PUBLISHED_WIDGET_TAB | |||
STRUCTURE_CONTENT_PUBLISHED_WIDGET_TAB_SLOT | |||||
| table | Discontinued Table | STRUCTURE_CONTENT_PUBLISHED_WIDGET_TAB_SLOT | |||
STRUCTURE_CONTENT_PUBLISHED_WIDGET_TAB_SLOT_HOST | |||||
| table | Discontinued Table | STRUCTURE_CONTENT_PUBLISHED_WIDGET_TAB_SLOT_HOST | |||
Freshservice
We have added support for custom fields in the TICKET_ITEM table. You can now sync additional metadata.
The custom fields appear with the custom_ prefix in your destination. For example, custom_priority_level and custom_approval_required.
Google Analytics 4 Export
We have added the following columns to the EVENT table:
session_traffic_source_last_click.sa360_campaign.*session_traffic_source_last_click.cm360_campaign.*session_traffic_source_last_click.dv360_campaign.*session_traffic_source_last_click.cross_channel_campaign.default_channel_groupsession_traffic_source_last_click.cross_channel_campaign.primary_channel_group
To backfill the historical data for these columns, re-sync the connection or contact Fivetran Support to re-sync it for you.
Google Display & Video 360
The previously announced Google Display & Video 360 API deprecations changed on the source side:
- The deprecation of the
Insertion Order ID(FILTER_INSERTION_ORDER)dimension is reverted - The
Insertion Order [FILTER_YOUTUBE_PROGRAMMATIC_GUARANTEED_INSERTION_ORDER](FILTER_YOUTUBE_PROGRAMMATIC_GUARANTEED_INSERTION_ORDER)dimension is deprecated
Greenhouse
We have added the following new tables:
APPLICATION_ATTACHMENTAPPROVALAPPROVERAPPROVER_GROUPHIRING_TEAM_STATUS
We have added the following new columns to the APPLICATION table:
recruiter_idcoordinator_idcustom_fieldscurrent_stage_nameprospective_departmenprospective_office
We have added two new columns, opening_id and values, to the OFFER table.
We have added the following new columns to the JOB_POST table:
activedemographic_question_set_idfirst_published_atjob_post_custom_location_idjob_post_location_type_idjob_post_location_type_namelocation_office_id
Intercom
We have added the email_message_metadata_subject column to the CONVERSATION_PART_HISTORY table.
We have added the child tables CONVERSATION_PART_TAG_HISTORY and EMAIL_ADDRESS_HEADER to the CONVERSATION_PART_HISTORY table.
We have added the following new columns to the CONVERSATION_PART_HISTORY table:
app_package_codeevent_details_action_nameevent_details_action_resultevent_details_attribute_nameevent_details_event_resultevent_details_event_typeevent_details_value_nameevent_details_workflow_namestate
We have added the following new tables:
RECEIPT_RESPONSESURVEY_ANSWERSURVEY_QUESTION
We are gradually rolling out this change to all existing connections.
Kustomer
We have made the following schema changes:
Added a new table,
WORK_SESSION, which contains work session information for agents, including capacity status, handled item counts, availability metrics, and time-tracking statistics.We incrementally sync the
WORK_SESSIONtable and its child tables to capture new records.
Lob
| Table/column | Change type | Old name | New name | Notes | |
|---|---|---|---|---|---|
CAMPAIGN | |||||
| table | New Table | CAMPAIGN | |||
CAMPAIGN_CREATIVE | |||||
| table | New Table | CAMPAIGN_CREATIVE | |||
CAMPAIGN_CREATIVE_TEMPLATE_PREVIEW | |||||
| table | New Table | CAMPAIGN_CREATIVE_TEMPLATE_PREVIEW | |||
CAMPAIGN_UPLOAD | |||||
| table | New Table | CAMPAIGN_UPLOAD | |||
POSTCARD | |||||
| column | New Column | completed_at | |||
| column | New Column | fsc | |||
| column | New Column | is_creative_proof | |||
| column | New Column | is_dashboard | |||
| column | New Column | lob_credits_funding_status | |||
| column | New Column | qr_code | |||
| column | New Column | raw_url | |||
| column | New Column | status | |||
| column | New Column | to_be_expunged_date | |||
| column | New Column | url | |||
| column | New Column | use_type | |||
| column | New Column | usps_campaign_id | |||
Okta
We have added two new tables, USER_ENROLLED_FACTOR and USER_AUTHENTICATOR_ENROLLMENT. We are gradually rolling out this change to all connections.
PostHog
| Table/column | Change type | Old name | New name | Notes | |
|---|---|---|---|---|---|
DATA_ATTRIBUTE | |||||
| table | Discontinued Table | DATA_ATTRIBUTE | Data is available in the PROJECT table. | ||
PROJECT | |||||
| column | New Column | data_attribute | |||
Salesforce Commerce Cloud
We have added a new column, customer_is_guest, to the ORDERS_HISTORY table. Be sure to re-sync the ORDERS_HISTORY table to backfill the data for the new column.
SAP Concur
We have added a new column, USER_ID, to the USER table. The column contains the unique identifier for each user in SAP Concur.
We have added the following new tables:
REPORT_APPROVERSPEND_USERSPEND_USER_AUTHORIZED_APPROVERSPEND_USER_CUSTOM_DATASPEND_USER_EXPENSE_DELEGATESPEND_USER_ROLE
We are gradually rolling out this change to all existing connections.
SmartRecruiters
| Table/column | Change type | Old name | New name | Notes | |
|---|---|---|---|---|---|
CANDIDATE | |||||
| column | New Column | tags | |||
CANDIDATE_EDUCATION | |||||
| column | Discontinued Column | index 🔑 | No longer a primary key. | ||
| column | Primary Key Change | _fivetran_id 🔑 | New primary key. | ||
CANDIDATE_EXPERIENCE | |||||
| column | Discontinued Column | index 🔑 | No longer a primary key. | ||
| column | Primary Key Change | _fivetran_id 🔑 | New primary key. | ||
CANDIDATE_TAG | |||||
| table | Discontinued Table | CANDIDATE_TAG | |||
Snapchat Ads
We've added the following columns to the TARGETING_GEOLOCATION_HISTORY table:
geo_typegeo_valuefivetran_id
We've also discontinued support for the index column in the TARGETING_GEOLOCATION_HISTORY table.
Stripe
We've added below fields in the QUOTE table:
subscription_data_billing_mode_flexible_proration_discountssubscription_data_billing_mode_typesubscription_data_descriptionsubscription_data_effective_datesubscription_data_metadatasubscription_data_trial_period_days
Transcend
| Table/column | Change type | Old name | New name | Notes | |
|---|---|---|---|---|---|
ASSESSMENT_FILE | |||||
| table | Discontinued Table | ASSESSMENT_FILE | |||
Validio
| Table/column | Change type | Old name | New name | Notes | |
|---|---|---|---|---|---|
SOURCE_CATALOG_ASSET | |||||
| column | Discontinued Column | query_user | |||
| column | Discontinued Column | stats_utilization | |||
SOURCE_CATALOG_ASSET_JOINED_TABLE | |||||
| table | Discontinued Table | SOURCE_CATALOG_ASSET_JOINED_TABLE | |||
VALIDATOR | |||||
| column | Discontinued Column | config_minimum_reference_data_point | |||
| column | Discontinued Column | config_minimum_relative_difference_percent | |||
| column | Discontinued Column | config_mininum_absolute_difference | |||
| column | Discontinued Column | config_reference_source_field | |||
| column | Discontinued Column | config_sensitivity | |||
Walmart Marketplace
| Table/column | Change type | Old name | New name | Notes | |
|---|---|---|---|---|---|
INCENTIVE_ITEM | |||||
| table | Discontinued Table | INCENTIVE_ITEM | |||
PRICE_INCENTIVE | |||||
| table | New Table | PRICE_INCENTIVE | |||
PRO_SELLER_BADGE_STATUS | |||||
| table | Discontinued Table | PRO_SELLER_BADGE_STATUS | |||
Workday Financial Management
We have added a new column country_alpha_2_code to the BUSINESS_ENTITY_ADDRESS table. Be sure to re-sync the table to backfill the historical data or reach out to Fivetran Support to re-sync it for you.
Workday HCM
We have added a new column country_alpha_2_code to the ADDRESS table. Be sure to re-sync the table to backfill the historical data or reach out to Fivetran Support to re-sync it for you.
Improvements
Amazon Selling Partner
We’re updating the sync frequency to once a day for the following reports in the Amazon Selling Partner connector.
CUSTOMER_SHIPMENT_SALES_REPORTFULFILLMENT_CUSTOMER_SHIPMENT_PROMOTION_REPORTLONG_TERM_STORAGE_FEE_CHARGES_REPORTMARKET_BASKET_ANALYSIS_REPORT_MONTHLYMARKET_BASKET_ANALYSIS_REPORT_QUARTERLYNET_PURE_PRODUCT_MARGIN_REPORT_MONTHLYNET_PURE_PRODUCT_MARGIN_REPORT_QUARTERLYORDERS_REPORTREIMBURSEMENTS_REPORTREPEAT_PURCHASE_REPORT_MONTHLYREPEAT_PURCHASE_REPORT_QUARTERLYSALES_AND_TRAFFIC_BUSINESS_CHILD_ASIN_REPORT_MONTHLYSALES_AND_TRAFFIC_BUSINESS_PARENT_ASIN_REPORT_MONTHLYSALES_AND_TRAFFIC_BUSINESS_REPORT_MONTHLYSALES_AND_TRAFFIC_BUSINESS_SKU_REPORT_MONTHLYSEARCH_TERMS_REPORT_MONTHLYSEARCH_TERMS_REPORT_QUARTERLYVENDOR_INVENTORY_MANUFACTURING_FRESH_ASIN_REPORT_MONTHLYVENDOR_INVENTORY_MANUFACTURING_FRESH_ASIN_REPORT_QUARTERLYVENDOR_INVENTORY_MANUFACTURING_FRESH_REPORT_MONTHLYVENDOR_INVENTORY_MANUFACTURING_FRESH_REPORT_QUARTERLYVENDOR_INVENTORY_MANUFACTURING_RETAIL_ASIN_REPORT_MONTHLYVENDOR_INVENTORY_MANUFACTURING_RETAIL_ASIN_REPORT_QUARTERLYVENDOR_INVENTORY_MANUFACTURING_RETAIL_REPORT_MONTHLYVENDOR_INVENTORY_MANUFACTURING_RETAIL_REPORT_QUARTERLYVENDOR_INVENTORY_SOURCING_FRESH_ASIN_REPORT_MONTHLYVENDOR_INVENTORY_SOURCING_FRESH_ASIN_REPORT_QUARTERLYVENDOR_INVENTORY_SOURCING_FRESH_REPORT_MONTHLYVENDOR_INVENTORY_SOURCING_FRESH_REPORT_QUARTERLYVENDOR_INVENTORY_SOURCING_RETAIL_ASIN_REPORT_MONTHLYVENDOR_INVENTORY_SOURCING_RETAIL_ASIN_REPORT_QUARTERLYVENDOR_INVENTORY_SOURCING_RETAIL_REPORT_MONTHLYVENDOR_INVENTORY_SOURCING_RETAIL_REPORT_QUARTERLYVENDOR_SALES_MANUFACTURING_BUSINESS_ASIN_REPORT_MONTHLYVENDOR_SALES_MANUFACTURING_BUSINESS_ASIN_REPORT_QUARTERLYVENDOR_SALES_MANUFACTURING_BUSINESS_REPORT_MONTHLYVENDOR_SALES_MANUFACTURING_BUSINESS_REPORT_QUARTERLYVENDOR_SALES_MANUFACTURING_FRESH_ASIN_REPORT_MONTHLYVENDOR_SALES_MANUFACTURING_FRESH_ASIN_REPORT_QUARTERLYVENDOR_SALES_MANUFACTURING_FRESH_REPORT_MONTHLYVENDOR_SALES_MANUFACTURING_FRESH_REPORT_QUARTERLYVENDOR_SALES_MANUFACTURING_RETAIL_ASIN_REPORT_MONTHLYVENDOR_SALES_MANUFACTURING_RETAIL_ASIN_REPORT_QUARTERLYVENDOR_SALES_MANUFACTURING_RETAIL_REPORT_MONTHLYVENDOR_SALES_MANUFACTURING_RETAIL_REPORT_QUARTERLYVENDOR_SALES_SOURCING_BUSINESS_ASIN_REPORT_MONTHLYVENDOR_SALES_SOURCING_BUSINESS_ASIN_REPORT_QUARTERLYVENDOR_SALES_SOURCING_BUSINESS_REPORT_MONTHLYVENDOR_SALES_SOURCING_BUSINESS_REPORT_QUARTERLYVENDOR_SALES_SOURCING_FRESH_ASIN_REPORT_MONTHLYVENDOR_SALES_SOURCING_FRESH_ASIN_REPORT_QUARTERLYVENDOR_SALES_SOURCING_FRESH_REPORT_MONTHLYVENDOR_SALES_SOURCING_FRESH_REPORT_QUARTERLYVENDOR_SALES_SOURCING_RETAIL_ASIN_REPORT_MONTHLYVENDOR_SALES_SOURCING_RETAIL_ASIN_REPORT_QUARTERLYVENDOR_SALES_SOURCING_RETAIL_REPORT_MONTHLYVENDOR_SALES_SOURCING_RETAIL_REPORT_QUARTERLYVENDOR_TRAFFIC_REPORT_MONTHLYVENDOR_TRAFFIC_REPORT_QUARTERLY
Azure Devops
We’ve made the following improvements to prevent data integrity issues:
Improved how the list_work_item temp table filters work items to ensure cleaner and more efficient syncs. Project ID and team ID filters are now applied in the query body instead of the path parameters. This change eliminates duplicate work_item_ids that were appearing in some syncs.
Added incremental sync support so that only new or updated work items are fetched during subsequent syncs.
Centra
We now re-import the PRODUCT table daily to capture updates and deletes.
Criteo Retail Media
We now retain data in the REPORT_CAMPAIGN and REPORT_LINE_ITEM tables for up to 3 years.
Databricks destination
You can now disable the VACUUM operations that Fivetran automatically runs on your destination tables. To support this enhancement, we have added a new toggle, Disable VACUUM operations, to the destination setup form.
Gong
We have changed the sync strategy for the call and transcript tables. The weekly re-import process has been removed.
Google Analytics 4 Export
We have added a new option, Intraday Export Type, to the connection setup form for the connections created on or after July 24, 2023. You can now select one of the following export types:
- Streaming - Sync a continuous export of events
- Fresh Daily - Sync periodic batch updates
- Daily Only (skip intraday events) - Sync only the full export of data that takes place daily
For more information, see our setup instructions and REST API config.
GRIN
We have fixed a bug that prevented us from syncing outstanding jobs data into the PARTNERSHIP_JOB table. Now, we correctly sync outstanding jobs data into this table.
Managed Data Lake Service
You can now modify the Snapshot Retention Period field in the setup form at any time for your Managed Data Lake destinations.
Microsoft Lists
We have added a new authentication method for our Microsoft List connector. You can now use a custom authentication method to connect your Microsoft list account with Fivetran. To support these features, we have made the following changes to the connection setup form:
- Added Authentication method field, that allows you to select between a Quick Setup (Default) and an Advanced Setup.
- Added Client ID, Client secret, Tenant Id and Site Id fields, allowing you to provide your own app credentials.
- Added a Run connection test button to validate the connection credentials.
For more information, see our setup instructions and REST API configuration. We are gradually rolling out these changes to all existing connections.
PostgreSQL "money" type improvement
We now support precision and scale for the money data type.
PostgreSQL source
We now handle JSON columns with duplicate keys by retaining only the last key’s value when writing to a PostgreSQL destination. Previously, such columns were populated with an error message if duplicate keys were detected.
Row Filtering supported for incremental syncs
We now support row filtering for incremental syncs. The filters are applied starting from the next sync after the filters are created.
Previously, we supported row filtering for initial syncs and re-syncs only.
For more information, see our row filtering documentation.
SAP ERP on HANA
A new version of the Fivetran NetWeaver API is now available for download: v1900284.
We added support for Netweaver 7.4.
SharePoint
Effective October 14, 2025, new SharePoint connections will support files with identical names located in different folders. To enable this enhancement, the connector will update the behavior of the _file column. Instead of including only the file name, the _file column will now store the full file path to uniquely identify files.
This change applies only to new SharePoint connections created after October 14, 2025. Existing connections will continue to work as they do today and will not be impacted by this update.
Shopify
We have added a new authentication method, Custom App to the setup form. You can now create and authorize a custom Shopify app directly from your Shopify admin to connect with Fivetran. For more information, see our setup guide.
Unicommerce
We now sync the sale_order entity data based on the facility code you provide in the connection setup form.
Workday Adaptive Planning
Our Workday Adaptive Planning connector is now available in BETA.
Read our Workday Adaptive Planning connector documentation.
Zendesk Support
The Zendesk Support connector now supports the Hybrid Deployment model. For more information, see our setup instructions.
Hybrid Deployment does not support the following webhook tables:
AGENT_CHANNEL_HISTORYAGENT_MAX_CAPACITY_HISTORYAGENT_STATUS_HISTORYAGENT_UNIFIED_STATUS_HISTORY