July 2025

Connector SDK

fivetran-connector-sdk PyPI package

We have released version 1.7.3 of the fivetran-connector-sdk PyPI package. This release adds the following:

• Internal enhancements and design improvements.

We have released version 1.7.2 of the fivetran-connector-sdk PyPI package. This release adds the following:

• Bugfix for requirements.txt validation.
• Minor improvements and enhancements.

We have released version 1.7.1 of the fivetran-connector-sdk PyPI package. This release adds the following:

• Internal enhancements and design improvements.
• Updated tester.

We have released version 1.7.0 of the fivetran-connector-sdk PyPI package. This release adds the following:

• Deploy flow improvements.
• Support for new environment variables.
• Upgraded requests library dependency to 2.32.4.
• Minor bug fixes and improvements.

Lite Connectors

Lite connectors are now available for the following sources:

• Acumatica
• Yotpo
• Fortnox

Managed Data Lakes Service

The Google Cloud Storage (GCS) storage configuration option for our Managed Data Lakes Service is now generally available.

Read our Managed Data Lakes Service documentation.

Fivetran Iceberg REST Catalog now supports the following query engines to query data stored in the Iceberg tables:

• Apache Spark
• Starburst
• Trino

Transformations for dbt Core

dbt Core versions 1.7.19, 1.8.9 and 1.10.3 support

We now support dbt Core* versions 1.7.19, 1.8.9 and 1.10.3. You can use these versions to run your projects.

* 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.

Updated dbt Quickstart packages

We have updated the Quickstart packages for the following connectors:

• Connectors supporting the Ad Reporting data model to version 1.16.0.
• Fivetran Platform to version 2.2.2.
• GitHub to version 0.9.1.
• HubSpot to version 0.25.0.
• Iterable to version 0.14.0.
• Microsoft Dynamics 365 CRM to version 0.1.0-b2.
• Recharge to version 0.5.0.
• Reddit Ads to version 0.6.0.
• Zendesk Support to version 0.24.2.

New connectors

PayPal Sandbox

PayPal sandbox is a virtual testing environment that simulates the PayPal production environment. Read our PayPal connector documentation.

Schema changes

Aha!

Amazon Selling Partner

We have added new tables facilitating vendor sales & inventory reports to have asin granularity. The following tables have been added and are available in multiple granularity (DAILY, MONTHLY, QUARTERLY):

• VENDOR_SALES_SOURCING_RETAIL_ASIN_REPORT_*
• VENDOR_SALES_SOURCING_BUSINESS_ASIN_REPORT_*
• VENDOR_SALES_SOURCING_FRESH_ASIN_REPORT_*
• VENDOR_INVENTORY_MANUFACTURING_FRESH_ASIN_REPORT_*
• VENDOR_INVENTORY_MANUFACTURING_RETAIL_ASIN_REPORT_*
• VENDOR_INVENTORY_SOURCING_FRESH_ASIN_REPORT_*
• VENDOR_INVENTORY_SOURCING_RETAIL_ASIN_REPORT_*
• VENDOR_SALES_MANUFACTURING_FRESH_ASIN_REPORT_*
• VENDOR_SALES_MANUFACTURING_BUSINESS_ASIN_REPORT_*
• VENDOR_SALES_MANUFACTURING_RETAIL_ASIN_REPORT_*

We will gradually rolling out this change to all connections.

Branch

We have added a new column, last_attributed_touch_data_touch_subtype, to the LAST_ATTRIBUTED_TOUCH_DATA events table.

Coupa

We've fixed a data consistency issue in the EASY_FORM_DATA table where the subject column had inconsistent null value representations. The subject column now consistently uses proper SQL NULL values. Previously, some records returned a true SQL NULL while others returned the text string null, which could cause data processing errors and affect analytics quality.

Re-sync the EASY_FORM_DATA table to fix historical data with inconsistent null value representations. The first re-sync will count towards free MAR.

We have added the following columns to the PROJECT table:

• additional_negotiated_savings'
• additional_planned_savings
• additional_realized_savings
• allow_users_to_view_member
• completion_percentage
• copy_project_id
• enabled_tabs
• external_reference_number
• project_id
• show_contracts_rollup_fields
• show_sourcing_rollup_fields
• show_suppliers_rollup_fields
• status
• template_group

We now sync TAGGING data from the PROJECT table.

We have added the following columns to the CHARGE table:

• accounting_currency
• accounting_total
• document_id
• document_type
• expense_holding_account
• legal_entity_name
• posting_date
• holding_account
• issuer_reconciliation_id
• payment_partner

We now sync TAX_LINE data from the CHARGE table. We have added a column charge_id to the TAX_LINE table.

Docebo

Forethought

GitHub

We have added a new table, REPOSITORY_PROPERTY. We are gradually rolling out this change to all existing connections.

We've added the state_reason column to the ISSUE table. This column captures the reason why an issue was closed, providing more context about issue resolution.

Greenhouse

HubSpot

We have added two new tables COMPANY_LIST and COMPANY_LIST_MEMBER to our HubSpot connector. COMPANY_LIST_MEMBER is a child table of COMPANY_LIST and contains the members of the list.

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

We’re deprecating the archived column in the CUSTOM_OBJECT table. We now use the _fivetran_deleted column to indicate whether a record is archived in the CUSTOM_OBJECT table. To support a smooth transition, we will populate both the archived and _fivetran_deleted for a limited time. After the transition period, you can drop the archived column from your destination.

Intercom

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

• ticket_state_internal_label
• ticket_state_external_label

Be sure to re-sync the connection to backfill the historical data for these columns.

Jira

We have added a new table, REQUEST_COMMENT, to store the comments associated with requests. We are gradually rolling out this change to all existing connections.

We have added the following columns to the COMMENT table:

• visibility_type
• visibility_identifier
• visibility_value

These columns allow you to understand which comments are restricted to specific groups or roles in your Jira instance. Comments without visibility restrictions will have null values in these columns, meaning they are visible to all users with access to the issue.

Mixpanel

We have removed the CAMPAIGN table because it is no longer available in the Mixpanel API.

NetSuite SuiteAnalytics

We now incrementally sync the NextTransactionLineLink and PreviousTransactionLineLink tables for the Netsuite2.com data source.

We have changed the primary key for the PostingAccountActivity, PreviousTransactionLineLink, and NextTransactionLineLink tables.

• For PostingAccountActivity, we now use the combination of fivetran_id and fivetran_index columns as the composite primary key.
• For PreviousTransactionLineLink, we now use the combination of previousdoc and fivetran_index columns as the composite primary key.
• For NextTransactionLineLink, we now use the combination of nextdoc and fivetran_index columns as the composite primary key.

Previously, _fivetran_id was their primary key.

QuickBooks

We have added two new columns, currency_id and exchange_rate, to the TRANSFER table.

We have added a new column, exchange_rate, to the CREDIT_CARD_PAYMENT_TXN table.

Rippling

Stripe

We've added a new table, CARD_PAYMENTS_FEES_TRANSACTION_LEVEL_1. The table provides enhanced visibility into transaction-level fees associated with card payments. We are gradually rolling out this change to all connections.

Workday Financial Management

We have added a new column, purchase_order_goods_line_id, to the RECEIPT_LINE_GOODS_ITEM table.

Workday HCM

We have added two new columns, organization_type_id and organization_type_code, to the WORKER_POSITION_ORGANIZATION table. Re-sync the table if you want to backfill historical data.

Zendesk Support

We have made the following changes to the sync strategy:

• We have added the following new columns to the GROUP_MEMBER table:

  • created_at
  • updated_at

• We now sync the TRANSLATION table. This table captures translation data for articles, sections, and categories. See our Translation Data documentation for more information.

• We have added a new child table USER_IDENTITY to the USER table. To sync the historical data for this table, you must trigger a full resync of the USER table.

  We are gradually rolling out this change to all connections.

• We have added the following new tables:

  • CSAT_SURVEY_ANSWER
  • CSAT_SURVEY_CLOSED_ENDED_OPTION
  • CSAT_SURVEY_QUESTION
  • CSAT_SURVEY_RATING_OPTION
  • LOCALE
  • TICKET_CSAT_SURVEY

  To sync the historical data for these table, you must trigger a full re-sync of the TICKET table.

  We are gradually rolling out this change to all connections.

Improvements

BigQuery

We have fixed a bug in the BigQuery connection setup form. Previously, setting the Use own service account toggle to OFF didn't clear the Service account key field value, causing connection failures.

Box

We have improved the setup experience for Box connections.

• Added a new configuration option, Preview Files to perform an intermediate test during configuration
• Added support for displaying fields based on the file type
• Added a new field, Quote character, to use an enclosing character
• Reorganised fields to make the setup form more intuitive
• Removed Infer as an option from the File Type field
• Removed the Enable Advanced Options toggle
• Changed the Null Sequence field to a toggle
• For the Delimiter character(s) field, we now use , as the default value
• For the Line Separator field, we now use \n as the default value

For more information, see our setup instructions and REST API configuration.

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

Exact Online

We have made the following changes to the sync strategy:

• We now incrementally sync the following tables:

• ACCOUNT

• ACCOUNT_CLASSIFICATION

• BANK

• BANK_ACCOUNT

• CONTACT

• GL_ACCOUNT

• GL_CLASSIFICATION

• SUBSCRIPTION

• SUBSCRIPTION_LINE

• SYSTEM_DIVISION

• TRANSACTION_LINE

• USERS

• We now capture deletes for the following tables:

• DIVISION

• GL_ACCOUNT_CLASSIFICATION_MAPPING

• LEAD_PURPOSE

• PROFIT_LOSS_OVERVIEW

• REPORTING_BALANCE

• RETURN

• REVENUE_LIST

• SALES_INVOICE

• SALES_INVOICE_LINE

Firebase

We have significantly improved the performance of our Firebase connector and added support for all levels of subcollections (nested collections).

All existing Firebase connections will be automatically upgraded to the new version.

• All levels of subcollections are now supported.
• The connector no longer automatically discovers subcollections. During connector setup, you can provide a list of subcollections to include. All existing subcollections will be automatically migrated.
• Subcollection table names in your destination are now prefixed with a forward slash (/) in the destination. If this character isn’t supported by the destination, it will be replaced with an appropriate alternative, such as an underscore (_).

For more information, see our Firebase connector documentation.

Forethought

The CONVERSATION_HISTORY table now supports history mode.

Greenhouse

We have changed the sync strategy for the JOB table and now re-import the table daily.

Managed Data Lakes Service

We renamed the Update BigQuery Metastore toggle in the destination setup form for Google Cloud Storage to Update BigLake Metastore. We have made this change to align with recent terminology changes by Google.

Maxio SaaSOptics

We have updated our sync strategy and now incrementally sync the TRANSACTION table. Previously, we re-imported this table daily.

Moloco

We have changed the authentication method for our Moloco connection. We now use an API key instead of OAuth to authenticate the Moloco connection. Be sure to re-authenticate your Moloco connection using API key. For more information, see our Moloco documentation.

Persona

We have changed our sync strategy. We now re-import the following tables during every sync to capture the updates and deletes:

• ACCOUNT
• CASES
• LIST
• TRANSACTION

We also re-import the REPORT table once a week to capture updates and deletes.

Sage Intacct

We have added a field, Historical Sync Limit, in the connection setup form. You can configure your historical sync limit to control the duration of historical records that are synced from Sage Intacct to your destination. Changes will be slowly rolled out to all customers over next two weeks.

We now sync child tables by ordering their records according to the foreign key of the parent table. We have changed the approach to ensure that we process the child records in alignment with their parent records, improving data integrity.

SAP ERP on HANA

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

• Since syncing parameterized views is not supported, they are now non-selectable in the Schema tab.

• Fivetran now displays a warning when syncing tables or views that reference proxy objects. Although these objects are supported, we recommend excluding them from sync. For more information, see the Excluded objects section.

• We fixed an issue affecting data volume calculations for unpacked tables (MDTC and STXL).

• We also resolved a timezone mismatch that caused incorrect suppression timestamp calculations.

High-availability SAP HANA replication configurations may experience a log replay delay. Previously, even a slight delay during failovers could cause tables to be re-synced to ensure reliable data replication. However, the connector now allows a small delay without requiring a re-sync.

During a failover event, we support a maximum log replay delay of 10 minutes between replicas. If the delay exceeds this threshold when the secondary replica takes over, affected tables will be re-synced individually based on the detected delay.

STFP

We have made the following changes to the connection setup form:

• Added support to configure archive patterns per table. This is useful when an archive folder contains files following different naming patterns, allowing you to route each pattern to a specific destination table based on its pattern.
• Renamed the Archive Folder Pattern field to Archive File Pattern.

For more information, see our setup instructions

Stripe

We have fixed an issue where the COUPON_PRODUCT table was not being populated correctly. Be sure to resync the COUPON table to backfill the historical data.

REST API Improvements

Managed Data Lakes Service

You can now configure your Managed Data Lakes Service destination using the Fivetran REST API. This feature is available only for Free, Standard, Enterprise, and Business Critical accounts.

Proxy Agent Management API changes

Our Proxy Agent Management API resource now supports the Regenerate secrets for Proxy Agent method.