July 2025

Connector SDK

Fivetran Connector SDK

Hybrid Deployment model is now generally available for Connector SDK. For more information, see our setup instructions.

`fivetran-connector-sdk` PyPI package

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

Internal enhancements and design improvements.

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

Internal enhancements and improvements.

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:

Managed Data Lake Service

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

Read our Managed Data Lake Service documentation.

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

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.

For these dbt Core versions, we don't support the MySQL destination. For the 1.10.3 dbt Core version, we also don't support the Azure Synapse destination. These destinations are not currently supported by the custom dbt Core adapters.

* 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.17.0.
Fivetran Platform Connector to version 2.2.2.
GitHub to version 0.9.1.
HubSpot to version 0.26.0.
Iterable to version 0.14.0.
Microsoft Dynamics 365 CRM to version 0.1.0-b2.
Qualtrics to version 0.4.0.
QuickBooks to version 0.20.1.
Recharge to version 0.5.0.
Reddit Ads to version 0.7.0.
SAP ERP on HANA to version 0.2.1.
Shopify to version 0.19.1.
Stripe to version 0.19.2.
Zendesk Support to version 0.25.0.

New connectors

Epic Clarity

Epic Clarity is a reporting database that extracts and transforms data from the Epic electronic health record (EHR) system.

Read our Epic Clarity connector documentation.

PayPal Sandbox

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

Veeva Vault

Veeva Vault is a cloud-based enterprise content management (ECM) platform designed specifically for the life sciences industry. Read our Veeva Vault connector documentation.

Schema changes

Aha!

Effective July 14, 2025 we use a new July 2025 schema. Review the latest ERD to better understand the schema changes.

We are updating the connector schema to prevent or resolve data integrity issues.

You should review the changes and update your downstream queries if necessary. Failing to do so may lead to missing or incomplete data in your data pipelines.

1 total changes • 1 possible breaking changes

Table/column	Change type		Old name	New name	Notes
`GOAL_PARENT`
column	Primary Key Change		`goal_id`	`goal_id` 🔑	Added to primary key.

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.

We have added the following tables to store Sales and Traffic Business Report data at ASIN granularity, with daily and monthly aggregations:

SALES_AND_TRAFFIC_BUSINESS_PARENT_ASIN_REPORT_*
SALES_AND_TRAFFIC_BUSINESS_CHILD_ASIN_REPORT_*
SALES_AND_TRAFFIC_BUSINESS_SKU_REPORT_*

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

Ashby

Effective July 31, 2025 we use a new July 2025 schema. Review the latest ERD to better understand the schema changes.

We are updating the connector schema to prevent or resolve data integrity issues.

1 total changes • 0 possible breaking changes

Table/column	Change type		Old name	New name	Notes
`LOCATION`
column	New Column			`name`

Braintree

We have added a new column, processed_with_network_token, to the TRANSACTION table. This column indicates whether the transaction was processed using a network token.

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.

We have added a new foreign key relationship between the CHARGE and VIRTUAL_CARD tables. The CHARGE table now includes a virtual_card_id column that references the id column in the VIRTUAL_CARD table.

Docebo

Effective July 1, 2025 we use a new July 2025 schema. Review the latest ERD to better understand the schema changes.

We are updating the connector schema to prevent or resolve data integrity issues.

You should review the changes and update your downstream queries if necessary. Failing to do so may lead to missing or incomplete data in your data pipelines.

2 total changes • 2 possible breaking changes

Table/column	Change type	Old name	New name	Notes
`GAMIFICATION_LEADERBOARD`
column	Primary Key Change	`users_id`	`users_id` 🔑	Added to primary key.
`GAMIFICATION_LEADERBOARD_POSITION`
column	Primary Key Change	`gamification_leaderboard_id`	`gamification_leaderboard_id` 🔑	Added to primary key.

Exact Online

Effective July 28, 2025 we use a new July 2025 schema. Review the latest ERD to better understand the schema changes.

We are updating the connector schema to adhere to standard naming conventions.

You should review the changes and update your downstream queries if necessary. Failing to do so may lead to missing or incomplete data in your data pipelines.

6 total changes • 6 possible breaking changes

Table/column	Change type	Old name	New name
`ACCOUNT`
column	Rename Column	`timestamp`	`timestamps`
`CONTACT`
column	Rename Column	`timestamp`	`timestamps`
`GL_ACCOUNT`
column	Rename Column	`timestamp`	`timestamps`
`GL_CLASSIFICATION`
column	Rename Column	`timestamp`	`timestamps`
`SUBSCRIPTION`
column	Rename Column	`timestamp`	`timestamps`
`SUBSCRIPTION_LINE`
column	Rename Column	`timestamp`	`timestamps`

Facebook Ads

Effective July 7, 2025 we use a new July 2025 schema. Review the latest ERD to better understand the schema changes.

We are updating the connector schema to support a feature enhancement.

You should review the changes and update your downstream queries if necessary. Failing to do so may lead to missing or incomplete data in your data pipelines.

16 total changes • 1 possible breaking changes

Table/column	Change type	Old name	New name	Notes
`AD_ASSET_FEED_SPEC_ASSET_CUSTOMIZATION_RULE`
table	New Table		`AD_ASSET_FEED_SPEC_ASSET_CUSTOMIZATION_RULE`
`AD_ASSET_FEED_SPEC_AUTOTRANSLATE`
table	New Table		`AD_ASSET_FEED_SPEC_AUTOTRANSLATE`
`AD_ASSET_FEED_SPEC_BODY`
table	New Table		`AD_ASSET_FEED_SPEC_BODY`
`AD_ASSET_FEED_SPEC_CALL_TO_ACTION`
table	New Table		`AD_ASSET_FEED_SPEC_CALL_TO_ACTION`
`AD_ASSET_FEED_SPEC_CAPTION`
table	New Table		`AD_ASSET_FEED_SPEC_CAPTION`
`AD_ASSET_FEED_SPEC_DESCRIPTION`
table	New Table		`AD_ASSET_FEED_SPEC_DESCRIPTION`
`AD_ASSET_FEED_SPEC_EVENT`
table	New Table		`AD_ASSET_FEED_SPEC_EVENT`
`AD_ASSET_FEED_SPEC_GROUP_RULE`
table	New Table		`AD_ASSET_FEED_SPEC_GROUP_RULE`
`AD_ASSET_FEED_SPEC_IMAGE`
table	New Table		`AD_ASSET_FEED_SPEC_IMAGE`
`AD_ASSET_FEED_SPEC_LINK_URL`
table	New Table		`AD_ASSET_FEED_SPEC_LINK_URL`
`AD_ASSET_FEED_SPEC_MESSAGE_EXTENSION`
table	New Table		`AD_ASSET_FEED_SPEC_MESSAGE_EXTENSION`
`AD_ASSET_FEED_SPEC_ONSITE_DESTINATION`
table	New Table		`AD_ASSET_FEED_SPEC_ONSITE_DESTINATION`
`AD_ASSET_FEED_SPEC_TITLE`
table	New Table		`AD_ASSET_FEED_SPEC_TITLE`
`AD_ASSET_FEED_SPEC_UPCOMING_EVENT`
table	New Table		`AD_ASSET_FEED_SPEC_UPCOMING_EVENT`
`AD_ASSET_FEED_SPEC_VIDEO`
table	New Table		`AD_ASSET_FEED_SPEC_VIDEO`
`CREATIVE_HISTORY`
column	Discontinued Column	`asset_feed_spec_link_urls`		Data now available in the `AD_ASSET_FEED_SPEC_LINK_URL` table.

Fivetran Platform Connector

We have added a new column, deployment_type, to the CONNECTIONS table. This column captures the deployment model used with a given connection. Possible values are as follows: Fivetran, Hybrid.

Float

Effective July 17, 2025 we use a new July 2025 schema. Review the latest ERD to better understand the schema changes.

We are updating the connector schema to enhance its usability.

1 total changes • 0 possible breaking changes

Table/column	Change type		Old name	New name	Notes
`LOGGED_TIME`
column	New Column			`task_meta_id`

Forethought

Effective July 3, 2025 we use a new July 2025 schema. Review the latest ERD to better understand the schema changes.

We are updating the connector schema to support a feature enhancement.

You should review the changes and update your downstream queries if necessary. Failing to do so may lead to missing or incomplete data in your data pipelines.

1 total changes • 1 possible breaking changes

Table/column	Change type		Old name	New name	Notes
`CONVERSATION (new table name: CONVERSATION_HISTORY)`
table	Rename Table		`CONVERSATION`	`CONVERSATION_HISTORY`

Genesys

Effective July 18, 2025 we use a new July 2025 schema. Review the latest ERD to better understand the schema changes.

We are updating the connector schema to prevent or resolve data integrity issues.

You should review the changes and update your downstream queries if necessary. Failing to do so may lead to missing or incomplete data in your data pipelines.

4 total changes • 4 possible breaking changes

Table/column	Change type	Old name	New name	Notes
`ANALYTIC_USER_DETAIL_PRIMARY_PRESENCE`
column	Discontinued Column	`index` 🔑		No longer primary key
column	Primary Key Change		`_fivetran_id` 🔑	New primary key
`ANALYTIC_USER_DETAIL_ROUTING_STATUS`
column	Discontinued Column	`index` 🔑		No longer primary key
column	Primary Key Change		`_fivetran_id` 🔑	New primary key

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.

Google Ads

The following reports have been deprecated:

extension_feed_item
feed_item
feed_placeholder_view

Greenhouse

Effective July 14, 2025 we use a new July 2025 schema. Review the latest ERD to better understand the schema changes.

We are updating the connector schema to enhance its usability.

1 total changes • 0 possible breaking changes

Table/column	Change type		Old name	New name	Notes
`USER_EMAIL`
column	New Column			`is_primary`	If a primary email address from the `USERS` table matches an email in the `USER_EMAIL` table, we set the column to TRUE; otherwise, it is FALSE.

Effective July 24, 2025 we use a new July 2025 schema. Review the latest ERD to better understand the schema changes.

We are updating the connector schema to prevent or resolve data integrity issues.

You should review the changes and update your downstream queries if necessary. Failing to do so may lead to missing or incomplete data in your data pipelines.

4 total changes • 2 possible breaking changes

Table/column	Change type	Old name	New name	Notes
`EDUCATION`
column	Primary Key Change	`id` 🔑		No longer a primary key.
column	New Column		`index` 🔑	New primary key.
`EMPLOYMENT`
column	Primary Key Change	`id` 🔑		No longer a primary key.
column	New Column		`index` 🔑	New primary key.

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.

Effective July 4, 2025 we use a new July 2025 schema. Review the latest ERD to better understand the schema changes.

We are updating the connector schema to align with source changes.

1 total changes • 0 possible breaking changes

Table/column	Change type		Old name	New name	Notes
`SUBMISSION_RESPONSE`
table	New Table			`SUBMISSION_RESPONSE`	`SUBMISSION_RESPONSE` is a child table of the `FORM` table.

Effective July 11, 2025 we use a new July 2025 schema. Review the latest ERD to better understand the schema changes.

We are updating the connector schema to align with source changes.

2 total changes • 0 possible breaking changes

Table/column	Change type	New name	Notes
`COMPANY_LIST`
table	New Table	`COMPANY_LIST`
`COMPANY_LIST_MEMBER`
table	New Table	`COMPANY_LIST_MEMBER`	`COMPANY_LIST_MEMBER` is a child table of the `COMPANY_LIST` table.

Effective July 21, 2025 we use a new July 2025 schema. Review the latest ERD to better understand the schema changes.

We are updating the connector schema to align with source changes.

8 total changes • 0 possible breaking changes

Table/column	Change type	New name	Notes
`CONVERSATION_CHANNEL`
table	New Table	`CONVERSATION_CHANNEL`
`CONVERSATION_CHANNEL_ACCOUNT`
table	New Table	`CONVERSATION_CHANNEL_ACCOUNT`	`CONVERSATION_CHANNEL_ACCOUNT` is a child table of the `CONVERSATION_CHANNEL` table.
`CONVERSATION_INBOX`
table	New Table	`CONVERSATION_INBOX`
`CONVERSATION_MESSAGE_ACTOR`
table	New Table	`CONVERSATION_MESSAGE_ACTOR`	`CONVERSATION_MESSAGE_ACTOR` is a child table of the `CONVERSATION_THREAD` table.
`CONVERSATION_MESSAGE_HISTORY`
table	New Table	`CONVERSATION_MESSAGE_HISTORY`	`CONVERSATION_MESSAGE_HISTORY` is a child table of the `CONVERSATION_THREAD` table.
`CONVERSATION_MESSAGE_RECIPIENT`
table	New Table	`CONVERSATION_MESSAGE_RECIPIENT`	`CONVERSATION_MESSAGE_RECIPIENT` is a child table of the `CONVERSATION_THREAD` table.
`CONVERSATION_MESSAGE_SENDER`
table	New Table	`CONVERSATION_MESSAGE_SENDER`	`CONVERSATION_MESSAGE_SENDER` is a child table of the `CONVERSATION_THREAD` table.
`CONVERSATION_THREAD`
table	New Table	`CONVERSATION_THREAD`

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.

ironSource

Effective July 31, 2025 we use a new July 2025 schema. Review the latest ERD to better understand the schema changes.

We are updating the connector schema to enhance its usability.

You should review the changes and update your downstream queries if necessary. Failing to do so may lead to missing or incomplete data in your data pipelines.

7 total changes • 3 possible breaking changes

Table/column	Change type	Old name	New name
`APPLICATION`
column	Discontinued Column	`network_reporting_api_ironSource`
column	New Column		`network_reporting_api_iron_source`
`MEDIATION_GROUP`
table	New Table		`MEDIATION_GROUP`
`MEDIATION_GROUP_COUNTRY`
table	New Table		`MEDIATION_GROUP_COUNTRY`
`MEDIATION_GROUP_INSTANCE`
table	New Table		`MEDIATION_GROUP_INSTANCE`
`MEDITATION_MANAGEMENT`
table	Discontinued Table	`MEDITATION_MANAGEMENT`
`MEDITATION_MANAGEMENT_AD_UNIT`
table	Discontinued Table	`MEDITATION_MANAGEMENT_AD_UNIT`

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.

Kantata

We've added a new table, WORKSPACE_STATUS_CHANGE. The table contains records of changes made to the status of a project workspace, allowing you to track project status transitions over time.

KeyPay

Effective July 28, 2025 we use a new July 2025 schema. Review the latest ERD to better understand the schema changes.

We are updating the connector schema to enhance its usability.

You should review the changes and update your downstream queries if necessary. Failing to do so may lead to missing or incomplete data in your data pipelines.

62 total changes • 29 possible breaking changes

Table/column	Change type	Old name	New name	Notes
`ABA`
table	New Table		`ABA`
`DEDUCTION_CATEGORY`
table	New Table		`DEDUCTION_CATEGORY`
`EMPLOYEE`
column	Rename Column	`is_enabled_for_timesheets`	`is_enabled_for_timesheet`
column	Rename Column	`locations`	`location`
column	Rename Column	`reporting_dimension_values`	`reporting_dimension_value`
column	Rename Column	`rostering_notification_choices`	`rostering_notification_choice`
column	Rename Column	`work_types`	`work_type`
`EMPLOYEE_DEDUCTION`
table	New Table		`EMPLOYEE_DEDUCTION`
`EMPLOYEE_STANDARD_HOUR`
table	New Table		`EMPLOYEE_STANDARD_HOUR`
`EMPLOYEE_STANDARD_HOUR_WORK_DAY`
table	New Table		`EMPLOYEE_STANDARD_HOUR_WORK_DAY`
`ESS_LEAVE_REQUEST`
table	Discontinued Table	`ESS_LEAVE_REQUEST`
`ESS_PAY_SLIP`
table	Discontinued Table	`ESS_PAY_SLIP`
`ESS_ROSTER_SHIFT`
table	Discontinued Table	`ESS_ROSTER_SHIFT`
`ESS_ROSTER_SHIFT_BREAK`
table	Discontinued Table	`ESS_ROSTER_SHIFT_BREAK`
`ESS_ROSTER_SHIFT_QUALIFICATION`
table	Discontinued Table	`ESS_ROSTER_SHIFT_QUALIFICATION`
`ESS_UNAVAILABILITY`
table	Discontinued Table	`ESS_UNAVAILABILITY`
`ESS_WORK_TYPE`
table	Discontinued Table	`ESS_WORK_TYPE`
`EXPENSE_REQUEST`
column	Rename Column	`status_update_notes`	`status_update_note`
`LEAVE_ALLOWANCE`
column	Primary Key Change	`_fivetran_id` 🔑	`_fivetran_id` 🔑	Calculation Change
column	Rename Column	`automatically_accrues`	`automatically_accrue`
`LEAVE_BALANCE`
table	New Table		`LEAVE_BALANCE`
`LEAVE_CATEGORY`
column	Rename Column	`automatically_accrues`	`automatically_accrue`
column	Rename Column	`units`	`unit`
`LEAVE_LIABILITY_REPORT`
column	Rename Column	`accrued_amount_in_hours`	`accrued_amount_in_hour`
column	Rename Column	`approved_leave_amount_in_hours`	`approved_leave_amount_in_hour`
column	Rename Column	`calculated_weeks`	`calculated_week`
`LEAVE_REQUEST`
table	New Table		`LEAVE_REQUEST`
`PAY_CATEGORY`
column	Rename Column	`number_of_decimal_places`	`number_of_decimal_place`
`PAY_RATE`
table	New Table		`PAY_RATE`
`PAY_RATE_TEMPLATE`
column	Rename Column	`reapply_to_linked_employees`	`reapply_to_linked_employee`
`PAY_RATE_TEMPLATE_PAY_CATEGORY`
column	Rename Column	`standard_weekly_hours`	`standard_weekly_hour`
`PAY_RUN`
table	New Table		`PAY_RUN`
`PAY_RUN_DETAIL`
table	New Table		`PAY_RUN_DETAIL`
`PAY_RUN_SUMMARY`
column	Rename Column	`total_gross_wages`	`total_gross_wage`
column	Rename Column	`total_hours`	`total_hour`
column	Rename Column	`total_net_wages`	`total_net_wage`
`PAY_SCHEDULE`
table	New Table		`PAY_SCHEDULE`
`PAY_SCHEDULE_LOCATION`
table	New Table		`PAY_SCHEDULE_LOCATION`
`PAY_SLIP`
table	New Table		`PAY_SLIP`
`PAY_SLIP_ACCRUED_LEAVE`
table	New Table		`PAY_SLIP_ACCRUED_LEAVE`
`PAY_SLIP_BANK_PAYMENT`
table	New Table		`PAY_SLIP_BANK_PAYMENT`
`PAY_SLIP_CONFIGURATION`
table	New Table		`PAY_SLIP_CONFIGURATION`
`PAY_SLIP_DEDUCTION`
table	New Table		`PAY_SLIP_DEDUCTION`
`PAY_SLIP_EARNINGS_LINE`
table	New Table		`PAY_SLIP_EARNINGS_LINE`
`PAY_SLIP_EMPLOYEE_EXPENSE`
table	New Table		`PAY_SLIP_EMPLOYEE_EXPENSE`
`PAY_SLIP_GROSS_YTD_DETAIL`
table	New Table		`PAY_SLIP_GROSS_YTD_DETAIL`
`PAY_SLIP_LEAVE_TAKEN`
table	New Table		`PAY_SLIP_LEAVE_TAKEN`
`PAY_SLIP_PAYG_ADJUSTMENT`
table	New Table		`PAY_SLIP_PAYG_ADJUSTMENT`
`PAY_SLIP_SUPER_ADJUSTMENT`
table	New Table		`PAY_SLIP_SUPER_ADJUSTMENT`
`PAY_SLIP_SUPER_PAYMENT`
table	New Table		`PAY_SLIP_SUPER_PAYMENT`
`PAY_SLIP_TOTAL_ACCRUED_LEAVE`
table	New Table		`PAY_SLIP_TOTAL_ACCRUED_LEAVE`
`PUBLIC_HOLIDAY`
table	New Table		`PUBLIC_HOLIDAY`
`PUBLIC_HOLIDAY_LOCATION`
table	New Table		`PUBLIC_HOLIDAY_LOCATION`
`ROSTER_SHIFT`
table	New Table		`ROSTER_SHIFT`
`ROSTER_SHIFT_BREAK`
table	New Table		`ROSTER_SHIFT_BREAK`
`ROSTER_SHIFT_QUALIFICATION`
table	New Table		`ROSTER_SHIFT_QUALIFICATION`
`SUPER_FUND`
table	New Table		`SUPER_FUND`
`TIMESHEET`
column	Rename Column	`comments`	`comment`
column	Rename Column	`hidden_comments`	`hidden_comment`
column	Rename Column	`units`	`unit`
`UNAVAILABILITY`
table	New Table		`UNAVAILABILITY`
`WORK_TYPE`
table	New Table		`WORK_TYPE`

LinkedIn Ad Analytics

Effective July 10, 2025 we use a new July 2025 schema. Review the latest ERD to better understand the schema changes.

We are updating the connector schema to support a feature enhancement.

1 total changes • 0 possible breaking changes

Table/column	Change type		Old name	New name	Notes
`CREATIVE_HISTORY`
column	New Column			`name`

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.

Pardot

We have added the following new tables:

CUSTOM_REDIRECT
FORM
FORM_FIELD
FORM_FIELD_DEPENDENT
FORM_FIELD_PROGRESSIVE
FORM_FIELD_VALUE
FORM_HANDLER
FORM_HANDLER_FIELD

We are gradually rolling out this improvement to all connections. Syncing these new tables will count towards free Monthly Active Rows (MAR) till Aug 30, 2025.

Pipedrive

We have added two new tables, TASKS and PROJECT. We are gradually rolling out this change to all connections.

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

Effective July 4, 2025 we use a new July 2025 schema. Review the latest ERD to better understand the schema changes.

We are updating the connector schema to align with source changes.

3 total changes • 0 possible breaking changes

Table/column	Change type	New name
`LEAVE_REQUEST`
table	New Table	`LEAVE_REQUEST`
`LEAVE_REQUEST_DAY_TAKE_OFF`
table	New Table	`LEAVE_REQUEST_DAY_TAKE_OFF`
`LEAVE_TYPE`
table	New Table	`LEAVE_TYPE`

Salesforce Commerce Cloud

We have added a new table, CUSTOMER_ADDRESS, to the Salesforce Commerce Cloud connector. This table now contains all customer addresses, and it can be joined to the CUSTOMER table using the customerNo column.

Shopify

We have removed pre_tax_price and pre_tax_price_set columns from the ORDER_LINE table.

We have added the following new tables to store web pixels event data to analyze customer interactions. We sync all the standard Shopify web pixels events that are sent by the Shopify web pixels. For more information, see our documentation.

ALERT_DISPLAYED_EVENT
CART_ATTRIBUTE_EVENT
CART_LINE_EVENT
CART_VIEWED_EVENT
CHECKOUT_ATTRIBUTES_EVENT
CHECKOUT_DELIVERY_OPTION_EVENT
CHECKOUT_DISCOUNT_APPLICATION_EVENT
CHECKOUT_EVENT
CHECKOUT_LINE_ITEM_DISCOUNT_ALLOCATION_EVENT
CHECKOUT_LINE_ITEM_EVENT
CHECKOUT_LINE_ITEM_PROPERTY_EVENT
CHECKOUT_TRANSACTION_EVENT
COLLECTION_VIEWED_EVENT
COLLECTION_VIEWED_PRODUCT_VARIANT_EVENT
PAGE_VIEWED_EVENT
PRODUCT_ADDED_TO_CART_EVENT
PRODUCT_REMOVED_FROM_CART_EVENT
PRODUCT_VIEWED_EVENT
SEARCH_RESULT_PRODUCT_VARIANT_EVENT
SEARCH_SUBMITTED_EVENT
UI_EXTENSION_ERRORED_EVENT

You must re-authenticate the connection to sync these tables. These syncs count towards free Monthly Active Rows (MAR) till 31st August, 2025.

We are gradually rolling out these changes for all connections.

Spotify Ads

We've added the following metadata tables:

BUSINESS
AUDIENCE
AD_SET_AUDIENCE
AD_SET_AUDIENCE_EXCLUSION
AD_SET_PLACEMENT

We've discontinued support for the AD_SET_EXCLUDE_PLACEMENT table. Use the new AD_SET_PLACEMENT table instead.

We've added the following columns to the AD_ACCOUNT table:

ad_account_role
billing_address_city
billing_address_name
billing_address_postal_code
billing_address_region
billing_address_street
billing_address_tax_region
business_id
currency_code
legal_entity_name
status
status_reason

We now support the STREAMED_IMPRESSIONS metric for custom reports.

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.

UKG Pro

Effective July 25, 2025 we use a new July 2025 schema. Review the latest ERD to better understand the schema changes.

We are updating the connector schema to support a feature enhancement

1 total changes • 0 possible breaking changes

Table/column	Change type		Old name	New name	Notes
`EMPLOYMENT`
column	New Column			`work_phone_number`

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've added the following new tables:

USER_SUBSCRIPTION
CONTENT_SUBSCRIPTION

See our Zendesk Support Subscription Data documentation for more information.

We've added the following new tables:

BADGE
BADGE_ASSIGNMENT
BADGE_CATEGORY

BADGE and BADGE_CATEGORY are the parent tables, while BADGE_ASSIGNMENT is a child table of BADGE.

We've added the following new columns to the GROUP_MEMBER table:

created_at
updated_at

We've added a new table, TRANSLATION. This table captures translation data for articles, sections, and categories. See our Translation Data documentation for more information.

We've added a new child table, USER_IDENTITY, to the USER table. To sync the historical data for this table, you must trigger a full re-sync of the USER table. We are gradually rolling out this change to all connections.

We've 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 tables, you must trigger a full re-sync of the TICKET table. We are gradually rolling out this change to all connections.

Zoho Recruit

Effective July 21, 2025 we use a new July 2025 schema. Review the latest ERD to better understand the schema changes.

We are updating the connector schema to fix a bug.

You should review the changes and update your downstream queries if necessary. Failing to do so may lead to missing or incomplete data in your data pipelines.

1 total changes • 1 possible breaking changes

Table/column	Change type		Old name	New name	Notes
`CANDIDATE`
column	Rename Column		`mofidied_by_id`	`modified_by_id`

Zuora

We've discontinued indirectly related object IDs for the CREDIT_TAXATION_ITEM and CREDIT_MEMO_APPLICATION_ITEM tables to enhance data normalization. To identify indirect relationships, refer to the direct-relationship field in the Zuora API response.

You can still retrieve these IDs by joining related tables in your destination.

We are making this change only for the accounts created after July 18, 2025.

Improvements

Acumatica

We now sync historical data for your connection starting from January 1, 2020.

Adobe Analytics

We removed the legacy JWT authentication method and migrated to Server-to-Server OAuth authentication. See the Adobe Analytics Migration Guide for more details.

Amazon S3

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.

Amplitude

We no longer support the AWS S3 bucket export mechanism.

Apache Kafka destination

All Kafka implementations now support the Hybrid Deployment model. We are gradually rolling out this feature to all existing destinations. For more information, see the individual destination setup guides.

Azure Blob Storage

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

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.

BigQuery destination

We have added support for the JSON data type. Previously, we converted the data type of JSON columns to STRING when writing them to your BigQuery destination.

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.

CockroachDB

We now support syncing the ENUM data type from your source. In your destination, the ENUM data type will appear as a STRING data type.

Concord

We have fixed an issue that prevented the AGREEMENT_PATH, FOLDER, REPORT, and TAGS entities from syncing the following breakout tables:

AGREEMENT_PATH_INVITATION
AGREEMENT_PATH_TEAM
AGREEMENT_PATH_TEAM_INVITATION
AGREEMENT_PATH_TEAM_USER
AGREEMENT_PATH_USER
FOLDER_CHILDREN
FOLDER_INVITATION
FOLDER_TEAM
FOLDER_TEAM_INVITATION
FOLDER_TEAM_USER
FOLDER_USER
REPORT_FILTER_CREATED_BY
REPORT_FILTER_STATUS
TAG_INVITATION
TAG_USER_GROUP_INVITATION
TAG_USER
TAG_USER_GROUP
TAG_USER_GROUP_MEMBER

Delighted

We've added tale-level selection and re-sync option for all the tables.

Dropbox

We have improved the setup experience for Dropbox 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

Facebook Ads

The Facebook Ads connector now supports syncing data which describes dynamic creatives. To see a list of tables we've added support for, see schema changes.

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

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.

GitLab

We have changed the sync strategy for the EPIC_ISSUE and GROUPS_MILESTONE tables. We now incrementally sync these tables. Previously, we re-imported them daily.

Google Ads

We now support Google Ads API 20.

Google Cloud Storage (GCS)

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

Google Drive

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

Google Search Ads 360

You can now set a rollback window between 2 and 90 days for each report in your connection setup form. By default, we use a 30-day rollback window. Learn more in our rollback sync documentation.

The Google Search Ads 360 connector now supports the Hybrid Deployment model. For more information, see the setup guide.

Google Search Console

Google Search Console connector now supports multi-filtering for custom reports.

Greenhouse

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

HubSpot

We have added support for HubSpot's Conversations API to sync conversations data from your HubSpot account. We are gradually rolling out this improvement to all existing connections.

We have improved our sync strategy for the 'EVENT' table to allow syncing all types of events from HubSpot, except e_list_size_changed and e_user_performed_action_no_object_type.

We now re-import property history for records with recent merges in the COMPANY and CONTACT tables during every incremental sync. This prevents frequent full resyncs of these tables to fetch the latest properties of merged records. To enable this, you can create a custom workflow for the COMPANY or CONTACT tables with the merge_timestamp property.

Jira

Our Jira connector now suppports OAuth 2.0 3LO authorization. We are gradually rolling out this change to all existing connections. See the connector's setup guide for more details.

Klaviyo

We now perform rollback syncs with a one-day window for the EVENT table to capture late-arriving records and ensure data accuracy.

Managed Data Lake 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.

Marketo

You can now deselect the LEAD table in your connection schema tab.

Maxio SaaSOptics

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

Microsoft Dynamics 365 Business Central

We have changed our sync strategy to capture deletes. Now, we also re-import all the tables weekly. For more information, see our Microsoft Dynamics 365 Business Central connector documentation.

Our Microsoft Dynamics 365 Business Central connection is now generally available.

Read our Microsoft Dynamics 365 Business Central connection documentation.

Microsoft Dynamics 365 Finance and Operations

We now support syncing data stored in Delta Lake format for our Microsoft Dynamics 365 Finance and Operations connection. For more information, see our Microsoft Dynamics 365 Finance and Operations connector documentation.

Migration of Reddit Reporting API to v3

Our Reddit Ads connector now uses the new Reddit Ads API v3. This migration includes the following changes:

We've discontinued support for the following columns:
- app_install_metrics_spend_count
- comment_downvotes
- comment_upvotes
- comments_page_views
- legacy_click_conversions
- legacy_view_conversions
- viewer_comments
- viewable_impressions
We've discontinued support for the post_id field. It is no longer available as a breakdown or report level, and all custom reports using this level are no longer supported. You must recreate any reports using this breakdown through the setup form.
We've discontinued support for the POST_REPORT prebuilt report.
We've discontinued support for all event conversion fields that start with view_through_conversion_attribution_window_* and click_through_conversion_attribution_window_* (e.g., view_through_conversion_attribution_window_week and click_through_conversion_attribution_window_day). This affects custom reports that include event conversion data and conversion reports that were created as child tables. Columns related to these event fields in _CONVERSION_REPORT tables will be discontinued.
We've renamed the following columns in all tables:
- app_install_metrics_add_payment_info has been renamed to app_install_add_payment_info_count
- app_install_metrics_add_to_cart has been renamed to app_install_add_to_cart_count
- app_install_metrics_app_launch has been renamed to app_install_app_launch_count
- app_install_metrics_completed_tutorial has been renamed to app_install_completed_tutorial_count
- app_install_metrics_install has been renamed to app_install_install_count
- app_install_metrics_level_achieved has been renamed to app_install_level_achieved_count
- app_install_metrics_purchase has been renamed to app_install_purchase_count
- app_install_metrics_search has been renamed to app_install_search_count
- app_install_metrics_sign_up has been renamed to app_install_sign_up_count
- app_install_metrics_spend_credits has been renamed to app_install_spend_credits_count
- app_install_metrics_view_content has been renamed to app_install_view_content_count
Our Reddit Ads connector can now retrieve 2-years worth of reporting data.

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.

PostgreSQL destination

We have added a new setup test, Validate Temporary Table Test, to verify that we have the permission to create a temporary table in your PostgreSQL database and insert rows into it.

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

We now truncate DATETIME and INSTANT values to the nearest microsecond in your PostgreSQL destination. Previously, we rounded these values to the nearest microsecond. We are gradually rolling out this change to all existing destinations. Be sure to update your downstream queries for accurate results.

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.

Salesforce

Salesforce Mutual TLS (mTLS), to connect your Salesforce account to Fivetran is now generally available. For more information, see our Mutual Authentication documentation for detailed instructions on how to enable this option.

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.

SharePoint

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

Snowflake destination

We now use the Snowflake user stage (internal stage) for staging intermediate files. This improves security and reduces your data footprint within Fivetran systems, minimizing data exposure.

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

We have increased the maximum allowed length for columns of the following data types to support the behavior change introduced in Snowflake 2025_03 bundle:

BINARY
VARCHAR
VARIANT

To backfill the historical data for such columns, re-sync the affected tables or contact our support team to re-sync them for you.

You can now choose the virtual warehouse you want to use for running queries and performing DML operations when setting up your Snowflake destination. To support this enhancement, we have made the following changes:

Added a new drop-down menu, Default Virtual Warehouse, to the Snowflake setup form. This menu displays all virtual warehouses available to the Fivetran user and allows you to specify the default warehouse for the destination.
Added a new drop-down menu, Snowflake Destination Virtual Warehouse, to the setup forms of source connections associated with Snowflake destinations. This option lets you override the destination-level default and select a different warehouse for individual connections.

We are gradually rolling out this feature to all existing destinations.

Spotify Ads

We now support the Spotify Ads API v3.

SQL Server

We have introduced a new incremental sync method, Binary Log Reader, for our SQL Server connector. This proprietary method reads your database's transaction log files in their original binary format. For more information, see our SQL Server - Binary Log Reader documentation.

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.

TikTok Ads

We've added the following dimensions to basic reports:

AD_TYPE
COMPONENT_NAME
EVENT_SOURCE_ID
IMAGE_ID
PAGE_ID
POST_ID
ROOM_ID
SEARCH_TERMS
VIDEO_MATERIAL_ID

We added checks to the UI for dimension groupings, for more information visit: https://business-api.tiktok.com/gateway/docs/index?identify_key=c0138ffadd90a955c1f0670a56fe348d1d40680b3c89461e09f78ed26785164b&language=ENGLISH&doc_id=1751443956638721#item-link-Dimension%20grouping

Workday Financial Management

We now sync the SUPPLIER_INVOICE_LINE table using the Get_Supplier_Invoice API, because Get_Supplier_Invoice_Lines does not return any data. We automatically resync the SUPPLIER_INVOICE_LINE table.

We are gradually rolling out this improvement to all connections.

Zendesk Chat

We've added tale-level selection and re-sync option for all the tables.

REST API Improvements

Managed Data Lake Service

You can now configure your Managed Data Lake 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.

July 2025

Connector SDK

Fivetran Connector SDK

fivetran-connector-sdk PyPI package

Lite Connectors

Managed Data Lake Service

Transformations for dbt Core

dbt Core versions 1.7.19, 1.8.9, and 1.10.3 support

Updated dbt Quickstart packages

New connectors

Epic Clarity

PayPal Sandbox

Veeva Vault

Schema changes

Aha!

Amazon Selling Partner

Ashby

Braintree

Branch

Coupa

Docebo

Exact Online

Facebook Ads

Fivetran Platform Connector

Float

Forethought

Genesys

GitHub

Google Ads

Greenhouse

HubSpot

Intercom

ironSource

Jira

Kantata

KeyPay

LinkedIn Ad Analytics

Mixpanel

NetSuite SuiteAnalytics

Pardot

Pipedrive

QuickBooks

Rippling

Salesforce Commerce Cloud

Shopify

Spotify Ads

Stripe

UKG Pro

Workday Financial Management

Workday HCM

Zendesk Support

Zoho Recruit

Zuora

Improvements

Acumatica

Adobe Analytics

Amazon S3

Amplitude

Apache Kafka destination

Azure Blob Storage

BigQuery

BigQuery destination

Box

CockroachDB

Concord

Delighted

Dropbox

Exact Online

Facebook Ads

Firebase

Forethought

GitLab

Google Ads

Google Cloud Storage (GCS)

Google Drive

Google Search Ads 360

Google Search Console

Greenhouse

HubSpot

Jira

`fivetran-connector-sdk` PyPI package