July 2026
Connector SDK
Fivetran Connector SDK
We now support an optional setup form for Connector SDK connections. You can define form fields and setup tests in Python that Fivetran renders in the dashboard. Refer to our Connector SDK Setup Form documentation for more details.
fivetran-connector-sdk PyPI package
We have released version 2.10.3 of the fivetran-connector-sdk PyPI package. This release includes the following updates:
- Adds the
configurationcommand to run the connector's configuration form with interactive prompting support and createconfiguration.jsonlocally from the provided input. Supports an additional--testflag to run connector tests locally. - Improved configuration form UI rendering performance.
- Updated testers to support the updates.
We have released version 2.10.2 of the fivetran-connector-sdk PyPI package. This release includes the following updates:
- Added validation for unique field names within a table.
- Improved
fivetran initbehavior. - Improved error detection for connector object issues in the tester.
We have released version 2.10.1 of the fivetran-connector-sdk PyPI package. This release supersedes the yanked 2.10.0 release and includes the following updates:
- Fixed an issue with downloading the stable updated testers.
- Added validation for empty table names.
- Improved logging for agent plugins.
- Minor enhancements and improvements.
(Yanked: Tester Version Mismatch) We have released version 2.10.0 of the fivetran-connector-sdk PyPI package. This release includes the following updates:
- Added validation for empty table names.
- Improved logging for agent plugins.
- Minor enhancements and improvements.
- Updated testers.
fivetran-api-playground PyPI package
We have released version 1.1.8 of the fivetran-api-playground PyPI package. This release adds the following:
- Upgrades the requests library dependency to 2.34.2.
- Upgrades the faker library dependency to 40.23.0.
Dashboard Improvements
Delay notification sensitivity default changed to Low
We changed the default delay notification sensitivity for new connections from Moderate sensitivity (previously called Standard sensitivity) to Low sensitivity. With this change, delay notifications will trigger later, at least 60 minutes after the expected sync time, or longer depending on the connection's average sync duration, instead of a minimum of 30 minutes under the previous default.
This reduces notification noise for transient delays, which typically resolve on their own within minutes. Delays that indicate a real problem will still generate a notification.
Existing connections are not affected by this change. You can adjust the delay notification sensitivity for any connection in its Settings tab.
Lite Connectors
Lite connectors are now available for the following sources:
Logs
Dynatrace External Logging
We now support Dynatrace as an external logging service. You can connect Dynatrace at both the account and destination levels to collect and query your Fivetran logs. We are gradually rolling out this feature to all accounts.
To set up the Dynatrace logging service, go to Account Settings > General> External Logging, or go to your destination settings in your Fivetran dashboard. For more information, see our Dynatrace Setup Guide.
Managed Data Lake Service
All new connections set up on or after July 22, 2026 preserve null byte characters in string values. Previously, we removed null byte characters before writing string values to the data lake, which could cause differences between the source and destination data.
You can now use Apache Polaris™ credentials with read/write access for your Managed Data Lake Service destinations to manage your Fivetran Catalog and modify table data using supported execution engines.
If you are an Account Administrator or Destination Administrator, you can access these credentials from the Write Credentials tab in your destination details page.
With Polaris credentials that have write access, you can:
- Create, update, and delete schemas and tables
- Read and modify table data, including insert, update, delete, and merge operations
- Manage your catalog without contacting Fivetran Support for routine table management tasks
We are gradually rolling out this change to all existing Managed Data Lake Service destinations.
Apache Polaris is a trademark of the Apache Software Foundation.
Partner SDK
Partner SDK Tester
We have released version 2.26.0706.001 of the Partner SDK Tester. This release includes the following improvements:
- Updated the connector tester to use a form field's default value when no input is provided during Partner SDK configuration prompts.
- Added a message that shows when the connector tester uses a default value.
We have released version 2.26.0706.002 of the Partner SDK Tester. This release includes the following improvements:
- Updated the destination tester to get the batch file format from the
CapabilitiesRPC instead of defaulting to CSV. - Added validation for unsupported batch file formats returned by the
CapabilitiesRPC.
Sunset Connectors
AVEVA PI
We have sunset the AVEVA PI connector.
Effective July 1, 2026, we no longer support the creation of new AVEVA PI connections. Existing AVEVA PI connections will stop syncing on July 23, 2026.
Delighted
We have sunset the Delighted connector due to the deprecation of the Delighted API.
Effective July 1, 2026, we no longer support the creation of new Delighted connections. Existing Delighted connections will be paused.
Transformations for dbt Core
Automatic dbt deps setting
We've added a new Automatically run dbt deps toggle to the Transformations for dbt Core setup form. The setting is enabled by default.
When enabled, Fivetran automatically runs the dbt deps service command before transformation runs if your dbt project contains a packages.yml or dependencies.yml file. When disabled, Fivetran skips the automatic dbt deps service command. Explicit dbt deps commands in your transformation jobs still run.
You can disable this setting if you manage dbt packages manually or need custom workarounds for package issues at any time. To disable the setting:
- In the Fivetran dashboard, click Transformations.
- Click Manage projects.
- In the transformation list, click the three dots on the right side of the relevant dbt project.
- Click Edit connection settings.
- Set the Automatically run dbt deps toggle to off.
- Click Save & Test.
Schema changes
AdRoll
We have added new dimension columns to the ALL_ADS, ALL_ADGROUPS, ALL_CAMPAIGNS, and ALL_ADVERTISABLES report types. These columns contain additional dimension fields returned by the AdRoll API and can be selected in your connection's Dimensions configuration.
New columns — ALL_ADS
actualStatusStringadcrabEIDadsManagerPermalinkcallToActioncampaignTypechanneldisapprovalReasonfacebookPermalinkinstagramPermalinkisDynamiclabelsStringlinkedInPermalinkpreviewURLremoteStatussyncErrorsyncStatusutmCampaignutmContentutmMediumutmSourceutmTerm
New columns — ALL_ADGROUPS
actualStatusStringadsManagerPermalinkadTypekpiCurrencykpiGoalkpiMetricprocessingStatussignificantFlightEndDatesignificantFlightStartDatesyncErrorsyncStatus
New columns — ALL_CAMPAIGNS
abmTypeactualStatusStringadsManagerPermalinkautomationEIDautomationNameautomationNodeEIDbillingAuthStatusbudgetEndDatebudgetGoalbudgetSettingsStringbudgetStartDatebudgetTypecampaignGroupEIDcampaignGroupNamedisabledfunnelStageisBillableisBudgetBalancingAutomatedisConnectedChannelisFrozenisIntegratedklaviyoFlowEIDklaviyoFlowNamenewsletterSchedulednewsletterScheduledDatenewsletterSendsplaybookEIDplaybookNameplaybookTypeprocessingStatusproxyStrategyEIDproxyStrategyIsFrozenproxyStrategyNameproxyStrategyStatussyncErrorsyncStatustargetingTypeuseCase
New columns — ALL_ADVERTISABLES
businessUnitisAbmCustomer
Algolia
| Table/column | Change type | Old name | New name | Notes | |
|---|---|---|---|---|---|
TOP_FILTER | |||||
| table | New Table | TOP_FILTER | |||
Amazon DSP
We added the ADVERTISER_ID column to the MEASUREMENT_STUDY table.
Apple Search Ads
We have added a new column, country_or_region_serving_state_reasons, to the CAMPAIGN_HISTORY table.
We have added a new column, app_preview_device_with_assets, to the PRODUCT_PAGE_LOCALE table.
Azure DevOps
We have added a new table, TEAM_MEMBER.
We have added the following new tables:
ITERATIONTEAM_CAPACITY_ACTIVITYTEAM_CAPACITY_DAYS_OFF
We have discontinued the TEAM_GROUPS table. We now sync the data for this table into the TEAM_MEMBER table. Be sure to update your downstream queries to reflect these changes.
We are gradually rolling out these changes to all existing connections.
Betterworks
| Table/column | Change type | Old name | New name | Notes | |
|---|---|---|---|---|---|
FEEDBACK_REQUEST | |||||
| column | Discontinued Column | id 🔑 | No longer a primary key. | ||
| column | Primary Key Change | uuid 🔑 | New primary key. | ||
FEEDBACK_REQUEST_QUESTION | |||||
| column | Discontinued Column | feedback_request_id 🔑 | No longer a primary key. | ||
| column | Discontinued Column | id 🔑 | No longer a primary key. | ||
| column | Primary Key Change | index | index 🔑 | Added to primary key. | |
| column | Primary Key Change | feedback_request_uuid 🔑 | New primary key. | ||
FEEDBACK_REQUEST_RESPONSE | |||||
| column | Discontinued Column | feedback_request_id 🔑 | No longer a primary key. | ||
| column | Discontinued Column | id 🔑 | No longer a primary key. | ||
| column | Primary Key Change | index | index 🔑 | Added to primary key. | |
| column | Primary Key Change | feedback_request_uuid 🔑 | New primary key. | ||
FEEDBACK_REQUEST_TEMPLATE_QUESTION | |||||
| column | Discontinued Column | feedback_request_id 🔑 | No longer a primary key. | ||
| column | Primary Key Change | feedback_request_uuid 🔑 | New primary key. | ||
Braze
We have added a new table, CANVAS_STEP_PROGRESSION_EVENT.
Brex
| Table/column | Change type | Old name | New name | Notes | |
|---|---|---|---|---|---|
LINKED_ACCOUNT | |||||
| table | New Table | LINKED_ACCOUNT | |||
TRIPS | |||||
| table | New Table | TRIPS | |||
TRIPS_BOOKING | |||||
| table | New Table | TRIPS_BOOKING | |||
Buildkite
| Table/column | Change type | Old name | New name | Notes | |
|---|---|---|---|---|---|
BUILD | |||||
| column | New Column | organization_slug | |||
BUILD_JOB | |||||
| column | New Column | retried_by | |||
| column | New Column | retry_source_job_id | |||
| column | New Column | retry_source_type | |||
| column | New Column | step_id | |||
| column | New Column | step_signature_algorithm | |||
| column | New Column | step_signature_signed_fields | |||
| column | New Column | step_signature_value | |||
PIPELINE | |||||
| column | New Column | organization_slug | |||
Cornerstone
| Table/column | Change type | Old name | New name | Notes | |
|---|---|---|---|---|---|
ASSESSMENT_TEST | |||||
| table | New Table | ASSESSMENT_TEST | |||
CULTURE_CORE | |||||
| table | New Table | CULTURE_CORE | |||
CURRICULUM_STRUCTURE_CORE | |||||
| table | New Table | CURRICULUM_STRUCTURE_CORE | |||
GOAL | |||||
| column | Discontinued Column | active_flag | |||
| column | Discontinued Column | aligned_with | |||
| column | Discontinued Column | categories_list | |||
| column | Discontinued Column | created_by_id | |||
| column | Discontinued Column | created_by_name | |||
| column | Discontinued Column | deleted_flag | |||
| column | Discontinued Column | difficulty_to_achieve_title | |||
| column | Discontinued Column | marked_as_final | |||
| column | Discontinued Column | marked_as_final_date | |||
| column | Discontinued Column | num_attachment | |||
| column | Discontinued Column | parent_goal_title | |||
| column | Discontinued Column | perspective_title | |||
| column | Discontinued Column | status_title | |||
| column | Discontinued Column | target_date | |||
| column | Discontinued Column | visible_to_others | |||
| column | New Column | compatibility_goal_status_id | |||
| column | New Column | due_date | |||
| column | New Column | is_active | |||
| column | New Column | is_marked_as_final | |||
| column | New Column | is_visible_to_others | |||
| column | New Column | last_touched_date_utc | |||
| column | New Column | parent_goal_id | |||
| column | New Column | progress_status_id | |||
| column | New Column | reference | |||
| column | New Column | type_id | |||
JOB_REQUISITION_TARGET_OU_CORE | |||||
| table | New Table | JOB_REQUISITION_TARGET_OU_CORE | |||
REQUISITION_CF | |||||
| column | New Column | last_touched_date_utc | |||
REQUISITION_LOCATION | |||||
| table | Discontinued Table | REQUISITION_LOCATION | Data is available in the JOB_REQUISITION_TARGET_OU_CORE table. | ||
TEST | |||||
| table | Discontinued Table | TEST | Data is available in the ASSESSMENT_TEST table. | ||
TRAINING | |||||
| column | Discontinued Column | classification | |||
| column | Discontinued Column | electronic_signature_required | |||
| column | Discontinued Column | is_ojt_enabled | |||
| column | Discontinued Column | keywords | |||
| column | Discontinued Column | latest_version | |||
| column | Discontinued Column | lo_billing_entity_name | |||
| column | Discontinued Column | lo_create_dt | |||
| column | Discontinued Column | lo_created_by | |||
| column | Discontinued Column | lo_created_by_fullname | |||
| column | Discontinued Column | lo_created_by_user_ref | |||
| column | Discontinued Column | lo_currency_code | |||
| column | Discontinued Column | lo_currency_symbol | |||
| column | Discontinued Column | lo_email_option_id | |||
| column | Discontinued Column | lo_end_dt | |||
| column | Discontinued Column | lo_eval_01 | |||
| column | Discontinued Column | lo_eval_02 | |||
| column | Discontinued Column | lo_eval_03 | |||
| column | Discontinued Column | lo_instructor | |||
| column | Discontinued Column | lo_language | |||
| column | Discontinued Column | lo_material_status | |||
| column | Discontinued Column | lo_material_type_active | |||
| column | Discontinued Column | lo_object_id | |||
| column | Discontinued Column | lo_owners_ids | |||
| column | Discontinued Column | lo_postwork_titles | |||
| column | Discontinued Column | lo_prework_titles | |||
| column | Discontinued Column | lo_provider | |||
| column | Discontinued Column | lo_provider_active | |||
| column | Discontinued Column | lo_provider_address_1 | |||
| column | Discontinued Column | lo_provider_address_2 | |||
| column | Discontinued Column | lo_provider_city | |||
| column | Discontinued Column | lo_provider_mailstop | |||
| column | Discontinued Column | lo_provider_state | |||
| column | Discontinued Column | lo_provider_zip | |||
| column | Discontinued Column | lo_publication_created_by | |||
| column | Discontinued Column | lo_publication_created_date | |||
| column | Discontinued Column | lo_publication_published | |||
| column | Discontinued Column | lo_ref | |||
| column | Discontinued Column | lo_root_id | |||
| column | Discontinued Column | lo_root_ref | |||
| column | Discontinued Column | lo_root_title | |||
| column | Discontinued Column | lo_secondary_training_provider | |||
| column | Discontinued Column | lo_skills | |||
| column | Discontinued Column | lo_status | |||
| column | Discontinued Column | lo_timezone_code | |||
| column | Discontinued Column | lo_title | |||
| column | Discontinued Column | lo_training_ref | |||
| column | Discontinued Column | lo_type | |||
| column | Discontinued Column | lo_type_id | |||
| column | Discontinued Column | object_type | |||
| column | New Column | effective_eval_01_id | |||
| column | New Column | effective_eval_02_id | |||
| column | New Column | effective_eval_03_id | |||
| column | New Column | email_option_id | |||
| column | New Column | gcid | |||
| column | New Column | is_multi_assignment_allowed | |||
| column | New Column | is_multi_request_allowed | |||
| column | New Column | is_multi_request_orig_approval_applied | |||
| column | New Column | lo_create_date | |||
| column | New Column | lo_end_date | |||
| column | New Column | proficiency_level | |||
| column | New Column | provider_reference | |||
| column | New Column | publication_create_date | |||
| column | New Column | publication_created_by_user_id | |||
| column | New Column | reference | |||
| column | New Column | source_object_id | |||
| column | New Column | thumbnail_location | |||
TRAINING_ASSIGNMENT_CORE | |||||
| table | New Table | TRAINING_ASSIGNMENT_CORE | |||
TRAINING_ASSIGNMENT_USER | |||||
| column | Discontinued Column | pu_is_dymanic_remove | |||
| column | Discontinued Column | pu_object_id | |||
| column | Discontinued Column | pu_proxy_id 🔑 | No longer a primary key. | ||
| column | Discontinued Column | pu_user_id 🔑 | No longer a primary key. | ||
| column | New Column | is_dynamic_removed | |||
| column | New Column | last_touched_date_utc | |||
| column | Primary Key Change | proxy_id 🔑 | New primary key. | ||
| column | Primary Key Change | user_id 🔑 | New primary key. | ||
TRAINING_AVAILABILITY_BY_OU_CORE | |||||
| table | New Table | TRAINING_AVAILABILITY_BY_OU_CORE | |||
TRAINING_LOCAL_CORE | |||||
| table | New Table | TRAINING_LOCAL_CORE | |||
TRAINING_MATERIAL_TYPE_CORE | |||||
| table | New Table | TRAINING_MATERIAL_TYPE_CORE | |||
TRAINING_MATERIAL_TYPE_LOCAL_CORE | |||||
| table | New Table | TRAINING_MATERIAL_TYPE_LOCAL_CORE | |||
TRAINING_PROVIDER_CORE | |||||
| table | New Table | TRAINING_PROVIDER_CORE | |||
TRAINING_TYPE_CORE | |||||
| table | New Table | TRAINING_TYPE_CORE | |||
TRAINING_TYPE_LOCAL_CORE | |||||
| table | New Table | TRAINING_TYPE_LOCAL_CORE | |||
TRANSCRIPT | |||||
| column | Discontinued Column | archived | |||
| column | Discontinued Column | exempt_approver_reason | |||
| column | Discontinued Column | exempt_reason | |||
| column | Discontinued Column | is_archive | |||
| column | Discontinued Column | last_touched_dt_utc | |||
| column | Discontinued Column | training_purpose | |||
| column | Discontinued Column | training_purpose_category | |||
| column | Discontinued Column | user_lo_assignor | |||
| column | Discontinued Column | user_lo_assignor_ref | |||
| column | Discontinued Column | user_lo_num_attempts | |||
| column | Discontinued Column | user_lo_status_group_id | |||
| column | Discontinued Column | user_lo_timezone_code | |||
| column | New Column | is_hidden_in_ui | |||
| column | New Column | last_touched_date_utc | |||
| column | New Column | license_expiration_dt | |||
| column | New Column | license_id | |||
| column | New Column | license_status_id | |||
| column | New Column | training_purpose_category_id | |||
| column | New Column | training_purpose_id | |||
TRANSCRIPT_DELIVERY_METHOD_LOCAL_CORE | |||||
| table | New Table | TRANSCRIPT_DELIVERY_METHOD_LOCAL_CORE | |||
TRANSCRIPT_STATUS_LOCAL_CORE | |||||
| table | New Table | TRANSCRIPT_STATUS_LOCAL_CORE | |||
USERS | |||||
| column | Discontinued Column | address_1 | |||
| column | Discontinued Column | address_2 | |||
| column | Discontinued Column | appr_id | |||
| column | Discontinued Column | appr_mailstop | |||
| column | Discontinued Column | appr_name_first | |||
| column | Discontinued Column | appr_name_last | |||
| column | Discontinued Column | appr_ref | |||
| column | Discontinued Column | approval | |||
| column | Discontinued Column | city | |||
| column | Discontinued Column | company_no | |||
| column | Discontinued Column | country | |||
| column | Discontinued Column | hire_date_last | |||
| column | Discontinued Column | hire_date_orig | |||
| column | Discontinued Column | i_mgr_email | |||
| column | Discontinued Column | i_mgr_id | |||
| column | Discontinued Column | i_mgr_name_first | |||
| column | Discontinued Column | i_mgr_name_last | |||
| column | Discontinued Column | indirect_manager_name | |||
| column | Discontinued Column | indirect_manager_ref | |||
| column | Discontinued Column | is_user_absent | |||
| column | Discontinued Column | mailstop | |||
| column | Discontinued Column | mgr_email | |||
| column | Discontinued Column | mgr_id | |||
| column | Discontinued Column | mgr_mailstop | |||
| column | Discontinued Column | mgr_name_first | |||
| column | Discontinued Column | mgr_name_last | |||
| column | Discontinued Column | mgr_ref | |||
| column | Discontinued Column | state | |||
| column | Discontinued Column | tax_override | |||
| column | Discontinued Column | tax_override_unit | |||
| column | Discontinued Column | termination_type | |||
| column | Discontinued Column | type | |||
| column | Discontinued Column | vat_number | |||
| column | Discontinued Column | zip | |||
| column | New Column | absent | |||
| column | New Column | address_id | |||
| column | New Column | approvals | |||
| column | New Column | approver_id | |||
| column | New Column | company_number | |||
| column | New Column | indirect_manager_id | |||
| column | New Column | last_hire_date | |||
| column | New Column | manager_id | |||
| column | New Column | original_hire_date | |||
| column | New Column | type_id | |||
Employment Hero
| Table/column | Change type | Old name | New name | Notes | |
|---|---|---|---|---|---|
EMPLOYEE | |||||
| column | New Column | abn | |||
| column | New Column | business_detail_business_type | |||
| column | New Column | business_detail_country | |||
| column | New Column | business_detail_number | |||
| column | New Column | independent_contractor | |||
| column | New Column | trading_name | |||
| column | New Column | uk_tax_and_national_insurance_id | |||
| column | New Column | uk_tax_and_national_insurance_number | |||
| column | New Column | uk_tax_and_national_insurance_unique_taxpayer_reference | |||
EMPLOYEE_HISTORY | |||||
| column | New Column | contract_type | |||
| column | New Column | industry_standard_job_title | |||
FireHydrant
| Table/column | Change type | Old name | New name | Notes | |
|---|---|---|---|---|---|
POST_MORTEM_REPORT | |||||
| table | Discontinued Table | POST_MORTEM_REPORT | Data is available in the RETROSPECTIVE_REPORT table. | ||
POST_MORTEM_REPORT_ADDITIONAL_DETAIL | |||||
| table | Discontinued Table | POST_MORTEM_REPORT_ADDITIONAL_DETAIL | |||
POST_MORTEM_REPORT_QUESTION | |||||
| table | Discontinued Table | POST_MORTEM_REPORT_QUESTION | |||
POST_MORTEM_REPORT_QUESTION_AVAILABLE_OPTION | |||||
| table | Discontinued Table | POST_MORTEM_REPORT_QUESTION_AVAILABLE_OPTION | |||
POST_MORTEM_REPORT_QUESTION_CONVERSATION | |||||
| table | Discontinued Table | POST_MORTEM_REPORT_QUESTION_CONVERSATION | |||
POST_MORTEM_REPORT_TAG_LIST | |||||
| table | Discontinued Table | POST_MORTEM_REPORT_TAG_LIST | |||
RETROSPECTIVE_REPORT | |||||
| table | New Table | RETROSPECTIVE_REPORT | |||
RETROSPECTIVE_REPORT_FIELD | |||||
| table | New Table | RETROSPECTIVE_REPORT_FIELD | |||
RETROSPECTIVE_REPORT_SECTION | |||||
| table | New Table | RETROSPECTIVE_REPORT_SECTION | |||
Freshservice
We've added the following new tables:
SLA_POLICY- Contains the SLA policies configured on the account.SLA_POLICY_TARGET- Contains the target definitions for each SLA policy.SLA_POLICY_ESCALATION- Contains the escalation rules for each SLA policy.
We have added a new column, sla_policy_id, to the TICKET table.
We are gradually rolling out this change to all existing connections.
Front
We have added new custom_* columns to the following tables to sync data from custom fields:
CONVERSATIONINBOXTEAMMATE
Genesys
| Table/column | Change type | Old name | New name | Notes | |
|---|---|---|---|---|---|
ANALYTIC_USER_DETAIL_PRIMARY_PRESENCE | |||||
| column | Discontinued Column | index 🔑 | No longer a primary key. | ||
| column | Primary Key Change | _fivetran_id 🔑 | New primary key. | ||
| column | Primary Key Change | user_id 🔑 | New primary key. | ||
ANALYTIC_USER_DETAIL_ROUTING_STATUS | |||||
| column | Discontinued Column | index 🔑 | No longer a primary key. | ||
| column | Primary Key Change | _fivetran_id 🔑 | New primary key. | ||
| column | Primary Key Change | user_id 🔑 | New primary key. | ||
GitLab
| Table/column | Change type | Old name | New name | Notes | |
|---|---|---|---|---|---|
MERGE_REQUEST_APPROVAL | |||||
| table | New Table | MERGE_REQUEST_APPROVAL | |||
MERGE_REQUEST_COMMIT | |||||
| table | New Table | MERGE_REQUEST_COMMIT | |||
PROJECT_MERGE_REQUEST_APPROVED_BY | |||||
| table | New Table | PROJECT_MERGE_REQUEST_APPROVED_BY | |||
PROJECT_MERGE_REQUEST_ELIGIBLE_APPROVER | |||||
| table | New Table | PROJECT_MERGE_REQUEST_ELIGIBLE_APPROVER | |||
PROJECT_MERGE_REQUEST_USER | |||||
| table | New Table | PROJECT_MERGE_REQUEST_USER | |||
Gladly
| Table/column | Change type | Old name | New name | Notes | |
|---|---|---|---|---|---|
CONVERSATION_SIDE_KICK_EXPORT_REPORT | |||||
| table | New Table | CONVERSATION_SIDE_KICK_EXPORT_REPORT | |||
Intercom
We have added two new tables, MESSAGE_OPEN and SERIES_DISENGAGEMENT.
We have added a new column, parent_id, to the ARTICLE_HISTORY table.
We have added a new table, ARTICLE_PARENT, to store the parent IDs associated with each article.
Ironclad
| Table/column | Change type | Old name | New name | Notes | |
|---|---|---|---|---|---|
APPROVAL_REQUEST | |||||
| column | Primary Key Change | workflow_id 🔑 | workflow_id | No longer a primary key. | |
RECORD | |||||
| column | New Column | _fivetran_file_path | |||
Jira
We now capture deletes for the ASSET_OBJECT table using the _fivetran_deleted column. Perform a resync to backfill historical data.
LinkedIn Ad Analytics
We've added a new table, DOCUMENT. The table contains document media assets referenced by posts, including the download URL, its expiration time, owner, and processing status.
We've added a new table IMAGE. The table contains metadata about images used in LinkedIn Ads, including the image ID, owner, download URL, download URL expiry, status, aspect ratio, and alt text.
Loopio
| Table/column | Change type | Old name | New name | Notes | |
|---|---|---|---|---|---|
LIBRARY_ENTRIES | |||||
| column | New Column | alert_text | |||
| column | New Column | usage_counts_project_usage_count | |||
| column | New Column | usage_counts_times_copied | |||
| column | New Column | usage_counts_total_usage_count | |||
PROJECT_ENTRIES | |||||
| column | New Column | answer_text | |||
| column | New Column | assignee_id | |||
| column | New Column | assignee_type | |||
| column | New Column | question | |||
| column | New Column | reviewer_id | |||
| column | New Column | reviewer_type | |||
PROJECT_ENTRIES_COMPLIANCE_ANSWER | |||||
| column | New Column | label | |||
PROJECT_SUMMARY | |||||
| column | New Column | completed_date | |||
| column | New Column | template_id | |||
Mailchimp
We have added a new column, opens_proxy_excluded_unique_opens, to the CAMPAIGN_REPORT table.
Microsoft Teams
| Table/column | Change type | Old name | New name | Notes | |
|---|---|---|---|---|---|
CHANNEL | |||||
| table | New Table | CHANNEL | |||
CHANNEL_MESSAGE | |||||
| table | New Table | CHANNEL_MESSAGE | |||
CHANNEL_MESSAGE_MENTION | |||||
| table | New Table | CHANNEL_MESSAGE_MENTION | |||
CHANNEL_MESSAGE_REACTION | |||||
| table | New Table | CHANNEL_MESSAGE_REACTION | |||
CHANNEL_MESSAGE_REPLY | |||||
| table | New Table | CHANNEL_MESSAGE_REPLY | |||
CHANNEL_MESSAGE_REPLY_MENTION | |||||
| table | New Table | CHANNEL_MESSAGE_REPLY_MENTION | |||
CHANNEL_MESSAGE_REPLY_REACTION | |||||
| table | New Table | CHANNEL_MESSAGE_REPLY_REACTION | |||
CHAT | |||||
| table | New Table | CHAT | |||
CHAT_MESSAGE | |||||
| table | New Table | CHAT_MESSAGE | |||
TEAM | |||||
| table | New Table | TEAM | |||
USERS | |||||
| table | New Table | USERS | |||
OpenAI
We have added the following new tables to store Codex Enterprise Analytics API data:
CODEX_CODE_REVIEWCODEX_CODE_REVIEW_RESPONSECODEX_USAGECODEX_USAGE_CLIENTCODEX_USAGE_MODEL
PagerDuty
| Table/column | Change type | Old name | New name | Notes | |
|---|---|---|---|---|---|
USER_DELEGATION | |||||
| table | New Table | USER_DELEGATION | |||
USERS_SESSION | |||||
| table | Discontinued Table | USERS_SESSION | Data is available in the USER_DELEGATION table. | ||
Paychex
| Table/column | Change type | Old name | New name | Notes | |
|---|---|---|---|---|---|
COMPANY_CHECK | |||||
| table | New Table | COMPANY_CHECK | |||
COMPANY_CHECK_DEDUCTION | |||||
| table | New Table | COMPANY_CHECK_DEDUCTION | |||
COMPANY_CHECK_EARNING | |||||
| table | New Table | COMPANY_CHECK_EARNING | |||
COMPANY_CHECK_INFORMATIONAL | |||||
| table | New Table | COMPANY_CHECK_INFORMATIONAL | |||
COMPANY_CHECK_TAX | |||||
| table | New Table | COMPANY_CHECK_TAX | |||
PAY_PERIOD | |||||
| table | New Table | PAY_PERIOD | |||
WORKER_CUSTOM_FIELD | |||||
| table | New Table | WORKER_CUSTOM_FIELD | |||
WORKER_TIME_OFF | |||||
| table | New Table | WORKER_TIME_OFF | |||
Personio
| Table/column | Change type | Old name | New name | Notes | |
|---|---|---|---|---|---|
ATTENDANCE | |||||
| column | Discontinued Column | break | |||
| column | Discontinued Column | employee_id | |||
| column | Discontinued Column | is_holiday | |||
| column | Discontinued Column | is_on_time_off | |||
| column | New Column | created_at | |||
| column | New Column | is_auto_generated | |||
| column | New Column | person_id | |||
PROJECT | |||||
| column | Discontinued Column | attributes_active | |||
| column | Discontinued Column | attributes_created_at | |||
| column | Discontinued Column | attributes_name | |||
| column | Discontinued Column | attributes_updated_at | |||
| column | New Column | assigned_to_all | |||
| column | New Column | billable | |||
| column | New Column | client_name | |||
| column | New Column | cost_center_id | |||
| column | New Column | created_at | |||
| column | New Column | description | |||
| column | New Column | end_date | |||
| column | New Column | name | |||
| column | New Column | parent_project_id | |||
| column | New Column | project_code | |||
| column | New Column | project_type | |||
| column | New Column | start_date | |||
| column | New Column | status | |||
| column | New Column | updated_at | |||
REPORT_EMPLOYEE_ATTRIBUTE_ABSENCE_OVERVIEW | |||||
| table | New Table | REPORT_EMPLOYEE_ATTRIBUTE_ABSENCE_OVERVIEW | |||
REPORT_EMPLOYEE_ATTRIBUTE_ABSENCE_PERIOD | |||||
| table | New Table | REPORT_EMPLOYEE_ATTRIBUTE_ABSENCE_PERIOD | |||
REPORT_EMPLOYEE_ATTRIBUTE_COST_CENTER | |||||
| table | New Table | REPORT_EMPLOYEE_ATTRIBUTE_COST_CENTER | |||
REPORT_EMPLOYEE_ATTRIBUTE_DURATION | |||||
| table | New Table | REPORT_EMPLOYEE_ATTRIBUTE_DURATION | |||
REPORT_EMPLOYEE_ATTRIBUTE_ENTITY | |||||
| table | New Table | REPORT_EMPLOYEE_ATTRIBUTE_ENTITY | |||
REPORT_EMPLOYEE_ATTRIBUTE_PERFORMANCE_KPI | |||||
| table | New Table | REPORT_EMPLOYEE_ATTRIBUTE_PERFORMANCE_KPI | |||
REPORT_EMPLOYEE_ATTRIBUTE_PERFORMANCE_TARGET | |||||
| table | New Table | REPORT_EMPLOYEE_ATTRIBUTE_PERFORMANCE_TARGET | |||
REPORT_EMPLOYEE_ATTRIBUTE_TEXT | |||||
| table | New Table | REPORT_EMPLOYEE_ATTRIBUTE_TEXT | |||
Picqer
| Table/column | Change type | Old name | New name | Notes | |
|---|---|---|---|---|---|
PICKLIST_LOCATION | |||||
| column | New Column | amount_picked | |||
| column | New Column | picklist_product_location_id | |||
Pinpoint
| Table/column | Change type | Old name | New name | Notes | |
|---|---|---|---|---|---|
APPLICATION | |||||
| column | Discontinued Column | offers_data | |||
APPLICATION_OFFER_DATA | |||||
| table | New Table | APPLICATION_OFFER_DATA | |||
CANDIDATE_SURVEY | |||||
| table | New Table | CANDIDATE_SURVEY | |||
CANDIDATES_SURVEY_INCLUDED | |||||
| table | New Table | CANDIDATES_SURVEY_INCLUDED | |||
CUSTOM_ATTRIBUTE | |||||
| table | New Table | CUSTOM_ATTRIBUTE | |||
CUSTOM_ATTRIBUTE_INCLUDED | |||||
| table | New Table | CUSTOM_ATTRIBUTE_INCLUDED | |||
CUSTOM_FIELD | |||||
| table | New Table | CUSTOM_FIELD | |||
CUSTOM_FIELDS_INCLUDED | |||||
| table | New Table | CUSTOM_FIELDS_INCLUDED | |||
OFFER | |||||
| table | New Table | OFFER | |||
Planhat
| Table/column | Change type | Old name | New name | Notes | |
|---|---|---|---|---|---|
CONVERSATION_END_USER | |||||
| column | Primary Key Change | end_user_id 🔑 | end_user_id | No longer a primary key | |
| column | Primary Key Change | index 🔑 | New primary key | ||
PowerReviews Enterprise
| Table/column | Change type | Old name | New name | Notes | |
|---|---|---|---|---|---|
REVIEW | |||||
| column | New Column | merchant_user_id | |||
Productboard
| Table/column | Change type | Old name | New name | Notes | |
|---|---|---|---|---|---|
COMPONENT_CUSTOM_FIELD | |||||
| table | New Table | COMPONENT_CUSTOM_FIELD | |||
COMPONENT_RELATIONSHIP | |||||
| table | New Table | COMPONENT_RELATIONSHIP | |||
COMPONENT_TAG | |||||
| table | New Table | COMPONENT_TAG | |||
CONVERSATION_NOTE | |||||
| table | New Table | CONVERSATION_NOTE | |||
CONVERSATION_NOTE_CONTENT | |||||
| table | New Table | CONVERSATION_NOTE_CONTENT | |||
CONVERSATION_NOTE_RELATIONSHIP | |||||
| table | New Table | CONVERSATION_NOTE_RELATIONSHIP | |||
CONVERSATION_NOTE_TAG | |||||
| table | New Table | CONVERSATION_NOTE_TAG | |||
CUSTOM_FIELD | |||||
| table | Discontinued Table | CUSTOM_FIELD | |||
CUSTOM_FIELD_VALUE | |||||
| table | Discontinued Table | CUSTOM_FIELD_VALUE | |||
FEATURE_CUSTOM_FIELD | |||||
| table | New Table | FEATURE_CUSTOM_FIELD | |||
FEATURE_RELATIONSHIP | |||||
| table | New Table | FEATURE_RELATIONSHIP | |||
FEATURE_RELEASE_ASSIGNMENT | |||||
| table | Discontinued Table | FEATURE_RELEASE_ASSIGNMENT | |||
FEATURE_STATUS | |||||
| table | Discontinued Table | FEATURE_STATUS | |||
FEATURE_TAG | |||||
| table | New Table | FEATURE_TAG | |||
FEATURE_TEAM | |||||
| table | New Table | FEATURE_TEAM | |||
MEMBER_ACTIVITY | |||||
| table | New Table | MEMBER_ACTIVITY | |||
NOTE | |||||
| table | Discontinued Table | NOTE | Data now available in the CONVERSATION_NOTE, OPPORTUNITY_NOTE, and TEXT_NOTE tables. | ||
NOTE_COMMENT | |||||
| table | Discontinued Table | NOTE_COMMENT | |||
NOTE_FEATURE | |||||
| table | Discontinued Table | NOTE_FEATURE | |||
NOTE_FOLLOWER | |||||
| table | Discontinued Table | NOTE_FOLLOWER | |||
NOTE_TAG | |||||
| table | Discontinued Table | NOTE_TAG | |||
OBJECTIVE_CUSTOM_FIELD | |||||
| table | New Table | OBJECTIVE_CUSTOM_FIELD | |||
OBJECTIVE_RELATIONSHIP | |||||
| table | New Table | OBJECTIVE_RELATIONSHIP | |||
OPPORTUNITY_NOTE | |||||
| table | New Table | OPPORTUNITY_NOTE | |||
OPPORTUNITY_NOTE_RELATIONSHIP | |||||
| table | New Table | OPPORTUNITY_NOTE_RELATIONSHIP | |||
OPPORTUNITY_NOTE_TAG | |||||
| table | New Table | OPPORTUNITY_NOTE_TAG | |||
OPTION | |||||
| table | Discontinued Table | OPTION | |||
PRODUCT_CUSTOM_FIELD | |||||
| table | New Table | PRODUCT_CUSTOM_FIELD | |||
PRODUCT_RELATIONSHIP | |||||
| table | New Table | PRODUCT_RELATIONSHIP | |||
PRODUCT_TAG | |||||
| table | New Table | PRODUCT_TAG | |||
PRODUCT_TEAM | |||||
| table | New Table | PRODUCT_TEAM | |||
RELEASE_CUSTOM_FIELD | |||||
| table | New Table | RELEASE_CUSTOM_FIELD | |||
RELEASE_GROUP_CUSTOM_FIELD | |||||
| table | New Table | RELEASE_GROUP_CUSTOM_FIELD | |||
RELEASE_GROUP_RELATIONSHIP | |||||
| table | New Table | RELEASE_GROUP_RELATIONSHIP | |||
RELEASE_RELATIONSHIP | |||||
| table | New Table | RELEASE_RELATIONSHIP | |||
TEAM | |||||
| table | New Table | TEAM | |||
TEXT_NOTE | |||||
| table | New Table | TEXT_NOTE | |||
TEXT_NOTE_RELATIONSHIP | |||||
| table | New Table | TEXT_NOTE_RELATIONSHIP | |||
TEXT_NOTE_TAG | |||||
| table | New Table | TEXT_NOTE_TAG | |||
USERS_TEAM | |||||
| table | New Table | USERS_TEAM | |||
Recharge
We have added the following new tables:
COLLECTIONCOLLECTION_PRODUCTPRODUCTPRODUCT_OPTIONPRODUCT_OPTION_VALUEPRODUCT_VARIANT
We are gradually rolling out these changes to all existing connections.
Recurly
We have made the following schema changes to the Recurly connector.
We've added the following new tables:
EXTERNAL_ACCOUNT_HISTORYEXTERNAL_SUBSCRIPTIONEXTERNAL_SUBSCRIPTION_PAYMENT_PHASEGIFT_CARDINVOICE_LINE_ITEMINVOICE_TAX_DETAILINVOICE_TRANSACTION_HISTORYLINE_ITEM_TAX_DETAILPLAN_ADD_ON_CURRENCY_PERCENTAGE_TIERPLAN_ADD_ON_TIER_HISTORYPLAN_SETUP_FEESSUBSCRIPTION_CREDIT_INVOICESUBSCRIPTION_RAMP_INTERVALTRANSACTION_FRAUD_INFO_RISK_RULES_TRIGGEREDUSAGE_RECORDUSAGE_RECORD_PERCENTAGE_TIERSUSAGE_RECORD_TIERS
We have added the following new columns to the ACCOUNT_HISTORY table:
account_geo_codebill_datedunning_campaign_identity_use_codehas_active_subscriptionhas_canceled_subscriptionhas_future_subscriptionhas_live_subscriptionhas_past_due_invoicehas_paused_subscriptioninvoice_template_idoverride_business_entity_idpreferred_time_zone
We have added the following new columns to the BILLING_INFO_HISTORY table:
account_geo_codebackup_payment_methodbill_datebilling_geo_codeentity_use_codehas_past_due_invoicepayment_gateway_referencespayment_method_account_typepayment_method_billing_agreement_idpayment_method_card_network_preferencepayment_method_cc_bin_countrypayment_method_funding_sourcepayment_method_gateway_attributes_account_referencepayment_method_gateway_codepayment_method_last_twopayment_method_name_on_accountpayment_method_routing_numberpayment_method_routing_number_bankpayment_method_usernameprimary_payment_method
We have added the following new columns to the SHIPPING_ADDRESS_HISTORY table:
geo_codestreet_1street_2
We have added the available_credit_amount and processing_prepayment_amount column to the ACCOUNT_BALANCE_HISTORY table.
We have added a new column, acquired_at, to the ACCOUNT_ACQUISITION_HISTORY table.
We have added a new column, subscription_id, to the COUPON_REDEMPTION_HISTORY table.
We have added the following new columns to the INVOICE_HISTORY table:
address_geo_codeaddress_name_on_accountaddress_phoneaddress_street_1address_street_2billing_info_idbusiness_entity_idcredit_paymentscustomer_notesdunning_campaign_iddunning_events_sentfinal_dunning_eventgateway_codehas_more_line_itemsobjectoriginreference_only_currency_conversion_currencyreference_only_currency_conversion_datereference_only_currency_conversion_ratereference_only_currency_conversion_sourcereference_only_currency_conversion_subtotal_in_centsreference_only_currency_conversion_tax_in_centsrefundable_amountshipping_address_geo_codeshipping_address_idshipping_address_nicknameshipping_address_objectshipping_address_street_1shipping_address_street_2shipping_address_vat_numberterms_and_conditionsused_tax_serviceuuidvat_numbervat_reverse_charge_notes
We have added the following new columns to the LINE_ITEM_HISTORY table:
avalara_service_typeavalara_transaction_typebill_for_account_iddestination_tax_address_sourceexternal_skuharmonized_system_codeitem_codeitem_idliability_gl_account_codeorigin_tax_address_sourceperformance_obligation_idquantity_decimalrefunded_quantity_decimalrevenue_gl_account_codeshipping_address_idtax_inclusiveunit_amount_decimal
We have added the following new columns to the PLAN_ADD_ON_HISTORY table:
add_on_typeavalara_service_typeavalara_transaction_typeexternal_skuharmonized_system_codeitem_codeitem_descriptionitem_iditem_nameitem_objectitem_stateliability_gl_account_idmeasured_unit_idperformance_obligation_idrevenue_gl_account_idusage_calculation_typeusage_percentageusage_timeframeusage_type
We have added the tax_inclusive and unit_amount_decimal columns to the PLAN_ADD_ON_CURRENCY_HISTORY table.
We have added the following new columns to the PLAN_HISTORY table:
allow_any_item_on_subscriptionsavalara_service_typeavalara_transaction_typedunning_campaign_idharmonized_system_codehosted_page_bypass_confirmationhosted_page_cancel_urlhosted_page_display_quantityhosted_page_success_urlliability_gl_account_idperformance_obligation_idpricing_modelrevenue_gl_account_idrevenue_schedule_typesetup_fee_liability_gl_account_idsetup_fee_performance_obligation_idsetup_fee_revenue_gl_account_idsetup_fee_revenue_schedule_typetrial_requires_billing_infovertex_transaction_type
We have added the price_segment_id and tax_inclusive columns to the PLAN_CURRENCY_HISTORY table.
We have added the following new columns to the SUBSCRIPTION_HISTORY table:
action_resultactive_invoice_idbank_account_authorized_atbilling_info_idbusiness_entity_idcredit_application_policy_modegateway_codeinvoice_collection_charge_invoice_idnet_terms_typenext_actionprice_segment_idshipping_address_objectshipping_amountshipping_method_codeshipping_method_idshipping_method_nameshipping_method_objecttaxtax_inclusivetotal
We have added the add_on_source and unit_amount_decimal columns to the SUBSCRIPTION_ADD_ON_HISTORY table.
We have added the billing_info_three_d_secure_action_result_token_id and tax_inclusive columns to the SUBSCRIPTION_CHANGE_HISTORY table.
We have added the following new columns to the TRANSACTION table:
action_resultbackup_method_usedbilling_geo_codebilling_phonefraud_info_decisionfraud_info_objectfraud_info_referencefraud_info_scoreinitiatornext_action_typenext_action_valuepayment_method_account_typepayment_method_billing_agreement_idpayment_method_card_network_preferencepayment_method_cc_bin_countrypayment_method_funding_sourcepayment_method_gateway_attribute_account_referencepayment_method_gateway_codepayment_method_last_twopayment_method_name_on_accountpayment_method_routing_numberpayment_method_routing_number_bankpayment_method_username
We have added a new column, bulk_coupon_id, to the BULK_UNIQUE_CODE table.
Reddit Ads
We've added a new table, CLICK_URL_QUERY_PARAMETER. The table contains user-defined query parameters that are appended to the ad's click URL when users click on ads.
Resource Management by Smartsheet
| Table/column | Change type | Old name | New name | Notes | |
|---|---|---|---|---|---|
ASSIGNMENT | |||||
| column | New Column | fixed_hours | |||
SAP Business ByDesign
We have added two new columns, purchase_order_id and purchase_order_uuid, to the PURCHASE_ORDER_ITEM_SCHEDULE_LINE table.
SAP SuccessFactors
| Table/column | Change type | Old name | New name | Notes | |
|---|---|---|---|---|---|
FO_EVENT_REASON | |||||
| table | New Table | FO_EVENT_REASON | |||
PER_GLOBAL_INFO_GBR | |||||
| table | New Table | PER_GLOBAL_INFO_GBR | |||
PER_GLOBAL_INFO_IRL | |||||
| table | New Table | PER_GLOBAL_INFO_IRL | |||
PER_NATIONAL_ID | |||||
| table | New Table | PER_NATIONAL_ID | |||
Shopify
We have made the following schema changes:
- Added a new table,
CATALOG_APP, to map records between theCATALOGandAPPtables - Removed the
catalog_idcolumn from theAPPtable
These changes are currently in beta. We will roll them out to all existing connections on August 3, 2026.
Effective August 6, 2026, we are discontinuing the created_by_description and created_by_title columns from the DISCOUNT_REDEEM_CODE table. You can access the same data in the description and title columns of the APP table by joining DISCOUNT_REDEEM_CODE.created_by_id to APP.id.
We now sync company metafields into the existing metafield table (where owner_resource = 'COMPANY').
Skilljar
| Table/column | Change type | Old name | New name | Notes | |
|---|---|---|---|---|---|
COURSE_TAG | |||||
| table | New Table | COURSE_TAG | |||
LESSON | |||||
| table | New Table | LESSON | |||
PATH_COMPLETION | |||||
| table | New Table | PATH_COMPLETION | |||
PATH_TAG | |||||
| table | New Table | PATH_TAG | |||
QUIZ_COMPLETION | |||||
| table | New Table | QUIZ_COMPLETION | |||
QUIZ_QUESTION | |||||
| table | New Table | QUIZ_QUESTION | |||
QUIZ_QUESTION_ANSWER | |||||
| table | New Table | QUIZ_QUESTION_ANSWER | |||
Sprout Social
We've added following new tables:
CUSTOMER_TOPICCUSTOMER_TOPIC_THEMECUSTOMER_TOPIC_THEMES_GROUP
We have added the following new columns to the TWITTER_PROFILE_POST table:
net_sentiment_scoresentiment_comments_negative_countsentiment_comments_neutral_countsentiment_comments_positive_countsentiment_comments_unclassified_count
We have added the following new columns to the LINKEDIN_PROFILE_POST table:
impressions_uniquenet_sentiment_scorepost_shares_countsentiment_comments_negative_countsentiment_comments_neutral_countsentiment_comments_positive_countsentiment_comments_unclassified_countvideo_view_timevideo_views_uniquevote_count
We have added the following new columns to the FACEBOOK_PROFILE_POST table:
impressions_organicnet_sentiment_scorepost_shares_countsentiment_comments_negative_countsentiment_comments_neutral_countsentiment_comments_positive_countsentiment_comments_unclassified_count
We have added the following new columns to the YOUTUBE_PROFILE_POST table:
net_sentiment_scorepost_shares_countsentiment_comments_negative_countsentiment_comments_neutral_countsentiment_comments_positive_countsentiment_comments_unclassified_count
We have added the following new columns to the INSTAGRAM_PROFILE_POST table:
link_in_bio_clicksnet_sentiment_scorepost_shares_countreels_unique_session_playssentiment_comments_negative_countsentiment_comments_neutral_countsentiment_comments_positive_countsentiment_comments_unclassified_countviews
We have added the following new columns to the TIKTOK_PROFILE_POST table:
net_sentiment_scorepost_shares_countsentiment_comments_negative_countsentiment_comments_neutral_countsentiment_comments_positive_countsentiment_comments_unclassified_count
Square
We have added the following new tables:
CATALOG_CUSTOM_ATTRIBUTE_DEFINITIONCATALOG_CUSTOM_ATTRIBUTE_VALUEDEVICEDEVICE_COMPONENTORDER_CUSTOM_ATTRIBUTEORDER_CUSTOM_ATTRIBUTE_DEFINITIONTEAM_MEMBERTEAM_MEMBER_ASSIGNED_LOCATIONTEAM_MEMBER_WAGETIMECARDTIMECARD_BREAK
We have deprecated the following tables as Square has deprecated the associated objects from its API:
| TABLE | NOTES |
|---|---|
EMPLOYEE | Data is available in the TEAM_MEMBER table. |
EMPLOYEE_WAGE | Data is available in the TEAM_MEMBER_WAGE table. |
SHIFT | Data is available in the TIMECARD table. |
SHIFT_BREAK | Data is available in the TIMECARD_BREAK table. |
We are gradually rolling out these changes to all existing connections. Be sure to update your downstream queries to align with these changes. Failing to do so may lead to missing or incomplete data in your data pipelines. To backfill historical data into the new tables and columns, re-sync the affected tables.
Standard Metrics
| Table/column | Change type | Old name | New name | Notes | |
|---|---|---|---|---|---|
DOCUMENT | |||||
| table | New Table | DOCUMENT | |||
FINANCING_EVENT | |||||
| table | New Table | FINANCING_EVENT | |||
FINANCING_EVENT_CO_INVESTOR | |||||
| table | New Table | FINANCING_EVENT_CO_INVESTOR | |||
FUND | |||||
| table | New Table | FUND | |||
INFORMATION_REQUEST | |||||
| table | New Table | INFORMATION_REQUEST | |||
SECURITY | |||||
| table | New Table | SECURITY | |||
SHARE_CLASS | |||||
| table | New Table | SHARE_CLASS | |||
TRANSACTION | |||||
| table | New Table | TRANSACTION | |||
TikTok Ads
We have deprecated the following prebuilt Reservation Ads report tables because TikTok removed the Reservation report type from their API:
RESERVATION_CAMPAIGN_REPORT_DAILYRESERVATION_ADGROUP_REPORT_DAILYRESERVATION_AD_REPORT_DAILYRESERVATION_CAMPAIGN_REPORT_HOURLYRESERVATION_ADGROUP_REPORT_HOURLYRESERVATION_AD_REPORT_HOURLY
These tables will no longer sync data. We have also removed the ability to create custom Reservation Ads reports, and any existing custom Reservation Ads reports will stop syncing. TikTok recommends using Auction Ads reports instead, which include data for both auction and reservation ad accounts.
We have added the following metrics to custom audience reports:
- Attribute Metrics:
delivery_typeadgroup_display_nameadgroup_scheduleoptimization_preferenceimage_infoad_display_nameidentity_type
We've added a new table, AD_IMAGE. The table links ads to their associated images. We have deprecated the image_ids column in the AD table. Image data now syncs to the new AD_IMAGE table instead.
We have added three new columns, campaign_name, adgroup_name, and campaign_automation_type, to the AD_HISTORY table. We have added the following new columns to the AD_HISTORY table:
adgroup_namecampaign_automation_typecampaign_name
Workday Financial Management
We've added a new table, ALLOCATION_POOL_HIERARCHY. The table contains allocation pool hierarchy definitions used for organizing and categorizing allocation pools.
We've added a new table, ALLOCATION_POOL_HIERARCHY_POOL. The table contains the allocation pool members that belong to each allocation pool hierarchy.
We've added the following new tables:
ALLOCATION_POOL_WORKTAG_OVERRIDE_RULEALLOCATION_POOL_WORKTAG_OVERRIDE_RULE_WORKTAGALLOCATION_POOL_WORKTAG_OVERRIDE_RULE_CONDITION
We've added new tables, ALLOCATION_PLAN, ALLOCATION_PLAN_TIER, ALLOCATION_PLAN_BOOK_CODES_MAPPING, RESTRICTED_TO_JOURNAL_SOURCE, RESTRICTED_TO_POOL_COMPANY, RESTRICTED_TO_LEDGER_TYPE, EXCLUDED_JOURNAL_SOURCE, RESTRICTED_TO_SOURCE_COMPANY, RESTRICTED_TO_LEDGER_ACCOUNT_TYPE, and DEFAULT_OPTIONAL_BALANCING_WORKTAG.
Workday HCM
We have added a new column, city, to the CANDIDATE table.
We have stopped syncing data into the costing_override_worktag_ids column of the WORKER_COSTING_ALLOCATION_DETAIL table since we sync the same data in the id column of the WORKER_COSTING_ALLOCATION_DETAIL_WORKTAG table. You can now discontinue using the costing_override_worktag_ids column in your downstream transformation, and remove it from your destination.
Wrike
| Table/column | Change type | Old name | New name | Notes | |
|---|---|---|---|---|---|
FOLDER_HOURLY_RATE | |||||
| table | New Table | FOLDER_HOURLY_RATE | |||
Zip
| Table/column | Change type | Old name | New name | Notes | |
|---|---|---|---|---|---|
APPROVAL | |||||
| column | Primary Key Change | id 🔑 | id | No longer a primary key. | |
| column | Primary Key Change | _fivetran_id 🔑 | New primary key. | ||
Improvements
Adyen
We have fixed a bug that prevented the exchange_rate_platform_settlement and valid_from columns from syncing in the EXCHANGE_RATE_REPORT table. By default, we will re-sync the EXCHANGE_RATE_REPORT table to backfill the historical data for these columns. This table re-sync will count towards free MAR.
Amazon Selling Partner
We now support table re-sync for our Amazon Selling Partner connector. Previously, we only supported connection-level re-syncs.
Apollo
We have updated the sync strategy for the CONTACT table. We now re-import the table every week to capture updates and deletes. Previously, we only incrementally synced the table to capture new records and updates.
BigQuery destination
All new connections set up on or after July 22, 2026 preserve null byte characters in string values. Previously, we removed null byte characters before writing string values to the destination, which could cause differences between the source and destination data.
Billing Platform
We have fixed an issue where incremental syncs could skip records due to pagination limit. Syncs now use offset-based pagination to ensure all records are fetched reliably. Previously, syncs relied on a pre-computed row count to paginate results within each time window.
Clari
We now use the Export API to sync the data for the following tables and their child tables:
FIELDFORECAST_ENTRYTIME_FRAMETIME_PERIODUSERS
We are gradually rolling out this improvement to all existing connections. This migration requires no action on your part.
Close
The Close connector no longer supports the Hybrid Deployment model.
Confluent Cloud
We now support OAuth 2.0 authentication for the Confluent Cloud connector. You can select your authentication method (API Key or OAuth 2.0) using either one of the following:
- Connection setup form: Use the new Authentication method field.
- Fivetran REST API: Specify either
API_KEYorOAUTHin the newauth_methodparameter.
For more information, see our setup guide and Fivetran REST API.
Databricks destination
All new connections set up on or after July 22, 2026 preserve null byte characters in string values. Previously, we removed null byte characters before writing string values to the destination, which could cause differences between the source and destination data.
We now support external cloud storage for the Email connector. You can choose whether Fivetran stores email attachments in Fivetran-managed storage or in your Amazon S3, Azure Blob Storage, or Google Cloud Storage bucket. For more information, see our setup instructions and REST API documentation.
Expensify
We have improved data integrity for the REPORT_ACTION_LIST and REPORT_APPROVER tables. We now use a 31-day lookback window during incremental syncs for these tables.
File connectors
We have improved how we determine column types for Parquet files that our File connectors sync to your destination. We now read column types directly from the Parquet file's schema metadata. Previously, we inferred them from the actual values in the rows. As a result, you can now find column types that more accurately match the source in your destination schema.
By default, this improvement is available to all new connections created on or after July 21, 2026. We are gradually rolling out this improvement to all existing connections.
FTP
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.
We now support specifying custom primary keys for tables created through dynamic table mapping.
Genesys
We've added a new configuration drop-down, Genesys API to sync Conversation Analytics Data, to the connection setup form. This drop-down menu lets you choose which Genesys API to use for syncing conversation analytics data. The Export API option is selected by default, and this continues to sync the existing conversation analytics tables without changes. If you select the Aggregate Query API option, we use a different Genesys endpoint, and we sync a different set of tables. For more information, see the Genesys connector setup guide.
We've added support for the following new tables, which are synced only if you select Aggregate Query API:
ANALYTICS_CONVERSATION_AGGREGATE_QUERY_DATA_METRICSCONVERSATION_PARTICIPANT_ATTRIBUTEANALYTICS_CONVERSATION_AGGREGATE_QUERY_DETAILSANALYTICS_CONVERSATION_AGGREGATE_QUERY_DETAILS_DIVISIONANALYTICS_CONVERSATION_AGGREGATE_QUERY_DETAILS_KNOWLEDGE_BASE_IDANALYTICS_CONVERSATION_AGGREGATE_QUERY_DETAILS_EVALUATIONANALYTICS_CONVERSATION_AGGREGATE_QUERY_DETAILS_SURVEYANALYTICS_CONVERSATION_AGGREGATE_QUERY_DETAILS_RESOLUTIONANALYTICS_CONVERSATION_AGGREGATE_QUERY_DETAILS_PARTICIPANTANALYTICS_CONVERSATION_AGGREGATE_QUERY_DETAILS_PARTICIPANT_SESSIONANALYTICS_CONVERSATION_AGGREGATE_QUERY_DETAILS_PARTICIPANT_SESSION_SKILL_IDANALYTICS_CONVERSATION_AGGREGATE_QUERY_DETAILS_PARTICIPANT_SESSION_CALLBACK_NUMBERANALYTICS_CONVERSATION_AGGREGATE_QUERY_DETAILS_PARTICIPANT_SESSION_BCCANALYTICS_CONVERSATION_AGGREGATE_QUERY_DETAILS_PARTICIPANT_SESSION_CCANALYTICS_CONVERSATION_AGGREGATE_QUERY_DETAILS_PARTICIPANT_SESSION_DESTINATION_ADDRESSANALYTICS_CONVERSATION_AGGREGATE_QUERY_DETAILS_PARTICIPANT_SESSION_ELIGIBLE_AGENT_COUNTANALYTICS_CONVERSATION_AGGREGATE_QUERY_DETAILS_PARTICIPANT_SESSION_REQUESTED_ROUTINGANALYTICS_CONVERSATION_AGGREGATE_QUERY_DETAILS_PARTICIPANT_SESSION_WAITING_INTERACTION_COUNTSANALYTICS_CONVERSATION_AGGREGATE_QUERY_DETAILS_PARTICIPANT_SESSION_PROPOSED_AGENTANALYTICS_CONVERSATION_AGGREGATE_QUERY_DETAILS_PARTICIPANT_SESSION_AGENT_GROUPANALYTICS_CONVERSATION_AGGREGATE_QUERY_DETAILS_PARTICIPANT_SESSION_MEDIA_ENDPOINT_STATSANALYTICS_CONVERSATION_AGGREGATE_QUERY_DETAILS_PARTICIPANT_SESSION_FLOW_OUTCOMEANALYTICS_CONVERSATION_AGGREGATE_QUERY_DETAILS_PARTICIPANT_SESSION_METRICANALYTICS_CONVERSATION_AGGREGATE_QUERY_DETAILS_PARTICIPANT_SESSION_SEGMENTQUALITY_CONVERSATION_SURVEYQUALITY_CONVERSATION_SURVEY_ANSWER_QUESTION_GROUP_SCOREQUALITY_CONVERSATION_SURVEY_ANSWER_QUESTION_GROUP_QUESTION_SCORE
For a full comparison of tables by API, see the Genesys API to sync Conversation Analytics data documentation.
Gong
We have changed the sync strategy for the following tables:
ANSWERED_SCORECARDCALLMANUAL_CALLTRANSCRIPT
We now re-import only the last 6 months of data during weekly re-imports for these tables. Previously, we re-imported all historical data. We also changed the re-import frequency for the TRANSCRIPT table from monthly to weekly.
Mambu
We have changed our sync strategy for the DEPOSIT_TRANSACTION table. We now incrementally sync the table.
MySQL
We now support AWS IAM database authentication for connections using AWS PrivateLink. To use IAM authentication with AWS PrivateLink, provide your database's Database Endpoint in the connection setup form. For more information, see the Amazon Aurora MySQL setup guide and the RDS MySQL setup guide.
MySQL destination
All new connections set up on or after July 22, 2026 preserve null byte characters in string values. Previously, we removed null byte characters before writing string values to the destination, which could cause differences between the source and destination data.
Oracle
We now support syncing XMLType columns using the Binary Log Reader incremental sync method in Private Preview.
We only support the binary XML storage model. Supplemental logging for primary key columns or all columns must be enabled on the table. Learn more in our Oracle connector documentation.
Pipedrive
We have changed the sync strategy for the ACTIVITY_TYPE table. We now re-import this table once a day instead of incrementally syncing it.
PowerReviews Enterprise
We've fixed an issue where the REVIEW_CUSTOM_QUESTION_NAME table failed to sync. The table will now sync correctly. To backfill historical data for this table, trigger a re-sync on the REVIEW table.
Qualtrics
We now capture deletes for the SURVEY_RESPONSE table. We perform a re-sync of the SURVEY_RESPONSE table every week to capture the deleted records. Previously, we only incrementally synced this table to capture updates.
Salesforce
Creating a Salesforce connection with AWS PrivateLink is not supported with the Fivetran connected app. To use AWS PrivateLink, you must use the External Client App (ECA) flow. To switch to the ECA flow, see How do I switch an existing connection from the Fivetran connected app to the local External Client App (ECA) flow?.
We now re-import the following tables once a week to capture updates and deletes and ensure data integrity:
OPPORTUNITY_LINE_ITEMOPPORTUNITY_LINE_ITEM_SCHEDULEOPPORTUNITY_SPLITQUOTE_LINE_ITEM
Shopify
We now support GraphQL Schema for the Shopify connector. This allows you to use Shopify's GraphQL API to sync data, which provides access to more tables, more granular data, and a structure that is aligned with Shopify's current API direction. Fivetran accounts created on or after August 1, 2025 use the GraphQL schema by default and do not see the toggle.
For other accounts, you can use the GraphQL Schema toggle in the connection setup form to configure it. If you are creating a connection via the Fivetran API or Connect Card, pass is_graphql_enabled: true in your connection configuration to use the GraphQL schema. If left blank, we use the Legacy schema as the default.
This change is applicable for new connections and we are gradually rolling it out to all existing ones. You cannot switch to the GraphQL schema for your existing connection. You must create a new connection with the GraphQL Schema toggle enabled to sync that data.
For more information, see our GraphQL vs Legacy schema documentation.
We now sync app records for discount redeem codes into the APP table. The table now includes records for apps that generate DiscountRedeemCode. This change is currently in beta. We will roll it out to all existing connections on August 3, 2026.
Snowflake destination
All new connections set up on or after July 22, 2026 preserve null byte characters in string values. Previously, we removed null byte characters before writing string values to the destination, which could cause differences between the source and destination data.
SQL Server
Effective July 27, 2026, we have improved Fivetran Teleport Sync change detection for nullable columns in SQL Server connections. New connections created on or after July 27, 2026, distinguish NULL values from non-NULL values when calculating row hashes, improving data consistency in your destination. Existing connections continue to use their current behavior.
SQL Server destination
All new connections set up on or after July 22, 2026 preserve null byte characters in string values. Previously, we removed null byte characters before writing string values to the destination, which could cause differences between the source and destination data.
SugarCRM
We have changed our sync strategy for the PMSE_CASE table. We now incrementally sync this table instead of re-importing it.
Workday Adaptive Planning
Our Workday Adaptive Planning connector now supports token-based authentication, providing enhanced security and a streamlined setup experience. To support this feature, we have added the following fields to the connection setup form:
- Client ID
- Private key
- Host
- Tenant
- Integration System User
For more information, see our setup instructions and REST API documentation.
We are gradually rolling out these changes to all existing connections.
REST API Improvements
Move Connection REST API (Beta)
You can now move connections from one destination group to another using the Move a Connection (Beta) REST API endpoint.