February 2025

Connector SDK

Fivetran Connector SDK

Connector SDK is now generally available. See our Connector SDK documentation for details.

`fivetran-connector-sdk` PyPI package

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

Enhancements and minor bug fixes around requirements.txt verification.
Minor improvements and bug fixes.

We have released version 1.0.0 of the fivetran-connector-sdk PyPI package. This release contains some improvements and bug fixes.

Lite Connectors

Lite connectors are now available for the following sources:

Managed Data Lakes Service

Managed Data Lakes Service provides a flexible way to store and manage data in Amazon S3 and Azure Data Lake Storage (ADLS). It writes data in Parquet format while maintaining metadata for both Iceberg and Delta Lake tables, allowing you to use either format without committing to one. The service supports multiple catalog options, including the Fivetran Iceberg REST Catalog, AWS Glue, and Databricks Unity Catalog, ensuring seamless metadata management and governance.

Read our Managed Data Lakes Service documentation.

Proxy Agent

The Fivetran Proxy Agent connection method is now available for the Azure West US 3 (Phoenix) region. The Proxy Agent allows you to connect Fivetran to your database securely. Installed behind your firewall, it initiates communication with Fivetran, eliminating the need for other complicated networking options.

Review Schema Changes

In the Fivetran dashboard, you can now see a summary of your pending connection schema changes before you commit them. The preview window helps you review the changes and avoid applying the changes you don't need.

Review schema changes

System Keys

Our System Keys feature is now in beta. You can now manage system keys in the dashboard, including the following actions:

Uploading permissions as JSON
Manual creation and editing of permissions
Setting the key expiration date
Key rotation
Key deletion
Disable user keys

Adding System Key in the dashboard

NOTE: Currently, you cannot edit a system key after creating it. The ability to edit system key is planned for rollout when system keys reach general availbility.

DEPRECATION NOTICE: We plan to deprecate user keys. Keep an eye out for an email that will outline the deprecation schedule.

Transformations for dbt Core

Updated dbt Quickstart packages

We have updated the Quickstart packages for the following connectors:

HubSpot to version 0.21.0
Shopify to version 0.16.1
Sage Intacct to version 0.6.0

Schema changes

Apple App Store

We have added the title column to the SALES_SUMMARY_DAILY and SALES_SUMMARY_YEARLY tables.

To capture the title column for existing data, start a historical re-sync for your connection.

Apple Search Ads

We've discontinued support for the lat_off_installs and lat_on_installs fields in the following tables:

AD_GROUP_REPORT
AD_LEVEL_REPORT
CAMPAIGN_REPORT
KEYWORD_REPORT
SEARCH_TERM_REPORT

We've added the following fields to the AD_GROUP_REPORT, AD_LEVEL_REPORT, CAMPAIGN_REPORT,KEYWORD_REPORT, and SEARCH_TERM_REPORT tables:

tap_install_cpi_amount
tap_install_cpi_currency
tap_install_rate
tap_installs
tap_new_downloads
tap_redownloads
total_avg_cpi_amount
total_avg_cpi_currency
total_install_rate
total_installs
total_new_downloads
total_redownloads
view_installs
view_new_downloads
view_redownloads

We're discontinuing support for the following fileds in the the AD_GROUP_REPORT, AD_LEVEL_REPORT, CAMPAIGN_REPORT,KEYWORD_REPORT, and SEARCH_TERM_REPORT tables:

avg_cpa_amount
avg_cpa_currency
conversion_rate
conversions
new_downloads
redownloads

We will continue to support the discontinued fields for another 30 days to give you time to adapt. During those 30 days, the following field pairs will sync the same data:

avg_cpa_amount has the same value as tap_install_cpi_amount
avg_cpa_currency has the same value as tap_install_cpi_currency
conversion_rate has the same value as tap_install_rate
conversions has the same value as tap_installs
new_downloads has the same value as tap_new_downloads
redownloads has the same value as tap_redownloads

After 30 days, we will fully stop supporting the discontinued fields (those without the tap_ prefix, used prior to the release of Apple Search Ads API v5).

For more information, see the Apple Search Ads ERD.

Azure DevOps

We have added the following new tables:

APPROVAL
APPROVAL_STEP
APPROVAL_STEP_HISTORY
BLOCKED_APPROVER
STATUS

Clazar

Effective February 21, 2025 we use a new February 2025 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migrations article for more details.

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
`METERING`
table	New Table			`METERING`

Coupa

We have added a new table, MATCHING_ALLOCATION.

Dialpad

Effective February 25, 2025 we use a new February 2024 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migrations article for more details.

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.

2 total changes • 2 possible breaking changes

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

Genesys

Effective February 11, 2025 we use a new February 2025 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migrations article for more details.

We are updating the connector schema to avoid 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.

23 total changes • 23 possible breaking changes

Table/column	Change type	Old name	Notes
`ANALYTICS_CONVERSATION_AGGREGATE_QUERY_DETAILS`
table	Discontinued Table	`ANALYTICS_CONVERSATION_AGGREGATE_QUERY_DETAILS`	Data is available in the `ANALYTICS_CONVERSATION_DETAILS` table and its child tables.
`ANALYTICS_CONVERSATION_AGGREGATE_QUERY_DETAILS_DIVISION`
table	Discontinued Table	`ANALYTICS_CONVERSATION_AGGREGATE_QUERY_DETAILS_DIVISION`	Data is available in the `ANALYTICS_CONVERSATION_DETAILS_DIVISION` table.
`ANALYTICS_CONVERSATION_AGGREGATE_QUERY_DETAILS_EVALUATION`
table	Discontinued Table	`ANALYTICS_CONVERSATION_AGGREGATE_QUERY_DETAILS_EVALUATION`	Data is available in the `ANALYTICS_CONVERSATION_DETAILS_EVALUATION` table.
`ANALYTICS_CONVERSATION_AGGREGATE_QUERY_DETAILS_KNOWLEDGE_BASE_ID`
table	Discontinued Table	`ANALYTICS_CONVERSATION_AGGREGATE_QUERY_DETAILS_KNOWLEDGE_BASE_ID`	Data is available in the `ANALYTICS_CONVERSATION_DETAILS_KNOWLEDGE_BASE_ID` table.
`ANALYTICS_CONVERSATION_AGGREGATE_QUERY_DETAILS_PARTICIPANT`
table	Discontinued Table	`ANALYTICS_CONVERSATION_AGGREGATE_QUERY_DETAILS_PARTICIPANT`	Data is available in the `ANALYTICS_CONVERSATION_DETAILS_PARTICIPANT` table.
`ANALYTICS_CONVERSATION_AGGREGATE_QUERY_DETAILS_PARTICIPANT_SESSION`
table	Discontinued Table	`ANALYTICS_CONVERSATION_AGGREGATE_QUERY_DETAILS_PARTICIPANT_SESSION`	Data is available in the `ANALYTICS_CONVERSATION_DETAILS_PARTICIPANT_SESSION` table.
`ANALYTICS_CONVERSATION_AGGREGATE_QUERY_DETAILS_PARTICIPANT_SESSION_AGENT_GROUP`
table	Discontinued Table	`ANALYTICS_CONVERSATION_AGGREGATE_QUERY_DETAILS_PARTICIPANT_SESSION_AGENT_GROUP`	Data is available in the `ANALYTICS_CONVERSATION_DETAILS_PARTICIPANT_SESSION_AGENT_GROUP` table.
`ANALYTICS_CONVERSATION_AGGREGATE_QUERY_DETAILS_PARTICIPANT_SESSION_BCC`
table	Discontinued Table	`ANALYTICS_CONVERSATION_AGGREGATE_QUERY_DETAILS_PARTICIPANT_SESSION_BCC`	Data is available in the `ANALYTICS_CONVERSATION_DETAILS_PARTICIPANT_SESSION_BCC` table.
`ANALYTICS_CONVERSATION_AGGREGATE_QUERY_DETAILS_PARTICIPANT_SESSION_CALLBACK_NUMBER`
table	Discontinued Table	`ANALYTICS_CONVERSATION_AGGREGATE_QUERY_DETAILS_PARTICIPANT_SESSION_CALLBACK_NUMBER`	Data is available in the `ANALYTICS_CONVERSATION_DETAILS_PARTICIPANT_SESSION_CALLBACK_NUMBER` table.
`ANALYTICS_CONVERSATION_AGGREGATE_QUERY_DETAILS_PARTICIPANT_SESSION_CC`
table	Discontinued Table	`ANALYTICS_CONVERSATION_AGGREGATE_QUERY_DETAILS_PARTICIPANT_SESSION_CC`	Data is available in the `ANALYTICS_CONVERSATION_DETAILS_PARTICIPANT_SESSION_CC` table.
`ANALYTICS_CONVERSATION_AGGREGATE_QUERY_DETAILS_PARTICIPANT_SESSION_DESTINATION_ADDRESS`
table	Discontinued Table	`ANALYTICS_CONVERSATION_AGGREGATE_QUERY_DETAILS_PARTICIPANT_SESSION_DESTINATION_ADDRESS`	Data is available in the `ANALYTICS_CONVERSATION_DETAILS_PARTICIPANT_SESSION_DESTINATION_ADDRESS` table.
`ANALYTICS_CONVERSATION_AGGREGATE_QUERY_DETAILS_PARTICIPANT_SESSION_ELIGIBLE_AGENT_COUNT`
table	Discontinued Table	`ANALYTICS_CONVERSATION_AGGREGATE_QUERY_DETAILS_PARTICIPANT_SESSION_ELIGIBLE_AGENT_COUNT`	Data is available in the `ANALYTICS_CONVERSATION_DETAILS_PARTICIPANT_SESSION_ELIGIBLE_AGENT_COUNT` table.
`ANALYTICS_CONVERSATION_AGGREGATE_QUERY_DETAILS_PARTICIPANT_SESSION_FLOW_OUTCOME`
table	Discontinued Table	`ANALYTICS_CONVERSATION_AGGREGATE_QUERY_DETAILS_PARTICIPANT_SESSION_FLOW_OUTCOME`	Data is available in the `ANALYTICS_CONVERSATION_DETAILS_PARTICIPANT_SESSION_FLOW_OUTCOME` table.
`ANALYTICS_CONVERSATION_AGGREGATE_QUERY_DETAILS_PARTICIPANT_SESSION_MEDIA_ENDPOINT_STATS`
table	Discontinued Table	`ANALYTICS_CONVERSATION_AGGREGATE_QUERY_DETAILS_PARTICIPANT_SESSION_MEDIA_ENDPOINT_STATS`	Data is available in the `ANALYTICS_CONVERSATION_DETAILS_PARTICIPANT_SESSION_MEDIA_ENDPOINT_STATS` table.
`ANALYTICS_CONVERSATION_AGGREGATE_QUERY_DETAILS_PARTICIPANT_SESSION_METRIC`
table	Discontinued Table	`ANALYTICS_CONVERSATION_AGGREGATE_QUERY_DETAILS_PARTICIPANT_SESSION_METRIC`	Data is available in the `ANALYTICS_CONVERSATION_DETAILS_PARTICIPANT_SESSION_METRIC` table.
`ANALYTICS_CONVERSATION_AGGREGATE_QUERY_DETAILS_PARTICIPANT_SESSION_PROPOSED_AGENT`
table	Discontinued Table	`ANALYTICS_CONVERSATION_AGGREGATE_QUERY_DETAILS_PARTICIPANT_SESSION_PROPOSED_AGENT`	Data is available in the `ANALYTICS_CONVERSATION_DETAILS_PARTICIPANT_SESSION_PROPOSED_AGENT` table.
`ANALYTICS_CONVERSATION_AGGREGATE_QUERY_DETAILS_PARTICIPANT_SESSION_REQUESTED_ROUTING`
table	Discontinued Table	`ANALYTICS_CONVERSATION_AGGREGATE_QUERY_DETAILS_PARTICIPANT_SESSION_REQUESTED_ROUTING`	Data is available in the `ANALYTICS_CONVERSATION_DETAILS_PARTICIPANT_SESSION_REQUESTED_ROUTING` table.
`ANALYTICS_CONVERSATION_AGGREGATE_QUERY_DETAILS_PARTICIPANT_SESSION_SEGMENT`
table	Discontinued Table	`ANALYTICS_CONVERSATION_AGGREGATE_QUERY_DETAILS_PARTICIPANT_SESSION_SEGMENT`	Data is available in the `ANALYTICS_CONVERSATION_DETAILS_PARTICIPANT_SESSION_SEGMENT` table.
`ANALYTICS_CONVERSATION_AGGREGATE_QUERY_DETAILS_PARTICIPANT_SESSION_SKILL_ID`
table	Discontinued Table	`ANALYTICS_CONVERSATION_AGGREGATE_QUERY_DETAILS_PARTICIPANT_SESSION_SKILL_ID`	Data is available in the `ANALYTICS_CONVERSATION_DETAILS_PARTICIPANT_SESSION_SKILL_ID` table.
`ANALYTICS_CONVERSATION_AGGREGATE_QUERY_DETAILS_PARTICIPANT_SESSION_WAITING_INTERACTION_COUNTS`
table	Discontinued Table	`ANALYTICS_CONVERSATION_AGGREGATE_QUERY_DETAILS_PARTICIPANT_SESSION_WAITING_INTERACTION_COUNTS`	Data is available in the `ANALYTICS_CONVERSATION_DETAILS_PARTICIPANT_SESSION_WAITING_INTERACTION_COUNTS` table.
`ANALYTICS_CONVERSATION_AGGREGATE_QUERY_DETAILS_RESOLUTION`
table	Discontinued Table	`ANALYTICS_CONVERSATION_AGGREGATE_QUERY_DETAILS_RESOLUTION`	Data is available in the `ANALYTICS_CONVERSATION_DETAILS_RESOLUTION` table.
`ANALYTICS_CONVERSATION_AGGREGATE_QUERY_DETAILS_SURVEY`
table	Discontinued Table	`ANALYTICS_CONVERSATION_AGGREGATE_QUERY_DETAILS_SURVEY`	Data is available in the `ANALYTICS_CONVERSATION_DETAILS_SURVEY` table.
`CONVERSATION_PARTICIPANT_ATTRIBUTE`
table	Discontinued Table	`CONVERSATION_PARTICIPANT_ATTRIBUTE`	Data is available in the `ANALYTICS_CONVERSATION_DETAILS` table and its child tables.

Google Business Profile

Effective February 21, 2025 we use a new February 2025 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migrations article for more details.

We are updating the connector schema to fix a bug.

17 total changes • 0 possible breaking changes

Table/column	Change type	New name
`LOCAL_POST_MEDIA`
column	New Column	`attribution_profile_name`
column	New Column	`attribution_profile_photo_url`
column	New Column	`attribution_profile_url`
column	New Column	`attribution_take_down_url`
column	New Column	`create_time`
column	New Column	`data_ref_resource_name`
column	New Column	`description`
column	New Column	`dimension_height_pixel`
column	New Column	`dimension_width_pixel`
column	New Column	`google_url`
column	New Column	`insights_view_count`
column	New Column	`location_association_category`
column	New Column	`location_association_price_list_item_id`
column	New Column	`media_format`
column	New Column	`source_url`
column	New Column	`summary`
column	New Column	`thumbnail_url`

Google Calendar

Effective February 10, 2025 we use a new February 2025 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migrations article for more details.

We are updating the connector schema to resolve a data integrity issue

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	Notes
`EVENT`
column	Type Change	`end_date_time`	Data type changed from INSTANT to STRING.
column	Type Change	`start_date_time`	Data type changed from INSTANT to STRING.

Google Search Ads 360

We now support the following resources as custom reports: - ad_group_ad_effective_label - ad_group_criterion_effective_label - ad_group_effective_label - campaign_effective_label - user_location_view

We now support the ad_group.effective_labels field for the ad_group table.

We now support the ad_group_ad.effective_labels field for the ad_group_ad table.

We now support the following fields for the ad_group_ad_effective_label table:

ad_group_ad_effective_label.ad_group_ad
ad_group_ad_effective_label.label
ad_group_ad_effective_label.owner_customer_id
ad_group_ad_effective_label.resource_name

We now support the ad_group_criterion.effective_labels field for the ad_group_criterion table.

We now support the following fields for the ad_group_criterion_effective_label table:

ad_group_criterion_effective_label.ad_group_criterion
ad_group_criterion_effective_label.label
ad_group_criterion_effective_label.owner_customer_id
ad_group_criterion_effective_label.resource_name

We now support the following fields for the ad_group_effective_label table:

ad_group_effective_label.ad_group
ad_group_effective_label.label
ad_group_effective_label.owner_customer_id
ad_group_effective_label.resource_name

We now support the campaign.effective_labels field for the campaign table.

We now support the following fields for the campaign_effective_label table:

campaign_effective_label.campaign
campaign_effective_label.label
campaign_effective_label.owner_customer_id
campaign_effective_label.resource_name

We now support the following fields for the user_location_view table:

user_location_view.country_criterion_id
user_location_view.resource_name
user_location_view.targeting_location

We've added support for the following metrics:

metrics.cross_device_conversions_by_conversion_date
metrics.cross_device_conversions_value_by_conversion_date
metrics.general_invalid_click_rate
metrics.general_invalid_clicks

HubSpot

Effective February 15, 2025 we use a new February 2025 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migrations article for more details.

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

4 total changes • 0 possible breaking changes

Table/column	Change type	New name
`MARKETING_EVENT`
table	New Table	`MARKETING_EVENT`
`MARKETING_EVENT_CUSTOM_PROPERTY`
table	New Table	`MARKETING_EVENT_CUSTOM_PROPERTY`
`MARKETING_EVENT_LIST`
table	New Table	`MARKETING_EVENT_LIST`
`MARKETING_EVENT_PARTICIPANT`
table	New Table	`MARKETING_EVENT_PARTICIPANT`

LaunchDarkly

Effective February 10, 2025 we use a new February 2025 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migrations article for more details.

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.

47 total changes • 22 possible breaking changes

Table/column	Change type	Old name	New name	Notes
`AUDIT_LOG`
table	New Table		`AUDIT_LOG`
`AUDIT_LOG_ACCESS`
table	New Table		`AUDIT_LOG_ACCESS`
`AUDIT_LOG_TARGET_RESOURCE`
table	New Table		`AUDIT_LOG_TARGET_RESOURCE`
`FEATURE_FLAG`
column	Discontinued Column	`environment_production_archived`		Data is available in the `FEATURE_FLAG_ENVIRONMENT` table.
column	Discontinued Column	`environment_production_last_modified`		Data is available in the `FEATURE_FLAG_ENVIRONMENT` table.
column	Discontinued Column	`environment_production_name`		Data is available in the `FEATURE_FLAG_ENVIRONMENT` table.
column	Discontinued Column	`environment_production_on`		Data is available in the `FEATURE_FLAG_ENVIRONMENT` table.
column	Discontinued Column	`environment_production_salt`		Data is available in the `FEATURE_FLAG_ENVIRONMENT` table.
column	Discontinued Column	`environment_production_sel`		Data is available in the `FEATURE_FLAG_ENVIRONMENT` table.
column	Discontinued Column	`environment_production_summary`		Data is available in the `FEATURE_FLAG_ENVIRONMENT` table.
column	Discontinued Column	`environment_production_track_events`		Data is available in the `FEATURE_FLAG_ENVIRONMENT` table.
column	Discontinued Column	`environment_production_track_events_fall_through`		Data is available in the `FEATURE_FLAG_ENVIRONMENT` table.
column	Discontinued Column	`environment_production_version`		Data is available in the `FEATURE_FLAG_ENVIRONMENT` table.
column	Discontinued Column	`environment_test_archived`		Data is available in the `FEATURE_FLAG_ENVIRONMENT` table.
column	Discontinued Column	`environment_test_last_modified`		Data is available in the `FEATURE_FLAG_ENVIRONMENT` table.
column	Discontinued Column	`environment_test_name`		Data is available in the `FEATURE_FLAG_ENVIRONMENT` table.
column	Discontinued Column	`environment_test_on`		Data is available in the `FEATURE_FLAG_ENVIRONMENT` table.
column	Discontinued Column	`environment_test_salt`		Data is available in the `FEATURE_FLAG_ENVIRONMENT` table.
column	Discontinued Column	`environment_test_sel`		Data is available in the `FEATURE_FLAG_ENVIRONMENT` table.
column	Discontinued Column	`environment_test_summary`		Data is available in the `FEATURE_FLAG_ENVIRONMENT` table.
column	Discontinued Column	`environment_test_track_events`		Data is available in the `FEATURE_FLAG_ENVIRONMENT` table.
column	Discontinued Column	`environment_test_track_events_fall_through`		Data is available in the `FEATURE_FLAG_ENVIRONMENT` table.
column	Discontinued Column	`environment_test_version`		Data is available in the `FEATURE_FLAG_ENVIRONMENT` table.
column	New Column		`deprecated`
column	New Column		`deprecated_date`
column	New Column		`maintainer_email`
column	New Column		`maintainer_first_name`
column	New Column		`maintainer_last_name`
column	New Column		`maintainer_role`
column	New Column		`migration_setting_context_kind`
column	New Column		`migration_setting_stage_count`
column	New Column		`purpose`
`FEATURE_FLAG_ENIVORNMENT_PRODUCTION_TARGET`
table	Discontinued Table	`FEATURE_FLAG_ENIVORNMENT_PRODUCTION_TARGET`		Data is available in the `FEATURE_FLAG_ENVIRONMENT` table.
`FEATURE_FLAG_ENIVORNMENT_TEST_TARGET`
table	Discontinued Table	`FEATURE_FLAG_ENIVORNMENT_TEST_TARGET`		Data is available in the `FEATURE_FLAG_ENVIRONMENT` table.
`FEATURE_FLAG_ENVIRONMENT`
table	New Table		`FEATURE_FLAG_ENVIRONMENT`
`FEATURE_FLAG_ENVIRONMENT_ACTION_ALLOWED`
table	New Table		`FEATURE_FLAG_ENVIRONMENT_ACTION_ALLOWED`
`FEATURE_FLAG_ENVIRONMENT_ACTION_DENIED`
table	New Table		`FEATURE_FLAG_ENVIRONMENT_ACTION_DENIED`
`FEATURE_FLAG_ENVIRONMENT_CONTEXT_TARGET`
table	New Table		`FEATURE_FLAG_ENVIRONMENT_CONTEXT_TARGET`
`FEATURE_FLAG_ENVIRONMENT_EVALUATION`
table	New Table		`FEATURE_FLAG_ENVIRONMENT_EVALUATION`
`FEATURE_FLAG_ENVIRONMENT_FALLTHROUGH_ROLLOUT_VARIATION`
table	New Table		`FEATURE_FLAG_ENVIRONMENT_FALLTHROUGH_ROLLOUT_VARIATION`
`FEATURE_FLAG_ENVIRONMENT_PREREQUISITE`
table	New Table		`FEATURE_FLAG_ENVIRONMENT_PREREQUISITE`
`FEATURE_FLAG_ENVIRONMENT_RULE`
table	New Table		`FEATURE_FLAG_ENVIRONMENT_RULE`
`FEATURE_FLAG_ENVIRONMENT_RULE_CLAUSE`
table	New Table		`FEATURE_FLAG_ENVIRONMENT_RULE_CLAUSE`
`FEATURE_FLAG_ENVIRONMENT_RULE_ROLLOUT_VARIATION`
table	New Table		`FEATURE_FLAG_ENVIRONMENT_RULE_ROLLOUT_VARIATION`
`FEATURE_FLAG_ENVIRONMENT_TARGET`
table	New Table		`FEATURE_FLAG_ENVIRONMENT_TARGET`
`FEATURE_FLAG_VARIATION`
column	New Column		`description`
column	New Column		`name`

Planhat

Effective February 11, 2025 we use a new February 2025 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migrations article for more details.

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
`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
`CONVERSATION_USER`
column	Primary Key Change	`user_id` 🔑	`user_id`	No longer a primary key
column	Primary Key Change		`index` 🔑	New primary key

Playvox

Effective February 10, 2025 we use a new February 2025 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migrations article for more details.

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.

8 total changes • 8 possible breaking changes

Table/column	Change type	New name	Notes
`CALIBRATION_ANALYST`
column	Primary Key Change	`calibration_id` 🔑	Added to primary key
`CALIBRATION_ANALYST_SECTION`
column	Primary Key Change	`calibration_id` 🔑	Added to primary key
`CALIBRATION_ANALYST_SECTION_QUESTION`
column	Primary Key Change	`calibration_id` 🔑	Added to primary key
`DISPUTE_REASON_COMMENT`
column	Primary Key Change	`dispute_id` 🔑	Added to primary key
column	Primary Key Change	`dispute_reason_id` 🔑	Added to primary key
`EVALUATION_CUSTOM_FIELD`
column	Primary Key Change	`evaluation_id` 🔑	Added to primary key
`EVALUATION_SECTION_CUSTOM_FIELD`
column	Primary Key Change	`evaluation_id` 🔑	Added to primary key
`SCORECARD_CUSTOM_FIELD_OPTION`
column	Primary Key Change	`scorecard_id` 🔑	Added to primary key

Ramp

Effective February 6, 2025 we use a new February 2025 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migrations article for more details.

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

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.

42 total changes • 3 possible breaking changes

Table/column	Change type	Old name	New name
`CARD`
column	Discontinued Column	`card_program_id`
column	New Column		`created_at`
column	New Column		`expiration`
`CARD_PROGRAM`
table	Discontinued Table	`CARD_PROGRAM`
`CARD_PROGRAM_SPENDING_RESTRICTION_CATEGORY`
table	Discontinued Table	`CARD_PROGRAM_SPENDING_RESTRICTION_CATEGORY`
`LIMITS`
table	New Table		`LIMITS`
`LOCATION`
column	New Column		`entity_id`
`REIMBURSEMENT`
column	New Column		`distance`
column	New Column		`entity_id`
column	New Column		`memo`
column	New Column		`original_reimbursement_amount`
column	New Column		`original_reimbursement_currency_code`
column	New Column		`payee_amount`
column	New Column		`payee_currency_code`
column	New Column		`spend_limit_id`
column	New Column		`state`
column	New Column		`submitted_at`
column	New Column		`synced_at`
column	New Column		`trip_id`
column	New Column		`type`
column	New Column		`updated_at`
`SPEND_PROGRAM`
table	New Table		`SPEND_PROGRAM`
`TRANSACTION`
column	New Column		`currency_code`
column	New Column		`entity_id`
column	New Column		`merchant_data_auto_rental`
column	New Column		`merchant_data_flight`
column	New Column		`merchant_data_fuel`
column	New Column		`merchant_data_lodging`
column	New Column		`merchant_data_reference`
column	New Column		`merchant_location_city`
column	New Column		`merchant_location_country`
column	New Column		`merchant_location_postal_code`
column	New Column		`merchant_location_state`
column	New Column		`original_transaction_amount_amount`
column	New Column		`original_transaction_amount_currency_code`
column	New Column		`receipts`
column	New Column		`settlement_date`
column	New Column		`spend_program_id`
column	New Column		`synced_at`
column	New Column		`trip_id`
column	New Column		`trip_name`
`USERS`
column	New Column		`employee_id`

RevOps

Effective February 11, 2025 we use a new February 2025 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migrations article for more details.

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.

4 total changes • 4 possible breaking changes

Table/column	Change type	Old name	New name
`SKU`
column	Rename Column	`order`	`orders`
`TAG (new table name: PLAN_TAG)`
table	Rename Table	`TAG`	`PLAN_TAG`
`TERM`
column	Rename Column	`order`	`orders`
`USAGE_OBJECT`
column	Rename Column	`timestamp`	`time_stamp`

Sage HR

Effective February 6, 2025 we use a new February 2025 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migrations article for more details.

We are updating the connector schema to improve schema 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.

8 total changes • 3 possible breaking changes

Table/column	Change type	Old name	New name	Notes
`EMPLOYEE_COMPENSATION`
column	Primary Key Change	`_fivetran_id` 🔑		Primary key calculation change.
`EMPLOYEE_EMPLOYMENT_STATUS_HISTORY`
table	New Table		`EMPLOYEE_EMPLOYMENT_STATUS_HISTORY`
`EMPLOYEE_HISTORY`
table	Discontinued Table	`EMPLOYEE_HISTORY`		Data is available in the `EMPLOYEE_POSITION_HISTORY` and `EMPLOYEE_EMPLOYMENT_STATUS_HISTORY` tables.
`EMPLOYEE_POSITION_HISTORY`
table	New Table		`EMPLOYEE_POSITION_HISTORY`
`INDIVIDUAL_TEAM_QUARTERLY_GOAL`
table	Discontinued Table	`INDIVIDUAL_TEAM_QUARTERLY_GOAL`		Data is available in the `QUARTERLY_INDIVIDUAL_GOAL` and `QUARTERLY_TEAM_GOAL` tables.
`QUARTERLY_INDIVIDUAL_GOAL`
table	New Table		`QUARTERLY_INDIVIDUAL_GOAL`
`QUARTERLY_TEAM_GOAL`
table	New Table		`QUARTERLY_TEAM_GOAL`
`TERMINATED_EMPLOYEE`
table	New Table		`TERMINATED_EMPLOYEE`

Salesforce Commerce Cloud

We have added a new column, cancel_code to the ORDERS_HISTORY table. To backfill the data for this column, you can perform a re-sync for the ORDERS_HISTORY table or contact our support team to re-sync the table for you.

Samsara

Effective February 17, 2025 we use a new February 2025 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migrations article for more details.

We are updating the connector schema to enhance its usability.

6 total changes • 0 possible breaking changes

Table/column	Change type	New name
`ALERT_INCIDENT`
table	New Table	`ALERT_INCIDENT`
`DVIR_TRAILER_DEFECT`
table	New Table	`DVIR_TRAILER_DEFECT`
`DVIR_VEHICLE_DEFECT`
table	New Table	`DVIR_VEHICLE_DEFECT`
`EQUIPMENT_STATS`
table	New Table	`EQUIPMENT_STATS`
`STREAM_DVIR`
table	New Table	`STREAM_DVIR`
`VEHICLE_IDLING_REPORT`
table	New Table	`VEHICLE_IDLING_REPORT`

SAP SuccessFactors

We have added the following new tables:

FO_BUSINESS_UNIT
FO_DIVISION
FO_DIVISION_BUSINESS_UNIT_FLX_NAV
FO_DIVISION_CUST_TO_BUSINESS_UNIT
FO_DEPARTMENT
FO_DEPARTMENT_DIVISION_FLX_NAV
FO_DEPARTMENT_CUST_TO_DIVISION
FO_DEPARTMENT_CUST_TO_LEGAL_ENTITY
FO_DEPARTMENT_CUST_TO_LEGAL_ENTITY_COMPANY_FLX_NAV
FO_LOCATION
FO_LOCATION_COMPANY_FLX_NAV
FO_COST_CENTER
FO_COST_CENTER_CUST_LEGAL_ENTITY
FO_COST_CENTER_CUST_LEGAL_ENTITY_COMPANY_FLX_NAV
PER_PERSONAL
PER_PERSON
PER_PERSON_PERSONAL_INFO_NAV
PER_PERSON_SOCIAL_ACCOUNT_NAV
PER_PERSON_PHONE_NAV
PER_PERSON_RELATIONSHIP_NAV
PER_PERSON_NATIONAL_ID_NAV
PER_PERSON_HOME_ADDRESS_NAV
PER_PERSON_EMAIL_NAV
PER_PERSON_EMERGENCY_CONTACT_NAV

Sentry

Effective February 7, 2025 we use a new February 2025 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migrations article for more details.

We are updating the connector schema to 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
`ORGANIZATION_ONBOARDING_TASK`
column	Primary Key Change	`task` 🔑	`task`	No longer a primary key.
column	Primary Key Change		`index` 🔑	New primary key.
`ORGANIZATION_ONBOARDING_TASK_USER_EMAIL`
column	Discontinued Column	`task` 🔑		No longer a primary key.
column	Primary Key Change		`organization_onboarding_task_index` 🔑	New primary key.

Slack

Effective February 7, 2025 we use a new February 2025 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migrations article for more details.

We are updating the connector schema to ensure data completeness.

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 • 1 possible breaking changes

Table/column	Change type	Old name	New name	Notes
`MESSAGE_BLOCK_ELEMENT`
column	Primary Key Change	`MESSAGE_BLOCK_index`	`MESSAGE_BLOCK_index` 🔑	Added to primary key
column	New Column		`text`
column	New Column		`verbatim`
`MESSAGE_BLOCK_FIELD`
table	New Table		`MESSAGE_BLOCK_FIELD`

Snyk

Effective February 18, 2025 we use a new February 2025 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migrations article for more details.

We are updating the connector schema to prevent 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.

30 total changes • 30 possible breaking changes

Table/column	Change type	Old name	New name	Notes
`COLLECTION`
column	Primary Key Change		`organization_id` 🔑	Added to primary key.
`DEPENDENCY`
column	Primary Key Change		`organization_id` 🔑	Added to primary key.
`DEPENDENCY_COPYRIGHT`
column	Primary Key Change		`organization_id` 🔑	Added to primary key.
`DEPENDENCY_LICENSE`
column	Primary Key Change		`organization_id` 🔑	Added to primary key.
`DEPENDENCY_PROJECT`
column	Primary Key Change		`organization_id` 🔑	Added to primary key.
`DEPENDENCY_WITH_ISSUE`
column	Primary Key Change		`organization_id` 🔑	Added to primary key.
`GROUP_MEMBER`
column	Primary Key Change	`organization_group_id` 🔑	`organization_group_id`	No longer a primary key.
column	Primary Key Change		`group_id` 🔑	Added to primary key.
`GROUP_ORGANIZATION`
column	Primary Key Change		`group_id` 🔑	Added to primary key.
`GROUP_TAG`
column	Primary Key Change		`organization_id` 🔑	Added to primary key.
`ISSUE`
column	Primary Key Change		`organization_id` 🔑	Added to primary key.
`ISSUE_CLASS`
column	Primary Key Change		`organization_id` 🔑	Added to primary key.
`ISSUE_COORDINATE`
column	Primary Key Change		`organization_id` 🔑	Added to primary key.
`ISSUE_COORDINATE_REMEDY`
column	Primary Key Change		`organization_id` 🔑	Added to primary key.
`ISSUE_COORDINATE_REPRESENTATION`
column	Primary Key Change		`organization_id` 🔑	Added to primary key.
`ISSUE_PROBLEM`
column	Primary Key Change		`organization_id` 🔑	Added to primary key.
`ISSUE_RISK_FACTOR`
column	Primary Key Change		`organization_id` 🔑	Added to primary key.
`ISSUE_TEST_EXECUTION`
column	Primary Key Change		`organization_id` 🔑	Added to primary key.
`LICENSE`
column	Primary Key Change		`organization_id` 🔑	Added to primary key.
`LICENSE_DEPENDENCY`
column	Primary Key Change		`organization_id` 🔑	Added to primary key.
`LICENSE_PROJECT`
column	Primary Key Change		`organization_id` 🔑	Added to primary key.
`MEMBER`
column	Primary Key Change		`organization_id` 🔑	Added to primary key.
`PROJECT`
column	Primary Key Change		`organization_id` 🔑	Added to primary key.
`PROJECT_BUSINESS_CRITICALITY`
column	Primary Key Change		`organization_id` 🔑	Added to primary key.
`PROJECT_ENVIRONMENT`
column	Primary Key Change		`organization_id` 🔑	Added to primary key.
`PROJECT_IGNORED_DEPENDENCY`
column	Primary Key Change		`organization_id` 🔑	Added to primary key.
`PROJECT_LIFE_CYCLE`
column	Primary Key Change		`organization_id` 🔑	Added to primary key.
`PROJECT_PULL_REQUEST_ASSIGNEE`
column	Primary Key Change		`organization_id` 🔑	Added to primary key.
`PROJECT_TAG`
column	Primary Key Change		`organization_id` 🔑	Added to primary key.
`TARGET`
column	Primary Key Change		`organization_id` 🔑	Added to primary key.

Transcend

Effective February 11, 2025 we use a new February 2024 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migrations article for more details.

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

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
`SUB_DATAPOINT_CATEGORY`
column	Discontinued Column		`confidence_label`

Wicked Reports

Effective February 21, 2025 we use a new February 2025 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migrations article for more details.

We are updating the connector schema to improve data integrity.

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.

12 total changes • 12 possible breaking changes

Table/column	Change type	Old name	New name	Notes
`FUNNEL_VISION_GRID`
column	Primary Key Change	`dataset` 🔑	`dataset`	No longer a primary key.
column	Primary Key Change	`date` 🔑	`date`	No longer a primary key.
column	Primary Key Change	`grid_first_click_date` 🔑	`grid_first_click_date`	No longer a primary key.
column	Primary Key Change	`grid_last_click_date` 🔑	`grid_last_click_date`	No longer a primary key.
column	Primary Key Change	`view_id` 🔑	`view_id`	No longer a primary key.
column	Primary Key Change		`_fivetran_id` 🔑	New primary key.
`FUNNEL_VISION_SUMMARY`
column	Primary Key Change	`dataset` 🔑	`dataset`	No longer a primary key.
column	Primary Key Change	`date` 🔑	`date`	No longer a primary key.
column	Primary Key Change	`summary_first_click_date` 🔑	`summary_first_click_date`	No longer a primary key.
column	Primary Key Change	`summary_last_click_date` 🔑	`summary_last_click_date`	No longer a primary key.
column	Primary Key Change	`view_id` 🔑	`view_id`	No longer a primary key.
column	Primary Key Change		`_fivetran_id` 🔑	New primary key.

Workable

Effective February 18, 2025 we use a new February 2025 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migrations article for more details.

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.

2 total changes • 1 possible breaking changes

Table/column	Change type	Old name	New name	Notes
`CANDIDATE_ACTIVITY`
column	Primary Key Change	`action` 🔑	`action`	We have removed the `action` column from the composite key to improve data integrity.
column	New Column		`id` 🔑	New composite key.

Workday Financial Management

We have added two new fields, operational_transaction_id and operational_transaction_reference, to the JOURNAL_ENTRY table.

Wrike

Effective February 11, 2025 we use a new February 2025 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migrations article for more details.

We are updating the connector schema to improve schema 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.

41 total changes • 16 possible breaking changes

Table/column	Change type	Old name	New name
`DEPENDENCY`
table	Discontinued Table	`DEPENDENCY`
`FOLDER_FINANCE`
table	New Table		`FOLDER_FINANCE`
`FOLDER_PROJECT`
column	Discontinued Column	`project_finance`
`FOLDER_TASK`
table	New Table		`FOLDER_TASK`
`FOLDER_TASK_AUTHOR_ID`
table	New Table		`FOLDER_TASK_AUTHOR_ID`
`FOLDER_TASK_CUSTOM_FIELD`
table	New Table		`FOLDER_TASK_CUSTOM_FIELD`
`FOLDER_TASK_DEPEDENCY_ID`
table	New Table		`FOLDER_TASK_DEPEDENCY_ID`
`FOLDER_TASK_FOLLOWER_ID`
table	New Table		`FOLDER_TASK_FOLLOWER_ID`
`FOLDER_TASK_PARENT_ID`
table	New Table		`FOLDER_TASK_PARENT_ID`
`FOLDER_TASK_RESPONSIBLE_ID`
table	New Table		`FOLDER_TASK_RESPONSIBLE_ID`
`FOLDER_TASK_RESPONSIBLE_PLACEHOLDER_ID`
table	New Table		`FOLDER_TASK_RESPONSIBLE_PLACEHOLDER_ID`
`FOLDER_TASK_SHARED_ID`
table	New Table		`FOLDER_TASK_SHARED_ID`
`FOLDER_TASK_SUB_TASK_ID`
table	New Table		`FOLDER_TASK_SUB_TASK_ID`
`FOLDER_TASK_SUPER_PARENT_ID`
table	New Table		`FOLDER_TASK_SUPER_PARENT_ID`
`FOLDER_TASK_SUPER_TASK_ID`
table	New Table		`FOLDER_TASK_SUPER_TASK_ID`
`SPACE_TASK`
table	New Table		`SPACE_TASK`
`SPACE_TASK_AUTHOR_ID`
table	New Table		`SPACE_TASK_AUTHOR_ID`
`SPACE_TASK_CUSTOM_FIELD`
table	New Table		`SPACE_TASK_CUSTOM_FIELD`
`SPACE_TASK_DEPEDENCY_ID`
table	New Table		`SPACE_TASK_DEPEDENCY_ID`
`SPACE_TASK_FOLLOWER_ID`
table	New Table		`SPACE_TASK_FOLLOWER_ID`
`SPACE_TASK_PARENT_ID`
table	New Table		`SPACE_TASK_PARENT_ID`
`SPACE_TASK_RESPONSIBLE_ID`
table	New Table		`SPACE_TASK_RESPONSIBLE_ID`
`SPACE_TASK_RESPONSIBLE_PLACEHOLDER_ID`
table	New Table		`SPACE_TASK_RESPONSIBLE_PLACEHOLDER_ID`
`SPACE_TASK_SHARED_ID`
table	New Table		`SPACE_TASK_SHARED_ID`
`SPACE_TASK_SUB_TASK_ID`
table	New Table		`SPACE_SUB_TASK_ID`
`SPACE_TASK_SUPER_PARENT_ID`
table	New Table		`SPACE_TASK_SUPER_PARENT_ID`
`SPACE_TASK_SUPER_TASK_ID`
table	New Table		`SPACE_SUPER_TASK_ID`
`TASK`
table	Discontinued Table	`TASK`
`TASK_AUTHOR`
table	Discontinued Table	`TASK_AUTHOR`
`TASK_CUSTOM_FIELD`
table	Discontinued Table	`TASK_CUSTOM_FIELD`
`TASK_DEPENDENCY`
table	Discontinued Table	`TASK_DEPENDENCY`
`TASK_EFFORT`
table	Discontinued Table	`TASK_EFFORT`
`TASK_FINANCE`
table	Discontinued Table	`TASK_FINANCE`
`TASK_FOLLOWER`
table	Discontinued Table	`TASK_FOLLOWER`
`TASK_PARENT`
table	Discontinued Table	`TASK_PARENT`
`TASK_PLACEHOLDER`
table	Discontinued Table	`TASK_PLACEHOLDER`
`TASK_RESPONSIBLE`
table	Discontinued Table	`TASK_RESPONSIBLE`
`TASK_SHARED`
table	Discontinued Table	`TASK_SHARED`
`TASK_SUB`
table	Discontinued Table	`TASK_SUB`
`TASK_SUPER`
table	Discontinued Table	`TASK_SUPER`
`TASK_SUPER_PARENT`
table	Discontinued Table	`TASK_SUPER_PARENT`

Xray

Effective February 10, 2025 we use a new February 2025 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migrations article for more details.

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

5 total changes • 0 possible breaking changes

Table/column	Change type	New name
`TEST_RUN`
column	New Column	`assignee_id`
column	New Column	`executed_by_id`
column	New Column	`finished_on`
column	New Column	`last_modified`
column	New Column	`started_on`

Improvements

Amazon Selling Partner

For new connectors created after 9th February, 2025, we have added a new field, Historical sync time frame, to the connector setup form. This allows you to select how many months' worth of historical data you want to sync. For an existing connector, you can edit the connection details and set the time frame value. For more information, see our Amazon Selling Partner documentation.

We apply the historical sync limit to the following tables only:

APPROVAL_SUPPORT_DATA_ELEMENT
FINANCIAL_ADHOC_DISBURSEMENT_EVENT
FINANCIAL_AFFORDABILITY_EXPENSE_EVENT
FINANCIAL_CAPACITY_RESERVATION_BILLING_EVENT
FINANCIAL_CHARGE_COMPONENT
FINANCIAL_CHARGE_INSTRUMENT
FINANCIAL_CHARGE_REFUND_EVENT
FINANCIAL_COUPON_PAYMENT_EVENT
FINANCIAL_DEBT_RECOVERY_EVENT
FINANCIAL_DEBT_RECOVERY_ITEM
FINANCIAL_FAILED_ADHOC_DISBURSEMENT_EVENT
FINANCIAL_FBA_LIQUIDATION_EVENT
FINANCIAL_FEE_COMPONENT
FINANCIAL_IMAGING_SERVICES_FEE_EVENT
FINANCIAL_PAY_WITH_AMAZON_EVENT
FINANCIAL_PRODUCT_ADS_PAYMENT_EVENT
FINANCIAL_REMOVAL_SHIPMENT_ADJUSTMENT_EVENT
FINANCIAL_REMOVAL_SHIPMENT_EVENT
FINANCIAL_REMOVAL_SHIPMENT_ITEM
FINANCIAL_REMOVAL_SHIPMENT_ITEM_ADJUSTMENT
FINANCIAL_RENTAL_TRANSACTION
FINANCIAL_RETRO_CHARGE_EVENT
FINANCIAL_SAFET_REIMBURSEMENT_EVENT
FINANCIAL_SAFET_REIMBURSEMENT_ITEM
FINANCIAL_SELLER_DEAL_PAYMENT_EVENT
FINANCIAL_SELLER_REVIEW_ENROLLMENT_PAYMENT_EVENT
FINANCIAL_SERVICE_FEE_EVENT
FINANCIAL_SHIPMENT_DIRECT_PAYMENT
FINANCIAL_SHIPMENT_EVENT
FINANCIAL_SHIPMENT_EVENT_ITEM
FINANCIAL_SHIPMENT_EVENT_ITEM_PROMOTION
FINANCIAL_SOLUTION_PROVIDER_CREDIT_EVENT
FINANCIAL_TAX_WITHHOLDING_EVENT
FINANCIAL_TDS_REIMBURSEMENT_EVENT
FINANCIAL_TRIAL_SHIPMENT_EVENT
FINANCIAL_VALUE_ADDED_SERVICE_CHARGE_EVENT
MARKET_BASKET_ANALYSIS_REPORT_DAILY
MARKET_BASKET_ANALYSIS_REPORT_MONTHLY
MARKET_BASKET_ANALYSIS_REPORT_QUARTERLY
MARKETPLACE_TAX_CLASSIFICATION
NET_PURE_PRODUCT_MARGIN_REPORT_DAILY
NET_PURE_PRODUCT_MARGIN_REPORT_MONTHLY
NET_PURE_PRODUCT_MARGIN_REPORT_QUARTERLY
NETWORK_COMMINGLING_TRANSACTION_EVENT
ORDER
ORDER_ITEMS
ORDERS_ITEM_PROMOTION_ID
ORDER_ITEM_SERIAL_NUMBER
ORDER_REGULATED_INFO
PAYMENT_EXECUTION_DETAIL_ITEM
PAYMENT_METHOD_DETAIL_ITEM
RAPID_RETAIL_ANALYTICS_INVENTORY_REPORT_HOURLY
RAPID_RETAIL_ANALYTICS_SALES_REPORT_HOURLY
RAPID_RETAIL_ANALYTICS_TRAFFIC_REPORT_HOURLY
REGULATED_INFORMATION_FIELD
REPEAT_PURCHASE_REPORT_MONTHLY
REPEAT_PURCHASE_REPORT_QUARTERLY
SALES_AND_TRAFFIC_BUSINESS_REPORT_DAILY
SALES_AND_TRAFFIC_BUSINESS_REPORT_MONTHLY
SEARCH_TERMS_REPORT_DAILY
SEARCH_TERMS_REPORT_MONTHLY
SEARCH_TERMS_REPORT_QUARTERLY
VENDOR_INVENTORY_MANUFACTURING_FRESH_REPORT_DAILY
VENDOR_INVENTORY_MANUFACTURING_FRESH_REPORT_MONTHLY
VENDOR_INVENTORY_MANUFACTURING_FRESH_REPORT_QUARTERLY
VENDOR_INVENTORY_MANUFACTURING_RETAIL_REPORT_DAILY
VENDOR_INVENTORY_MANUFACTURING_RETAIL_REPORT_MONTHLY
VENDOR_INVENTORY_MANUFACTURING_RETAIL_REPORT_QUARTERLY
VENDOR_INVENTORY_SOURCING_FRESH_REPORT_DAILY
VENDOR_INVENTORY_SOURCING_FRESH_REPORT_MONTHLY
VENDOR_INVENTORY_SOURCING_FRESH_REPORT_QUARTERLY
VENDOR_INVENTORY_SOURCING_RETAIL_REPORT_DAILY
VENDOR_INVENTORY_SOURCING_RETAIL_REPORT_MONTHLY
VENDOR_INVENTORY_SOURCING_RETAIL_REPORT_QUARTERLY
VENDOR_SALES_MANUFACTURING_BUSINESS_REPORT_DAILY
VENDOR_SALES_MANUFACTURING_BUSINESS_REPORT_MONTHLY
VENDOR_SALES_MANUFACTURING_BUSINESS_REPORT_QUARTERLY
VENDOR_SALES_MANUFACTURING_FRESH_REPORT_DAILY
VENDOR_SALES_MANUFACTURING_FRESH_REPORT_MONTHLY
VENDOR_SALES_MANUFACTURING_FRESH_REPORT_QUARTERLY
VENDOR_SALES_MANUFACTURING_RETAIL_REPORT_DAILY
VENDOR_SALES_MANUFACTURING_RETAIL_REPORT_MONTHLY
VENDOR_SALES_MANUFACTURING_RETAIL_REPORT_QUARTERLY
VENDOR_SALES_SOURCING_BUSINESS_REPORT_DAILY
VENDOR_SALES_SOURCING_BUSINESS_REPORT_MONTHLY
VENDOR_SALES_SOURCING_BUSINESS_REPORT_QUARTERLY
VENDOR_SALES_SOURCING_FRESH_REPORT_DAILY
VENDOR_SALES_SOURCING_FRESH_REPORT_MONTHLY
VENDOR_SALES_SOURCING_FRESH_REPORT_QUARTERLY
VENDOR_SALES_SOURCING_RETAIL_REPORT_DAILY
VENDOR_SALES_SOURCING_RETAIL_REPORT_MONTHLY
VENDOR_SALES_SOURCING_RETAIL_REPORT_QUARTERLY
VENDOR_TRAFFIC_REPORT_DAILY
VENDOR_TRAFFIC_REPORT_MONTHLY
VENDOR_TRAFFIC_REPORT_QUARTERLY

Apple Search Ads

We have added support for report fields which Apple introduced in v5 of the Apple Search Ads API. For more information about the changes, see Apple Search Ads API's changelog.

Attentive

We have removed the foreign key relationship of the message_id column to the EMAIL_SENT and SMS_SENT tables, in the EMAIL_MESSAGE_LINK_CLICK and SMS_MESSAGE_LINK_CLICK tables.

Azure Data Lake Storage

We now delete the old snapshots of your destination tables once daily. We are gradually rolling out this enhancement to all existing destinations.

Azure DevOps

We now sync all work items to the WORK_ITEM table. Previously, we synced only the backlog work items.

Braintree

We have upgraded our Braintree connector from version 3.29.0 to 3.39.0 of the Braintree API. For more information about the changes and deprecations, see Braintree API's changelog.

Deputy

We have updated the connector's sync strategy. We now incrementally sync the ROSTER table.

eBay

We've removed table-level selection and re-sync options for the PAYMENT_DISPUTE table.

Email

Our Email connector now supports syncing Microsoft Excel spreadsheets. For more information, see our setup instructions.

Formstack

We've removed table-level selection and re-sync options for the FORM_SUBMISSION and PARTIAL_SUBMISSION tables.

Google Cloud Storage

The Google Cloud Storage connector now supports the Hybrid Deployment model. For more information, see our setup instructions.

Google Search Ads 360

We now support Google Search Ads 360 Reporting API v0 (2024-11-08).

Google Sheets

We have renamed the Grant User Access field in the connector setup form to Authorize with User account. For more information, see our setup instructions.

HiBob

We now sync future leave data for up to 18 months from the current date for the EMPLOYEE_OUT_OF_OFFICE table during every incremental sync.

Jama Software

We've removed table-level selection and re-sync options for the following tables:

ATTACHMENT
ITEM
TEST_CYCLE
TEST_RUN

Maxio SaaSOptics

We have added new custom_* columns to capture custom fields for the CUSTOMER table.

Microsoft Dynamics 365 CRM

We now sync columns with the suffix _lookuplogicalname for the selected lookup property fields in each table. You can find these columns only in your destination, and not on the Schema tab of your connector details page. Be sure to re-sync the required tables to backfill the historical data or click Resync all historical data in the Setup tab to re-sync the historical data to your destination. We are gradually rolling out this feature to all existing connectors.

Mixpanel

We have added a new field, Historical sync time frame, to the connector setup form. This allows you to select how many months' worth of historical data you want to sync. For an existing connector, you can edit the connection details and set the time frame value. For more information, see our Historical sync time frame documentation.

We apply the historical sync limit to the EVENT table only.

We are gradually rolling out this feature to all connections.

Monday.com

The Monday.com connector now uses API version 2025-04.

Mux

We've removed table-level selection and re-sync options for the VIDEO_VIEW table.

OneLake

We now delete the old snapshots of your destination tables once daily. We are gradually rolling out this enhancement to all existing destinations.

PayPal

We've removed table-level selection and re-sync options for the DISPUTE table.

Pendo

We have added a new field, Historical Sync Time Frame, to the connector setup form. This allows you to select how much duration worth of historical data you want to sync. The default value is Sync all historical data. You can choose Sync data from selected date option from the drop down to set HistoricSync Backwards Limit form date picker. You can edit the connection details and set the time frame value for an existing connector. We have also added support for the historic_sync_time_frame field for connectors created using the Create a Connector endpoint. For more information, see our REST API config.

The historical sync limit only applies to the following tables.

EVENT
FEATURE_EVENT
GUIDE_EVENT
PAGE_EVENT
POLL_EVENT
TRACK_TYPE_EVENT

We are gradually rolling out this feature to all connections.

Pingdom

We have updated the connector's sync strategy. We now incrementally sync the RESULT table.

PostgreSQL

We now support PostgreSQL 17. For more information, see our PostgreSQL documentation.

Rakuten Advertising

We now sync REPORT table from the year 2022.

Recharge

We now re-import the previous day’s data for the CUSTOMER table to capture any delayed updates from the source.

S3 Data Lake

We now delete the old snapshots of your destination tables once daily. We are gradually rolling out this enhancement to all existing destinations.

Sage Intacct

We no longer sync the GL_DETAIL table as a child table of the GL_BATCH table. We now sync the GL_DETAIL table as a parent table without any child tables.

We have also changed the sync strategy for the GL_DETAIL table. We no longer capture the deletes for the GL_DETAIL table through incremental syncs.

We now support syncing custom fields for the SO_DOCUMENT and SO_DOCUMENT_ENTRY tables. To sync these fields, you must enable the SO_DOCUMENT_PARAMS table in Sage intacct.

Salesforce Commerce Cloud

We have updated the connector's sync strategy. We now perform a daily backfill for the PRODUCT endpoint to capture the previous day's data. As a result, you may notice a temporary increase in your Monthly Active Rows (MAR) usage at the beginning of each month, reflecting the final day’s data from the previous month.

SAP ERP on HANA

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

We have significantly improved the performance of database triggers that we use to detect deleted records. Additionally, the 'Mass activity' report can now recreate triggers for tables that were manually removed.

We've added support for the Proxy Agent connection method to the SAP ERP on HANA connector. You can now use Proxy Agent to connect to your SAP ERP on HANA instance.

For more information, see our SAP ERP on HANA documentation and SAP ERP on HANA setup guide.

Smarthr

We now re-import the EMPLOYEE table and its child tables once a week to capture updates and deletes.

Statsig

We've removed table-level selection and re-sync options for the FIRST_EXPOSURES_REPORT and PULSE_DAILY_REPORT tables.

Stripe

Effective February 14, 2025, we have added a new field, Historical sync time frame, to the Stripe connection setup form. This field allows you to select how many months' worth of historical data you want to sync. To use this field for an existing connection, select the time frame value on the Connection details page. Learn more in our Stripe connector historical sync time frame documentation.

We apply the historical sync limit to the following tables only:

APPLICATION_FEE
AUTHORIZATION
BALANCE_TRANSACTION
CHARGE
DISPUTE
FILE
FILE_LINK
INVOICE
INVOICE_ITEM
ISSUING_DISPUTE
ISSUING_TRANSACTION
ORDER_RETURN
PAYMENT_INTENT
PAYOUT
REFUND
REVIEW
SETUP_INTENT
TOPUP
TRANSFER

The Movie Database

We've removed table-level selection and re-sync options for the MOVIE and TV_SERIES tables.

Workday Financial Management

Our Workday Financial Management connector now supports below endpoints of Workday Resource Management Module. To support this enhancement, we have added the following new tables:

BUSINESS_ENTITY_ADDRESS_LINE
BUSINESS_ENTITY_ADDRESS_SUBMUNICIPALITY
BUSINESS_ENTITY_ADDRESS_SUBREGION
BUSINESS_ENTITY_ADDRESS
BUSINESS_ENTITY_COMMUNICATION_USAGE
BUSINESS_ENTITY_CONTACT_TYPE_TENANTED
BUSINESS_ENTITY_CONTACT_TYPE
BUSINESS_ENTITY_CONTACT
BUSINESS_ENTITY_EMAIL_ADDRESS
BUSINESS_ENTITY_IM
BUSINESS_ENTITY_PERSON_NAME
BUSINESS_ENTITY_PHONE
BUSINESS_ENTITY_WEB_ADDRESS
CREDIT_CARD_TRANSACTION_LINE
EXPENSE_CREDIT_CARD_TRANSACTION
HOTEL_DETAIL
NAME_MATCH
OTHER_HOTEL_SERVICE
PROJECT_ATTACHMENT
PROJECT_COST_RATE_RULE
PROJECT_HIERARCHY
PROJECT_RESOURCE_REQUIREMENT_PARAMETER
PROJECT_ROLE_CATEGORY
PROJECT_ROLE_RATE
PROJECT_STANDARD_COST_RATE_SHEET
PROJECT_STANDARD_COST_RATE_SNAPSHOT
PROJECT_TASK_HIERARCHY
PROJECT_TASK_RESOURCE
PROJECT_TASK
PROJECT_TIMESHEET_DAY
PROJECT_TIMESHEET_LINE
PROJECT_TIMESHEET
PROJECT_WORKER_PROJECT_HIERARCHY
PROJECT_WORKER_RATE
PROJECT_WORKER_ROLE
PROJECT
RELATED_WORKTAG
RESOURCE_FORECAST_CONFIGURATION
RESOURCE_FORECAST_LINE_ALLOCATION
RESOURCE_FORECAST_LINE
RESOURCE_FORECAST
TAX_DETAIL
TICKET_DETAIL
TRIP_LEG_DETAIL_NAME_MATCH
TRIP_LEG_DETAIL

We are gradually rolling out these features to all existing connections. If you have any questions, contact our Support team.

Workday HCM

Our Workday HCM connector now supports the Workday Talent module. To support this enhancement, we have added the following new tables:

ASSESS_TALENT
ASSESS_TALENT_NOMINATION
CALIBRATION_PROGRAM
CALIBRATION_VALUE_MAP
CELL_TARGET_PERCENTAGE
TALENT_POOL
TALENT_POOL_WORKER

We have added the following new tables to support the Learning Module:

LEARNING_COURSE_ADVANCED_PRICING_RULE
LEARNING_COURSE_CONTACT_PERSON
LEARNING_COURSE_LANGUAGE
LEARNING_COURSE_OFFERING
LEARNING_COURSE_OFFERING_DATA
LEARNING_COURSE_OFFERING_DATA_FROM_COURSE
LEARNING_COURSE_OFFERING_DETAIL
LEARNING_COURSE_OFFERING_LESSON
LEARNING_COURSE_OTHER_UNIT_TYPE
LEARNING_COURSE_SALES_ITEM
LEARNING_ENROLLMENT
LEARNING_LESSON
LEARNING_LESSON_LANGUAGE
LEARNING_LESSON_SKILL
LEARNING_LESSON_TOPIC

We are gradually rolling out these features to all existing connections. If you have any questions, contact our Support team.

REST API Improvements

Connection state REST API endpoints

The Retrieve Function Connector State and Update Function Connector State endpoints in our REST API that allow you to get and update the state of Functions and Connector SDK connections are generally available.

Synchronization of terminology

We have renamed the Connector Management API to the Connection Management API and the Connector Schema Management API to the Connection Schema Management API to align with our terminology. We have also updated all API paths from /connectors to /connections, while continuing to support both access methods.

We have updated the relevant paths in the following resources from /connectors to /connections, while continuing to support both access methods:

Timestamp Format in REST API Responses

Our REST API responses now use the "yyyy-MM-dd'T'HH:mm:ss.SSSSSS'Z'" timestamp format.

February 2025

Connector SDK

Fivetran Connector SDK

fivetran-connector-sdk PyPI package

Lite Connectors

Managed Data Lakes Service

Proxy Agent

Review Schema Changes

System Keys

Transformations for dbt Core

Updated dbt Quickstart packages

Schema changes

Apple App Store

Apple Search Ads

Azure DevOps

Clazar

Coupa

Dialpad

Genesys

Google Business Profile

Google Calendar

Google Search Ads 360

HubSpot

LaunchDarkly

Planhat

Playvox

Ramp

RevOps

Sage HR

Salesforce Commerce Cloud

Samsara

SAP SuccessFactors

Sentry

Slack

Snyk

Transcend

Wicked Reports

Workable

Workday Financial Management

Wrike

Xray

Improvements

Amazon Selling Partner

Apple Search Ads

Attentive

Azure Data Lake Storage

Azure DevOps

Braintree

Deputy

eBay

Email

Formstack

Google Cloud Storage

Google Search Ads 360

Google Sheets

HiBob

Jama Software

Maxio SaaSOptics

Microsoft Dynamics 365 CRM

Mixpanel

Monday.com

Mux

OneLake

PayPal

Pendo

Pingdom

PostgreSQL

Rakuten Advertising

Recharge

S3 Data Lake

Sage Intacct

Salesforce Commerce Cloud

SAP ERP on HANA

Smarthr

Statsig

Stripe

The Movie Database

Workday Financial Management

Workday HCM

REST API Improvements

`fivetran-connector-sdk` PyPI package