November 2025
Connector SDK
fivetran-connector-sdk PyPI package
We have released version 2.3.4 of the fivetran-connector-sdk PyPI package. This release adds the following:
- Adds support for Python version 3.14. All new connections default to Python 3.14 unless the version is specified with the
--python-versionor --pythonargument at the deploy time. - Minor enhancements and improvements.
We have released version 2.3.3 of the fivetran-connector-sdk PyPI package. This release adds the following:
.ftignoresupport for Connector SDK. You can now create a.ftignorefile in the root of your connector project to specify files and directories that should be excluded duringfivetran_deploy. The syntax of the.ftignorefile is similar to that of a.gitignorefile.- Two new environment variables,
FIVETRAN_GROUP_IDandFIVETRAN_CONNECTION_NAME, which can be referenced from connector code. - Minor enhancements and improvements.
We have released version 2.3.2 of the fivetran-connector-sdk PyPI package. This release adds the following:
- Deprecation of Python v3.9
- Minor enhancements and improvements
Fivetran Connector SDK
Connector SDK no longer supports Python v3.9. If any of your connectors are using Python v3.9, you must update it to a more recent version of Python. If not, your connection's sync will fail.
Fivetran Azure Korea Center Servers
We have added new servers in the Azure Korea Central (Seoul) region.
If you're on a Business Critical plan, you can now select this region in your destination setup form. Connectors configured in a destination run in their designated cloud and region, meaning that your data doesn't leave our region-specific servers during processing. For example, if you configure your connectors to use our servers in the US, your data does not leave the US during processing.
For more information, see our data residency documentation.
Fivetran GCP Korea Seoul Servers
We have added new servers in the GCP Asia Northeast3 (Seoul) region.
If you're on a Business Critical plan, you can now select this region in your destination setup form. Connections configured in a destination run in their designated cloud and region, meaning that your data doesn't leave our region-specific servers during processing. For example, if you configure your connections to use our servers in the US, your data remains within the US during processing.
For more information, see our data residency documentation.
Lite Connectors
Lite connectors are now available for the following sources:
Type Locking
You can now lock the data types of your connection's columns in the destination by using the type locking feature. Once type locking is enabled for a connection, during every sync, Fivetran determines if the data type of incoming data differs from the locked type. Fivetran then converts values of the changed types to the locked types, preventing unexpected type changes that could disrupt your data workflows.
See our Type Locking documentation to learn more.
Schema changes
ADP Workforce Now
We have added two new child tables, WORKER_PAY_DISTRIBUTION and WORKER_PAY_DISTRIBUTION_INSTRUCTIONS, to the WORKER table. Be sure to re-sync the WORKER table to backfill historical data for these new child tables, or reach out to Fivetran Support to re-sync for you. MAR will be free for WORKER_PAY_DISTRIBUTION and WORKER_PAY_DISTRIBUTION_INSTRUCTIONS tables only.
We are gradually rolling out these changes to all connections.
Braze
We've added a new table, BANNER_EVENT.
Canny
| Table/column | Change type | Old name | New name | Notes | |
|---|---|---|---|---|---|
VOTE | |||||
| column | New Column | vote_priority | |||
Datadog
| Table/column | Change type | Old name | New name | Notes | |
|---|---|---|---|---|---|
SERVICE_LEVEL_OBJECTIVE_HISTORY_DENOMINATOR_VALUE | |||||
| column | Primary Key Change | denominator_value | denominator_value 🔑 | Added to primary key. | |
| column | Discontinued Column | index 🔑 | No longer primary key. | ||
SERVICE_LEVEL_OBJECTIVE_HISTORY_NUMERATOR_VALUE | |||||
| column | Discontinued Column | index 🔑 | No longer primary key. | ||
| column | Primary Key Change | numerator_value | numerator_value 🔑 | Added to primary key. | |
SERVICE_LEVEL_OBJECTIVE_HISTORY_SERIES_TIME | |||||
| column | Discontinued Column | index 🔑 | No longer primary key. | ||
| column | Primary Key Change | time | time 🔑 | Added to primary key. | |
GitHub
We have added the following new tables:
PROJECT_V2PROJECT_V2_CUSTOM_FIELDPROJECT_V2_ITEMPAGE_VIEWREPOSITORY_CLONE
We are gradually rolling out this change to all existing connections.
incident.io
| Table/column | Change type | Old name | New name | Notes | |
|---|---|---|---|---|---|
WORKFLOW_ONCE_FOR | |||||
| column | Rename Column | array | is_array | ||
Intercom
We have added two new tables, CALL and CALL_TRANSCRIPT.
We are gradually rolling out this change to all existing connections.
Ironclad
| Table/column | Change type | Old name | New name | Notes | |
|---|---|---|---|---|---|
APPROVAL_REQUEST | |||||
| table | New Table | APPROVAL_REQUEST | |||
ENTITY | |||||
| table | New Table | ENTITY | |||
ENTITY_NAMED_TYPE_ID | |||||
| table | New Table | ENTITY_NAMED_TYPE_ID | |||
ENTITY_RELATIONSHIP_TYPE | |||||
| table | New Table | ENTITY_RELATIONSHIP_TYPE | |||
TURN_HISTORY | |||||
| table | New Table | TURN_HISTORY | |||
TYPE_HASH_DATA | |||||
| table | New Table | TYPE_HASH_DATA | |||
Jamf
| Table/column | Change type | Old name | New name | Notes | |
|---|---|---|---|---|---|
COMPUTER_INVENTORY_LOCAL_USER_ACCOUNT | |||||
| column | Primary Key Change | id 🔑 | id | No longer a primary key. | |
| column | Primary Key Change | index 🔑 | Added to primary key. | ||
Jira
We have added a new column activatedDate to the SPRINT table.
Khoros Care
| Table/column | Change type | Old name | New name | Notes | |
|---|---|---|---|---|---|
TEAM_PERFORMANCE_INTERVAL | |||||
| column | Primary Key Change | _fivetran_id 🔑 | _fivetran_id 🔑 | Primary key calculation change. | |
| column | New Column | agent_activities_total_review_closed_time | |||
| column | New Column | agent_activities_v_2_active_time_in_focus | |||
| column | New Column | agent_activities_v_2_active_time_out_of_focus | |||
| column | New Column | agent_activities_v_2_idle_time_in_focus | |||
| column | New Column | agent_activities_v_2_idle_time_out_of_focus | |||
| column | New Column | agent_activities_v_2_in_app_time_in_focus | |||
| column | New Column | agent_activities_v_2_in_app_time_out_of_focus | |||
| column | New Column | agent_activities_v_2_inactive_time_in_focus | |||
| column | New Column | agent_activities_v_2_inactive_time_out_of_focus | |||
| column | New Column | agent_activities_v_2_non_agent_time_in_focus | |||
| column | New Column | agent_activities_v_2_non_agent_time_out_of_focus | |||
| column | New Column | agent_utilization | |||
TEAM_PERFORMANCE_REPORT | |||||
| column | Primary Key Change | _fivetran_id 🔑 | _fivetran_id 🔑 | Primary key calculation change. | |
| column | New Column | agent_activities_total_review_closed_time | |||
| column | New Column | agent_utilization | |||
Qualtrics
We have added the following new columns to the TICKET table:
first_time_enteredfirst_time_leftmost_recent_time_enteredmost_recent_time_left
SafetyCulture
| Table/column | Change type | Old name | New name | Notes | |
|---|---|---|---|---|---|
ACTION | |||||
| column | Discontinued Column | asset_id | |||
| column | Discontinued Column | completed_at | |||
| column | Discontinued Column | created_at | |||
| column | Discontinued Column | creator_id | |||
| column | Discontinued Column | description | |||
| column | Discontinued Column | due_at | |||
| column | Discontinued Column | inspection_id | |||
| column | Discontinued Column | occurred_at | |||
| column | Discontinued Column | priority_id | |||
| column | Discontinued Column | site_area | |||
| column | Discontinued Column | site_id | |||
| column | Discontinued Column | site_name | |||
| column | Discontinued Column | site_region | |||
| column | Discontinued Column | status_display_order | |||
| column | Discontinued Column | status_id | |||
| column | Discontinued Column | status_key | |||
| column | Discontinued Column | status_label | |||
| column | Discontinued Column | template_id | |||
| column | Discontinued Column | title | |||
| column | Discontinued Column | unique_id | |||
| column | New Column | action_id | |||
| column | New Column | assignee_id | |||
| column | New Column | name | |||
| column | New Column | organisation_id | |||
ACTION_COLLABORATOR | |||||
| table | Discontinued Table | ACTION_COLLABORATOR | |||
ACTION_LABEL | |||||
| table | Discontinued Table | ACTION_LABEL | |||
ACTION_REFERENCE | |||||
| table | Discontinued Table | ACTION_REFERENCE | |||
INSPECTION | |||||
| column | Discontinued Column | completed_at | |||
| column | Discontinued Column | delete_permission | |||
| column | Discontinued Column | edit_permission | |||
| column | Discontinued Column | is_marked_as_complete | |||
| column | Discontinued Column | issue_id | |||
| column | Discontinued Column | modified_by | |||
| column | Discontinued Column | owner_permission | |||
| column | Discontinued Column | revision_id | |||
| column | Discontinued Column | revision_key | |||
| column | Discontinued Column | schedule_id | |||
| column | Discontinued Column | site_ids | |||
| column | Discontinued Column | site_name | |||
| column | Discontinued Column | started_on | |||
| column | Discontinued Column | template_revision_id | |||
| column | Discontinued Column | title | |||
| column | Discontinued Column | total_score | |||
| column | Discontinued Column | view_permission | |||
| column | New Column | archived | |||
| column | New Column | asset_id | |||
| column | New Column | author_id | |||
| column | New Column | author_name | |||
| column | New Column | client_site | |||
| column | New Column | conducted_on | |||
| column | New Column | date_completed | |||
| column | New Column | date_modified | |||
| column | New Column | date_started | |||
| column | New Column | document_no | |||
| column | New Column | latitude | |||
| column | New Column | location | |||
| column | New Column | longitude | |||
| column | New Column | max_score | |||
| column | New Column | name | |||
| column | New Column | organisation_id | |||
| column | New Column | owner_id | |||
| column | New Column | owner_name | |||
| column | New Column | personnel | |||
| column | New Column | prepared_by | |||
| column | New Column | score | |||
| column | New Column | template_author | |||
| column | New Column | template_name | |||
| column | New Column | web_report_link | |||
INSPECTION_ITEMS | |||||
| table | New Table | INSPECTION_ITEMS | |||
INSPECTION_MEDIA | |||||
| table | Discontinued Table | INSPECTION_MEDIA | |||
SCHEDULE_OCCURRENCE | |||||
| table | New Table | SCHEDULE_OCCURRENCE | |||
SITE | |||||
| table | New Table | SITE | |||
USERS | |||||
| column | Discontinued Column | status | |||
| column | New Column | active | |||
| column | New Column | created_at | |||
| column | New Column | last_seen_at | |||
| column | New Column | organisation_id | |||
ShipHero
| Table/column | Change type | Old name | New name | Notes | |
|---|---|---|---|---|---|
ORDER_LINE_ITEM | |||||
| column | New Column | price | |||
SHIPMENT_SHIPPING_LABEL | |||||
| column | New Column | status | |||
Stripe
We have added the following new tables:
CASH_BALANCECASH_BALANCE_TRANSACTIONCHARGE_PAYMENT_METHOD_DETAILSPRICE_CURRENCY_OPTION
We are gradually rolling out this change to all existing connections.
Talkdesk
We have removed the foreign key constraint on contact_id between the CONTACT and CONTACT_CALL tables.
Teamwork
| Table/column | Change type | Old name | New name | Notes | |
|---|---|---|---|---|---|
CUSTOM_FIELD | |||||
| table | New Table | CUSTOM_FIELD | |||
PROJECT_CATEGORY | |||||
| table | New Table | PROJECT_CATEGORY | |||
Workday HCM
We have added a new child table, LOCATION_DOCUMENT_FIELD, to the LOCATION table.
Improvements
360Learning
We have added a new authentication method for our 360Learning connector. You can now use OAuth authentication to connect your 360Learning account with Fivetran. To support this enhancement, we have made the following changes to the connection setup form:
Added Authentication type field, that allows you to select between API key and OAuth 2.0 authentication methods.
Added Client ID, Client secret, and Base URL fields, allowing you to provide your own app credentials.
For more information, see our setup instructions.
Amazon S3
We have added a new feature, Dynamically extract tables. You can now define a single regex pattern with a named capture group (?<table>...) to automatically extract table names from file paths. This feature automatically creates and maps destination tables based on your file naming patterns, eliminating the need for manual intervention.
To support this feature, we have made the following changes to the connection setup form:
- Added a new option, File mapping, that allows you to choose between Define per table and Dynamically extract tables.
- Added a new field, Table extraction pattern, to specify your own regex pattern.
- Added a new button, Preview, to validate the specified regex pattern.
Key benefits include:
- Simplified configuration: Avoids repetitive setup for multiple entities.
- Automatic table creation: Captures new entities as they appear in your source, without additional configuration.
For more information, see our Dynamic Table Mapping tutorial and setup instructions.
We are gradually rolling out this change to all existing connections.
Azure Blob Storage
Azure Blob Storage connector now supports syncing Microsoft Excel spreadsheets. For more information, see our setup instructions.
Bitly
You can now select and deselect tables to be synced on the Schema tab of the connection details page in your Fivetran dashboard.
Bizzabo
We have changed our connection setup form and REST API parameters to support the following new tables:
AGENDA_SETTING_FILTER_URL_FILTER_TAGAGENDA_SETTING_FILTER_URL_FILTERAGENDA_SETTING_FILTER_URL_LOCATION_SUBLOCATIONAGENDA_SETTING_FILTER_URL_LOCATIONAGENDA_SETTING_FILTER_URLATTENDEE_ANALYTICSEVENT_CATEGORYEVENT_GOALEVENT_TEMPLATEPREROLL_SESSIONRECORDING_AUTHORIZATIONRECORDING_SESSIONREGISTRATION_FLOWREGISTRATION_FORMSESSION_ASSETSESSION_CHECKINSESSION_RATESESSION_RECORDING_VIEWSESSION_STARRINGSESSIONVIDEO_PRODUCER_SESSION
For more information, see our setup instructions and REST API Configuration.
Drata
We have made the following improvements to the connector:
Added table re-sync support. Previously, we only supported connection-level re-syncs.
Event-based tables and tables with a retention period at the source don't support this feature.
You can now select and deselect tables to be synced on the Schema tab of the connection details page in your Fivetran dashboard.
FTP
Our FTP connector now supports syncing Microsoft Excel spreadsheets. For more information, see our setup instructions.
GitHub
We now support syncing data from GitHub Enterprise Server (GHES) instances. You can connect your GHES instance by specifying the Host during the connection setup process. The feature is available only if you use the Personal Access Token authentication option. For more information, see our setup instructions. We are gradually rolling out this change to all connections.
Google Cloud Storage
Our Google Cloud Storage connector now supports syncing Microsoft Excel spreadsheets. For more information, see our setup instructions.
Invoiced
We have made the following changes to the sync strategy:
- We now re-import the
CUSTOMERtable weekly to capture updates and deletes. - We now use webhooks to capture updates and deletes for the
CONTACTtable.
Iterable
We now require the use of read-only API keys for connections created before August 10, 2023. If your connection uses an API key with write permissions, update it to a read-only key to maintain compatibility and ensure uninterrupted syncs.
Managed Data Lake Service
We now support the AWS PrivateLink and Azure Private Link connection methods for AWS and Azure data lakes on the Business Critical plan, respectively. We are gradually rolling out this enhancement to all existing destinations.
For more information, see our Managed Data Lake Service setup guide.
NICE
We no longer support priority-first sync for the CONTACT table.
Oracle Business Intelligence Publisher
We now support incremental syncs for custom data models, as well as for data models exceeding 2 GB or 2 million rows. For more information, see our Custom data models documentation.
We have improved the pagination strategy for re-import tables and active primary key extracts to prevent sync failures with large datasets. Previously, we attempted to extract all data at once, which caused syncs to fail when the data size was too large to process.
We are gradually rolling out this change to all existing connections.
Redshift destination
We now support IAM role authentication for authorizing S3 buckets associated with Redshift destinations configured for Hybrid Deployment.
Row Filtering - list of supported connectors extended
Row filtering is now supported for the following connectors:
To learn how to use row filtering and see the list of supported connectors, see our row filtering documentation.
Sage HR
We have made the following improvements to the connector:
Added table re-sync support. Previously, we only supported connection-level re-syncs.
Event-based tables and tables with a retention period at the source don't support this feature.
You can now select and deselect tables to be synced on the Schema tab of the connection details page in your Fivetran dashboard.
SAP ERP on HANA
A new version of the Fivetran NetWeaver API is now available for download: v1900296.
We have added a new configuration parameter that allows you to control the maximum number of background (BTC) processes used by SAP during data extraction.
We have improved the loading of partitions from disk to HANA memory for tables with active Data Aging. When reading the data from historical partitions only affected partitions will be loaded.
We now automatically maintain shadow tables to prevent them from growing indefinitely. Shadow tables are used for delete capture and accumulate records over time.
Our new incremental cleanup mechanism removes old records that are no longer needed after successful delete synchronization. The cleanup process works automatically in the background during each sync cycle without impacting sync reliability or data accuracy.
This feature is available for Fivetran NetWeaver API version 1900271 and higher. No additional configuration is required. For more information, see our Shadow table maintenance documentation.
Simplecast
We have made the following improvements to the connector:
Added table re-sync support. Previously, we only supported connection-level re-syncs.
Event-based tables and tables with a retention period at the source don't support this feature.
You can now select and deselect tables to be synced on the Schema tab of the connection details page in your Fivetran dashboard.
Slack
We will discontinue authentication using the Fivetran Slack app on February 28, 2026. We recommend that you create a new Slack connection using custom authentication. For more information, see our setup instructions.
Tableau
We have changed the sync strategy for the JOB table. We now re-import this table once a week to capture updates and deletes.
Webhooks
We now capture and store HTTP request headers from webhook events in a new headers column. This enhancement provides better observability and debugging capabilities by allowing you to access request metadata such as User-Agent, Content-Type, and custom headers sent with webhook events. For security, authentication headers and other sensitive headers containing keywords like auth, token, secret, password, and cookie are automatically filtered before storage. For more information, see the schema information in our Webhooks documentation.