March 2025

Connector SDK

`fivetran-connector-sdk` PyPI package

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

Minor improvements and bug fixes.
Improved prompting of parameters for the fivetran deploy command.

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

Minor improvements and bug fixes.
Prevent uploading of Python virtual environment files to Fivetran.

Fivetran AWS EU Servers

We have added new servers in the AWS Europe (Stockholm) region.

If you're on a Business Critical plan, you can now select this region in your destination setup form. Connectors configured in a destination run in their designated cloud and region, meaning that your data doesn't leave our region-specific servers during processing. For example, if you configure your connectors to use our servers in the EU, your data does not leave the EU during processing.

For more information, see our data residency documentation.

Lite Connectors

Lite connectors are now available for the following sources:

Logs

New attributes in log events

We have added new fields connection_id and connection_name to all log events. They will replace current fields connector_id and connector_name, which are now deprecated and will be removed in the future.

We also added a new fields in some specific events data instead of deprecated ones:

Event name	New field	Deprecated field
`change_schema_config`	`connectionId`	`connectorId`
`change_schema_config_via_api`	`connectionId`	`connectorId`
`change_schema_config_via_sync`	`connectionId`	`connectorId`
`diagnostic_access_approved`	`connectionName`	`connectorName`
`diagnostic_access_denied`	`connectionName`	`connectorName`
`diagnostic_access_revoked`	`connectionName`	`connectorName`
`diagnostic_access_ended`	`connectionName`	`connectorName`
`diagnostic_access_expired`	`connectionName`	`connectorName`
`diagnostic_access_granted`	`connectionName`	`connectorName`

For more information, see our Logs documentation.

Transformations for dbt Core

Deprecated transformation log events

We have deprecated the following Transformation log events:

dbt_run_start - replaced with transformation_start
dbt_run_succeeded - replaced with transformation_succeeded
dbt_run_failed - replaced with transformation_failed

Updated dbt Quickstart packages

We have updated the Quickstart packages for the following connectors:

Connectors supporting the Ad Reporting data model to version 1.13.0
Facebook Ads to version 0.8.1
Fivetran Platform Connector to version 2.1.0
HubSpot to version 0.22.0
Microsoft Advertising to version 0.10.0
Mixpanel to version 0.12.0
NetSuite SuiteAnalytics to version 0.18.0
Shopify to version 0.18.0
Connectors supporting the Social Media Reporting data model to version 0.6.0
Stripe to version 0.17.0
Xero to version 0.8.0
Zendesk Support to version 0.21.0

New connectors

Adobe Commerce

Adobe Commerce is a digital commerce solution for merchants and brands. Read our Adobe Commerce connector documentation.

Db2 for LUW

Db2 for Linux, UNIX and Windows (LUW) is a relational database created by IBM. Read our Db2 for LUW connector documentation.

Schema changes

Aha!

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

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

43 total changes • 0 possible breaking changes

Table/column	Change type	New name
`EPIC_CUSTOM_FIELD`
column	New Column	`attachments`
column	New Column	`body`
column	New Column	`created_at`
column	New Column	`email_value`
`EPIC_CUSTOM_FIELD_SCORE_FACT`
table	New Table	`EPIC_CUSTOM_FIELD_SCORE_FACT`
`INITIATIVE`
column	New Column	`color`
column	New Column	`score`
column	New Column	`score_facts`
`INITIATIVE_CUSTOM_FIELD`
table	New Table	`INITIATIVE_CUSTOM_FIELD`
`INITIATIVE_CUSTOM_FIELD_SCORE_FACT`
table	New Table	`INITIATIVE_CUSTOM_FIELD_SCORE_FACT`
`INITIATIVE_FEATURE`
table	New Table	`INITIATIVE_FEATURE`
`PRODUCT`
column	New Column	`description_attachments`
`RELEASE`
column	New Column	`comments_count`
column	New Column	`created_by_user_id`
column	New Column	`development_started_on`
column	New Column	`duration_source`
column	New Column	`end_date`
column	New Column	`external_date_resolution`
column	New Column	`external_release_date`
column	New Column	`external_release_date_description`
column	New Column	`master_release`
column	New Column	`original_estimate`
column	New Column	`position`
column	New Column	`progress`
column	New Column	`progress_source`
column	New Column	`released`
column	New Column	`released_on`
column	New Column	`remaining_estimate`
column	New Column	`status_changed_on`
column	New Column	`theme_attachments`
column	New Column	`theme_body`
column	New Column	`theme_created_at`
column	New Column	`theme_id`
column	New Column	`theme_updated_at`
column	New Column	`updated_at`
column	New Column	`work_done`
column	New Column	`work_units`
column	New Column	`workflow_status_id`
column	New Column	`workflow_status_times`
`RELEASE_CUSTOM_FIELD`
table	New Table	`RELEASE_CUSTOM_FIELD`
`RELEASE_CUSTOM_FIELD_SCORE_FACT`
table	New Table	`RELEASE_CUSTOM_FIELD_SCORE_FACT`
`RELEASE_GOAL`
table	New Table	`RELEASE_GOAL`
`RELEASE_INITIATIVE`
table	New Table	`RELEASE_INITIATIVE`

Alchemer

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

We are updating the connector schema to enhance its usability.

1 total changes • 0 possible breaking changes

Table/column	Change type		Old name	New name	Notes
`SURVEY_DATA`
column	New Column			`comment`

Auth0

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

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

13 total changes • 0 possible breaking changes

Table/column	Change type	New name
`STATS_DAILY`
column	New Column	`leaked_passwords_reset`
`USERS`
column	New Column	`first_name`
column	New Column	`identity_api`
column	New Column	`idp_tenant_domain`
column	New Column	`is_private_email`
column	New Column	`last_name`
column	New Column	`last_password_reset`
column	New Column	`nonce_supported`
column	New Column	`o_id`
column	New Column	`picture`
column	New Column	`principal_name`
column	New Column	`real_user_status`
column	New Column	`tenant_id`

BigCommerce

We have added a new table, CATALOG_VARIANT_METAFIELD, to track updates to product variant metafields.

Chargebee Product Catalog 2.0

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

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

1 total changes • 0 possible breaking changes

Table/column	Change type		Old name	New name	Notes
`EVENT`
column	New Column			`origin_user`

Cin7 Core

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

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

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

8 total changes • 4 possible breaking changes

Table/column	Change type	Old name	New name	Notes
`PURCHASE_CREDIT_NOTE_LINE`
column	Primary Key Change	`product_id`	`index` 🔑	New primary key.
`PURCHASE_INVOICE_LINE`
column	Primary Key Change	`product_id`	`index` 🔑	New primary key.
`PURCHASE_STOCK_AND_PUT_AWAY_LINE`
table	Discontinued Table	`PURCHASE_STOCK_AND_PUT_AWAY_LINE`
`PURCHASE_STOCK_AND_PUT_AWAY_STATUS`
table	Discontinued Table	`PURCHASE_STOCK_AND_PUT_AWAY_STATUS`
`PUT_AWAY`
table	New Table		`PUT_AWAY`
`PUT_AWAY_LINE`
table	New Table		`PUT_AWAY_LINE`
`STOCK_RECEIVED`
table	New Table		`STOCK_RECEIVED`
`STOCK_RECEIVED_LINE`
table	New Table		`STOCK_RECEIVED_LINE`

Close

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

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

4 total changes • 0 possible breaking changes

Table/column	Change type	New name
`NOTE_ACTIVITY`
column	New Column	`attachment`
column	New Column	`lead_id`
column	New Column	`note_mention`
column	New Column	`user_name`

Coupa

We have added two new tables, USER_ADDRESS and USER_ADDRESS_MAPPING. We sync the data using the User API endpoint.

We now sync data from the following API endpoints to the COMMENT table:

ExpenseReport
InvoiceHeader
OrderHeader
RequisitionHeader
User

Re-sync the connection to backfill the historical data for these tables, or contact Fivetran Support to re-sync the data only for these specific endpoints.

Facebook Pages

We have removed the following metrics since Facebook has deprecated them due to version migration from v18 to v21:

page_video_views_10s
page_video_views_10s_autoplayed
page_video_views_10s_click_to_play
page_video_views_10s_organic
page_video_views_10s_paid
page_video_views_10s_repeat
page_video_views_10s_unique
post_video_views_10s
post_video_views_10s_autoplayed
post_video_views_10s_clicked_to_play
post_video_views_10s_organic
post_video_views_10s_paid
post_video_views_10s_sound_on
post_video_views_10s_unique

Factbird

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

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

2 total changes • 0 possible breaking changes

Table/column	Change type	New name
`SENSOR_STOP_CAUSE`
table	New Table	`SENSOR_STOP_CAUSE`
`SENSOR_STOP_CAUSE_META`
table	New Table	`SENSOR_STOP_CAUSE_META`

FireHydrant

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

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

4 total changes • 4 possible breaking changes

Table/column	Change type	Old name	Notes
`RUNBOOK`
column	Discontinued Column	`attachment_rule_user_data_label`	Data is available in the `label` column of the `RUNBOOKS_ATTACHMENT_RULE_USER_DATA_VALUE` table.
column	Discontinued Column	`attachment_rule_user_data_type`	Data is available in the `type` column of the `RUNBOOKS_ATTACHMENT_RULE_USER_DATA_VALUE` table.
column	Discontinued Column	`attachment_rule_user_data_value`	Data is available in the `value` column of the `RUNBOOKS_ATTACHMENT_RULE_USER_DATA_VALUE` table.
`RUNBOOKS_ATTACHMENT_RULE_LOGIC`
table	Discontinued Table	`RUNBOOKS_ATTACHMENT_RULE_LOGIC`

Fivetran Platform Connector

We've introduced the new CONNECTION table, which replaces the deprecated CONNECTOR table. Additionally, we have deprecated several columns and introduced new ones.

TABLE NAME	DEPRECATED COLUMNS	NEW COLUMN
INCREMENTAL_MAR	CONNECTOR_ID, CONNECTOR_NAME	CONNECTION_NAME
RESOURCE_MEMBERSHIP	INTEGRATION_ID, CONNECTOR_ID	CONNECTION_ID
LOG	CONNECTOR_ID	CONNECTION_ID
CONNECTOR_SDK_LOG	CONNECTOR_ID	CONNECTION_ID
SOURCE_SCHEMA_METADATA	CONNECTOR_ID	CONNECTION_ID
SOURCE_TABLE_METADATA	CONNECTOR_ID	CONNECTION_ID
SOURCE_COLUMN_METADATA	CONNECTOR_ID	CONNECTION_ID
DESTINATION_SCHEMA_METADATA	CONNECTOR_ID	CONNECTION_ID
DESTINATION_TABLE_METADATA	CONNECTOR_ID	CONNECTION_ID
DESTINATION_COLUMN_METADATA	CONNECTOR_ID	CONNECTION_ID
SOURCE_SCHEMA_CHANGE_EVENT	CONNECTOR_ID	CONNECTION_ID
SOURCE_TABLE_CHANGE_EVENT	CONNECTOR_ID	CONNECTION_ID
SOURCE_COLUMN_CHANGE_EVENT	CONNECTOR_ID	CONNECTION_ID
DESTINATION_SCHEMA_CHANGE_EVENT	CONNECTOR_ID	CONNECTION_ID
DESTINATION_TABLE_CHANGE_EVENT	CONNECTOR_ID	CONNECTION_ID
DESTINATION_COLUMN_CHANGE_EVENT	CONNECTOR_ID	CONNECTION_ID

See the Fivetran Platform Connector documentation for details.

Kisi

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

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

1 total changes • 0 possible breaking changes

Table/column	Change type		Old name	New name	Notes
`PRESENCE`
table	New Table			`PRESENCE`

Linear

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

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
`PROJECT_LINK`
table	Discontinued Table		`PROJECT_LINK`

Microsoft Advertising

We have added the following metadata tables:

ASSET_GROUP_ATTRIBUTE_HISTORY
ASSET_GROUP_HISTORY

We have added the following reporting tables:

PRODUCT_DIMENSION_IMPRESSION_PERFORMANCE_MAX_DAILY_REPORT
PRODUCT_DIMENSION_IMPRESSION_PERFORMANCE_MAX_HOURLY_REPORT
PRODUCT_DIMENSION_PERFORMANCE_MAX_DAILY_REPORT
PRODUCT_DIMENSION_PERFORMANCE_MAX_HOURLY_REPORT

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

By default, we select all new tables for the sync. You can sync them for free until April 15, 2025. Be sure to exclude the tables that you don't want to count towards paid Monthly Active Rows (MAR) before this date.

Notion

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

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

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

1 total changes • 1 possible breaking changes

Table/column	Change type		Old name	New name	Notes
`PAGE`
column	Discontinued Column		`in_trash`

Planful

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

We are updating the connector schema to enhance its usability.

1 total changes • 0 possible breaking changes

Table/column	Change type		Old name	New name	Notes
`GL_DATA_ACTUAL_SCENARIO`
table	New Table			`GL_DATA_ACTUAL_SCENARIO`

Qmatic Data Connect

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

We are updating the connector schema to enhance its usability.

42 total changes • 0 possible breaking changes

Table/column	Change type	New name
`AGENT`
table	New Table	`AGENT`
`AGENT_DAEMON_EVENT`
table	New Table	`AGENT_DAEMON_EVENT`
`AGENT_DEVICE_CONTROLLER_STATUS`
table	New Table	`AGENT_DEVICE_CONTROLLER_STATUS`
`AGENT_DEVICE_STATUS`
table	New Table	`AGENT_DEVICE_STATUS`
`APPOINTMENT_CANCELLED_DATE`
table	New Table	`APPOINTMENT_CANCELLED_DATE`
`APPOINTMENT_CREATED_DATE`
table	New Table	`APPOINTMENT_CREATED_DATE`
`APPOINTMENT_CREATED_TIME`
table	New Table	`APPOINTMENT_CREATED_TIME`
`APPOINTMENT_END_TIME`
table	New Table	`APPOINTMENT_END_TIME`
`APPOINTMENT_START_TIME`
table	New Table	`APPOINTMENT_START_TIME`
`CALL_TIME`
table	New Table	`CALL_TIME`
`DAEMON_EVENT_TYPE`
table	New Table	`DAEMON_EVENT_TYPE`
`DAEMON_STATUS`
table	New Table	`DAEMON_STATUS`
`DAEMON_VERSION`
table	New Table	`DAEMON_VERSION`
`DATE`
table	New Table	`DATE`
`DELIVERED_SERVICE_TIME`
table	New Table	`DELIVERED_SERVICE_TIME`
`DEVICE`
table	New Table	`DEVICE`
`DEVICE_CONTROLLER`
table	New Table	`DEVICE_CONTROLLER`
`DEVICE_CONTROLLER_EVENT`
table	New Table	`DEVICE_CONTROLLER_EVENT`
`DEVICE_CONTROLLER_EVENT_TYPE`
table	New Table	`DEVICE_CONTROLLER_EVENT_TYPE`
`DEVICE_CONTROLLER_STATUS`
table	New Table	`DEVICE_CONTROLLER_STATUS`
`DEVICE_CONTROLLER_TIME`
table	New Table	`DEVICE_CONTROLLER_TIME`
`DEVICE_EVENT`
table	New Table	`DEVICE_EVENT`
`DEVICE_EVENT_TYPE`
table	New Table	`DEVICE_EVENT_TYPE`
`DEVICE_STATUS`
table	New Table	`DEVICE_STATUS`
`DEVICE_TIME`
table	New Table	`DEVICE_TIME`
`DIM_DEVICE_TYPE`
table	New Table	`DIM_DEVICE_TYPE`
`DIM_UNIT_TYPE`
table	New Table	`DIM_UNIT_TYPE`
`END_TIME`
table	New Table	`END_TIME`
`ENTERED_QUEUE_TIME`
table	New Table	`ENTERED_QUEUE_TIME`
`FACT_AGENT_JIQL_EVENT`
table	New Table	`FACT_AGENT_JIQL_EVENT`
`FEEDBACK_DATE`
table	New Table	`FEEDBACK_DATE`
`FEEDBACK_TIME`
table	New Table	`FEEDBACK_TIME`
`JIQL_EVENT_TYPE`
table	New Table	`JIQL_EVENT_TYPE`
`JIQL_STATUS`
table	New Table	`JIQL_STATUS`
`JIQL_VERSION`
table	New Table	`JIQL_VERSION`
`MARK_TRANSACTION_DATE`
table	New Table	`MARK_TRANSACTION_DATE`
`MARK_TRANSACTION_TIME`
table	New Table	`MARK_TRANSACTION_TIME`
`SERVICE_DELIVERED`
table	New Table	`SERVICE_DELIVERED`
`STAFF_SESSION_END_TIME`
table	New Table	`STAFF_SESSION_END_TIME`
`STAFF_SESSION_START_TIME`
table	New Table	`STAFF_SESSION_START_TIME`
`TIME`
table	New Table	`TIME`
`UNIT`
table	New Table	`UNIT`

Retently

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

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

1 total changes • 0 possible breaking changes

Table/column	Change type		Old name	New name	Notes
`FEEDBACK_TOPIC`
table	New Table			`FEEDBACK_TOPIC`

Rippling

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

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.

119 total changes • 50 possible breaking changes

Table/column	Change type	Old name	New name	Notes
`COMPANY`
table	New Table		`COMPANY`
`COMPANY_ACTIVITY`
table	Discontinued Table	`COMPANY_ACTIVITY`
`COMPANY_ACTIVITY_SUBJECT`
table	Discontinued Table	`COMPANY_ACTIVITY_SUBJECT`
`COMPANY_LEAVE_TYPE`
table	Discontinued Table	`COMPANY_LEAVE_TYPE`
`CUSTOM_FIELD`
column	Discontinued Column	`_fivetran_id` 🔑		No longer a primary key.
column	Discontinued Column	`caption`
column	Discontinued Column	`title`
column	New Column		`created_at`
column	New Column		`description`
column	Primary Key Change		`id` 🔑	New primary key.
column	New Column		`name`
column	New Column		`updated_at`
`DEPARTMENT`
column	Discontinued Column	`parent`
column	New Column		`created_at`
column	New Column		`parent_id`
column	New Column		`reference_code`
column	New Column		`updated_at`
`EMPLOYEE`
table	Discontinued Table	`EMPLOYEE`
`EMPLOYEE_POSSIBLE_NEW_EMPLOYMENT_TYPE`
table	Discontinued Table	`EMPLOYEE_POSSIBLE_NEW_EMPLOYMENT_TYPE`
`LEAVE_BALANCE`
table	Discontinued Table	`LEAVE_BALANCE`
`LEAVE_BALANCE_BALANCES`
table	Discontinued Table	`LEAVE_BALANCE_BALANCES`
`LEAVE_REQUEST`
table	Discontinued Table	`LEAVE_REQUEST`
`LEAVE_REQUEST_DATE`
table	Discontinued Table	`LEAVE_REQUEST_DATE`
`LEVEL`
column	Discontinued Column	`parent`
column	New Column		`created_at`
column	New Column		`description`
column	New Column		`global_level`
column	New Column		`parent_id`
column	New Column		`rank`
column	New Column		`track_created_at`
column	New Column		`track_id`
column	New Column		`track_name`
column	New Column		`track_updated_at`
column	New Column		`updated_at`
`TEAM`
column	Discontinued Column	`parent`
column	New Column		`created_at`
column	New Column		`parent_id`
column	New Column		`updated_at`
`TIME_ENTRY`
column	Discontinued Column	`company`
column	Discontinued Column	`duration`
column	Discontinued Column	`overtime_hours`
column	Discontinued Column	`pay_periodend_date`
column	Discontinued Column	`pay_periodpay_schedule`
column	Discontinued Column	`pay_periodstart_date`
column	Discontinued Column	`regular_hours`
column	Discontinued Column	`role_id`
column	Discontinued Column	`timezone`
column	New Column		`create_extra_hours_run`
column	New Column		`created_at`
column	New Column		`idempotency_key`
column	New Column		`pay_period_end_date`
column	New Column		`pay_period_schedule_id`
column	New Column		`pay_period_start_date`
column	New Column		`piece_rate_premiums`
column	New Column		`premiums`
column	New Column		`shift_input_values`
column	New Column		`status`
column	New Column		`tags`
column	New Column		`time_card_id`
column	New Column		`time_entry_summary_double_over_time_hours`
column	New Column		`time_entry_summary_duration`
column	New Column		`time_entry_summary_over_time_hours`
column	New Column		`time_entry_summary_regular_hours`
column	New Column		`updated_at`
column	New Column		`worker_id`
`TIME_ENTRY_BREAK`
column	Discontinued Column	`_fivetran_id` 🔑		No longer a primary key.
column	Discontinued Column	`description`
column	Discontinued Column	`is_ot_eligible`
column	Discontinued Column	`is_paid`
column	Primary Key Change	`time_entry_id`	`time_entry_id` 🔑	Added to primary key.
column	Primary Key Change		`break_type_id` 🔑	New primary key.
column	New Column		`original_end_time`
column	New Column		`original_start_time`
`TIME_ENTRY_JOB_SHIFT`
column	Discontinued Column	`_fivetran_id` 🔑		No longer a primary key.
column	Discontinued Column	`job_codes`
column	Primary Key Change	`time_entry_id`	`time_entry_id` 🔑	Added to primary key.
column	Primary Key Change		`index` 🔑	New primary key.
column	New Column		`is_hours_only_input`
column	New Column		`job_codes_id`
column	New Column		`original_end_time`
column	New Column		`original_start_time`
`TIME_ENTRY_SEGMENT`
table	New Table		`TIME_ENTRY_SEGMENT` 🔑	Child table of the `TIME_ENTRY` table.
`TIMECARD`
column	Discontinued Column	`approved_hours`
column	Discontinued Column	`earnings`
column	Discontinued Column	`job_codes`
column	Discontinued Column	`overtime_hours`
column	Discontinued Column	`paid_hours`
column	Discontinued Column	`pay_periodend_date`
column	Discontinued Column	`pay_periodpay_schedule`
column	Discontinued Column	`pay_periodstart_date`
column	Discontinued Column	`premiums`
column	Discontinued Column	`regular_hours`
column	Discontinued Column	`role_id`
column	Discontinued Column	`total_holiday_hours`
column	Discontinued Column	`total_hours`
column	Discontinued Column	`total_paid_time_off_hours`
column	Discontinued Column	`total_unpaid_time_off_hours`
column	New Column		`created_at`
column	New Column		`pay_period_end_date`
column	New Column		`pay_period_schedule_id`
column	New Column		`pay_period_start_date`
column	New Column		`summary_approved_hours`
column	New Column		`summary_double_overtime_hours`
column	New Column		`summary_earnings`
column	New Column		`summary_hours_worked_by_job_code`
column	New Column		`summary_overtime_hours`
column	New Column		`summary_paid_hours`
column	New Column		`summary_premiums`
column	New Column		`summary_regular_hours`
column	New Column		`summary_total_holiday_hours`
column	New Column		`summary_total_hours`
column	New Column		`summary_total_paid_time_off_hours`
column	New Column		`summary_total_unpaid_time_off_hours`
column	New Column		`summary_unpaid_break_hours_by_entry`
column	New Column		`updated_at`
column	New Column		`worker_id`
`USERS`
table	New Table		`USERS`
`WORK_LOCATION`
table	New Table		`WORK_LOCATION`
`WORKER`
table	New Table		`WORKER`

Stripe

We have added a new table, PAYOUT_BALANCE_TRANSACTION, which contains the following columns:

PAYOUT_ID
BALANCE_TRANSACTION_ID

You can use this table instead of referencing PAYOUT_ID in the BALANCE_TRANSACTION table, as PAYOUT_ID will no longer be populated in BALANCE_TRANSACTION after April 30, 2025.

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

Workday Financial Management

We have made the following schema changes to the connector:

Table Name	New Primary Key Column(s)
`BILLING_INSTALLMENT_LINE`	`billing_schedule_id`
`BILLING_INSTALLMENT_LINE_TAX_APPLICABILITY`	`billing_installment_id`, `billing_schedule_id`
`BILLING_INSTALLMENT_LINE_TAX_CODE`	`billing_installment_id`, `billing_schedule_id`
`BILLING_INSTALLMENT_LINE_WORKTAG`	`billing_installment_id`, `billing_schedule_id`
`BILLING_INSTALLMENT_MILESTONE`	`billing_schedule_id`
`BILLING_INSTALLMENT_STATUS`	`billing_schedule_id`
`BILLING_SCHEDULE_PREPAID_INSTALLMENT`	`billing_schedule_id`
`BILLING_SCHEDULE_PREPAID_INSTALLMENT_MILESTONE`	`prepaid_installment_and_mapping_id`, `billing_schedule_id`
`BILLING_SCHEDULE_PREPAID_MAPPING`	`billing_schedule_id`
`LINE_OVERRIDE_DEFAULT`	`revenue_allocation_configuration_id`
`PREPAID_MAPPING_CUSTOMER_CONTRACT_LINE`	`prepaid_mapping_id`, `billing_schedule_id`
`REVENUE_RECOGNITION_INSTALLMENT_HOLD_REASON`	`revenue_recognition_schedule_id`
`REVENUE_RECOGNITION_INSTALLMENT_LINE`	`revenue_recognition_schedule_id`
`REVENUE_RECOGNITION_INSTALLMENT_LINE_WORKTAG`	`revenue_recognition_installment_id`, `revenue_recognition_schedule_id`
`REVENUE_RECOGNITION_INSTALLMENT_MILESTONE`	`revenue_recognition_schedule_id`
`REVENUE_RECOGNITION_INSTALLMENT_STATUS`	`revenue_recognition_schedule_id`
`SALES_ITEM_ALLOWED_WORKTAG`	`sales_item_id`
`SALES_ITEM_FAIR_VALUE_PRICE_LIST_RULE_LINE_WORKTAG`	`sales_item_fair_value_price_list_id`
`SALES_ITEM_PRICE_LIST_RULE_LINE_CONTRACT_LINE_TYPE`	`sales_item_price_list_id`
`SALES_ITEM_PRICE_LIST_RULE_LINE_WORKTAG`	`sales_item_price_list_id`
`SALES_ITEM_TIERED_PRICING`	`sales_item_price_list_id`

We will perform a free re-sync for the above tables to backfill the old data.

Workday HCM

We have added the following new tables to support the Performance_Management module:

ACCOMPLISHMENT_COMPONENT
ACCOMPLISHMENT_SECTION
ADDITIONAL_MANAGER_ACCOMPLISHMENT_COMPONENT
ADDITIONAL_MANAGER_ACCOMPLISHMENT_SECTION
ADDITIONAL_MANAGER_CAREER_SECTION
ADDITIONAL_MANAGER_COMPETENCY_COMPONENT
ADDITIONAL_MANAGER_COMPETENCY_SECTION
ADDITIONAL_MANAGER_DEVELOPMENT_ITEM_COMPONENT
ADDITIONAL_MANAGER_DEVELOPMENT_ITEM_SECTION
ADDITIONAL_MANAGER_FEEDBACK_SECTION
ADDITIONAL_MANAGER_GOAL_COMPONENT
ADDITIONAL_MANAGER_GOAL_SECTION
ADDITIONAL_MANAGER_OVERALL_EVALUATION
ADDITIONAL_MANAGER_QUESTION_COMPONENT
ADDITIONAL_MANAGER_QUESTION_SECTION
ADDITIONAL_MANAGER_RESPONSIBILITY_COMPONENT
ADDITIONAL_MANAGER_RESPONSIBILITY_SECTION
CAREER_INTEREST_COMPONENT
CAREER_SECTION
COMPETENCY_COMPONENT
COMPETENCY_SECTION
DEVELOPMENT_AREA_COMPONENT
DEVELOPMENT_ITEM_COMPONENT
DEVELOPMENT_ITEM_SECTION
EMPLOYEE_REVIEW
FEEDBACK_SECTION
GOAL_COMPONENT
GOAL_MILESTONE_DETAIL
GOAL_SECTION
OVERALL_EVALUATION
POST_EVALUATION_FEEDBACK
QUESTION_COMPONENT
QUESTION_SECTION
RESPONSIBILITY_COMPONENT
RESPONSIBILITY_SECTION
REVIEW_QUESTION
REVIEW_QUESTION_CATEGORY
REVIEW_TYPE

Wrike

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

We are updating the connector schema to fix a bug.

5 total changes • 0 possible breaking changes

Table/column	Change type	New name
`FOLDER_TASK`
column	New Column	`custom_item_id`
column	New Column	`recurrent`
column	New Column	`responsible_allocation`
`SPACE_TASK`
column	New Column	`custom_item_id`
column	New Column	`recurrent`

Zip

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

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

41 total changes • 0 possible breaking changes

Table/column	Change type	New name
`AGREEMENT`
column	New Column	`amount`
column	New Column	`auto_renews`
column	New Column	`display_renewal_status`
column	New Column	`opt_out_date`
column	New Column	`renewal_workflow_id`
`AUDIT_LOG`
column	New Column	`data`
`INVOICE`
column	New Column	`payment_terms`
`PURCHASE_ORDER`
column	New Column	`agreement_number`
column	New Column	`amount_billed`
column	New Column	`category_category_type`
column	New Column	`category_id`
column	New Column	`category_name`
column	New Column	`category_status`
column	New Column	`created_at`
column	New Column	`created_by_id`
column	New Column	`end_date`
column	New Column	`external_id`
column	New Column	`location_id`
column	New Column	`payment_frequency`
column	New Column	`payment_method`
column	New Column	`payment_terms`
column	New Column	`requester_id`
column	New Column	`start_date`
column	New Column	`subcategory_category_type`
column	New Column	`subcategory_id`
column	New Column	`subcategory_name`
column	New Column	`subcategory_status`
column	New Column	`subcategory_type`
`PURCHASE_ORDER_ATTRIBUTE`
table	New Table	`PURCHASE_ORDER_ATTRIBUTE`
`PURCHASE_ORDER_LINE_ITEM_ATTRIBUTE`
table	New Table	`PURCHASE_ORDER_LINE_ITEM_ATTRIBUTE`
`REQUEST`
column	New Column	`link`
`REQUEST_ATTRIBUTE`
column	New Column	`integration_data_id`
column	New Column	`integration_data_key`
column	New Column	`integration_data_name`
column	New Column	`integration_data_type`
`REQUEST_PRICE_LINE_ITEM_ATTRIBUTE`
table	New Table	`REQUEST_PRICE_LINE_ITEM_ATTRIBUTE`
`USER_ATTRIBUTE`
table	New Table	`USER_ATTRIBUTE`
`VENDOR`
column	New Column	`duns_number`
column	New Column	`tax_id_number`
column	New Column	`vat_number`
`VENDOR_CREDIT`
column	New Column	`applied_invoices`

Improvements

Afterpay

The Afterpay connector's priority-first sync now fetches data from the most recent 120 days. Previously, the priority fetch period was 90 days.

AWS CloudWatch

We now support AWS CloudWatch in Hybrid Deployment. For more information, see our setup guide.

AWS Cost and Usage Reports

Our AWS Cost and Usage Reports connector is now generally available. Read our AWS Cost and Usage Reports connector documentation.

Braze

We have added a new field, Sync data from selected date, under the Historical Sync Time Frame dropdown in the setup form. This allows you to select the exact date up to which the backward sync will occur. The default value is Sync all historical data. You can edit the connection details and update the time frame for an existing connector.

This limit applies to the following tables:

ATTRIBUTION_EVENT
CAMPAIGN_CONTROL_ENROLLMENT_EVENT
CAMPAIGN_CONVERSION_EVENT
CANVAS_CONVERSION_EVENT
CANVAS_ENTRY_EVENT
CANVAS_EXIT_EVENT
CANVAS_EXPERIMENT_STEP_CONVERSION_EVENT
CANVAS_EXPERIMENT_STEP_ENTRY_EVENT
CONTENT_CARD_EVENT
CUSTOM_EVENT
EMAIL_EVENT
IN_APP_MESSAGE_EVENT
LOCATION_EVENT
NEWSFEED_CARD_EVENT
NEWSFEED_IMPRESSION_EVENT
PURCHASE_EVENT
PUSH_NOTIFICATION_EVENT
RANDOM_BUCKET_NUMBER_EVENT
SESSION_EVENT
SMS_EVENT
SUBSCRIPTION_EVENT
UNINSTALL_EVENT
WEBHOOK_EVENT
WHATSAPP_EVENT

We are gradually rolling out this feature to all connections.

Close

We have updated the sync strategy for the CUSTOM_ACTIVITY_INSTANCE table. We now incrementally sync the table to capture updates and re-import it once a week to capture deletes.

Gmail

You can now opt to specify the User ID field in the connection setup form.

Google Sheets

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

Harvest

We no longer re-import the TIME_ENTRY table to capture updates and deletes.

Oracle Business Intelligence Publisher

We can now sync your custom data models.

Pardot

This limit applies to the following tables:

EMAIL
EXTERNAL_ACTIVITY
LIST_MEMBERSHIP
VISITOR_ACTIVITY
VISITOR_PAGE_VIEW

We are gradually rolling out this feature to all connections.

Persona

We now sync data from the INQUIRY table starting from the year 2018.

Sailthru

This limit applies to the following tables:

CAMPAIGN_QUERY
PURCHASE
PURCHASE_ITEM

We are gradually rolling out this feature to all connections.

Salesforce

We have resolved an issue in our DateValue formula function translation. In Salesforce, when converting a datetime to a date, Salesforce first adjusts the input to the current user's timezone before performing the calculation. Previously, our translation did not account for this implicit timezone conversion, causing inconsistencies. This has now been fixed to ensure accurate date computations.

Salesforce Marketing Cloud

We have replaced the historical sync time frame dropdown in the setup form with a date picker, enabling you to select the exact date up to which the backward sync will occur.

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 Historical Sync Limit Date from date picker. You can edit the connection details and set the time frame value for an existing connector.

This limit applies to the following tables:

CHAT_INBOUND_MESSAGE_LOG
CHAT_POTENTIAL_UNSUBS
CHAT_TRACKING
EVENT
MOBILE_PUSH_DETAIL_EXTRACT
SMS_MESSAGE_TRACKING_DATA_VIEW

We are gradually rolling out this feature to all connections.

SAP OData

We now support the AWS PrivateLink and Azure Private Link connection methods available only for Business Critical accounts.

For more information, see our SAP Odata Setup Guide.

Stripe

We have updated our sync strategy. We now re-import the ACCOUNT table once weekly. Previously, we re-imported the table daily. We are gradually rolling out this change to all existing connections.

WooCommerce

We now retrieve historical data only upto January 1, 2015, for the COUPON, ORDERS, and PRODUCT tables.

Workday Financial Management

Our Workday Financial Management connector now allows you to select between an API client and an API client for integrations on the setup page when configuring the connector. For more information, see our Workday Financial Management connector documentation.

Workday HCM

Our Workday HCM connector now allows you to select between an API client and an API client for integrations on the setup page when configuring the connector. For more information, see our Workday HCM connector documentation.

Workday RaaS

We have now added the option to add multiple reports to a single connection.

We have enhanced the process to add dynamic parameters to your reports in the setup form.

We now support large report (> 2gb) syncs given dynamic parameters are enabled for the report.

This change is applicable for new connections only. For existing connectors, you need to create multiple connections to sync multiple reports.

Zip

We have updated our sync strategy for the APPROVAL table. We now capture updates for the APPROVAL table in every sync using the updated_at API parameter. Previously, we used the created_at parameter.

We have updated our sync strategy for the PURCHASE_ORDER table. We now capture updates for the PURCHASE_ORDER table in every sync using the last_updated_after and last_updated_before API parameters. Previously, we used the created_after and created_before parameters.

REST API Improvements

Additional fields in the List all roles response

The response of the List all roles endpoint has been expanded with the following fields:

is_deprecated: defines whether the role is deprecated
replacement_role_name: the name of the new role replacing the deprecated role.

Enforcing Base64URL encoding for certificate and fingerprint hashes in path parameters

We are now requiring Base64URL encoding for certificate and fingerprint hashes in the REST API request path-parameters for the following endpoints:

The certificate and fingerprint hashes in the REST API response body are still returned in raw format. The new id field is added to the response body of all certificate and fingerprint endpoints. This field contains the Base64URL encoded certificate or fingerprint hash.

Using the raw format for certificate and fingerprint hashes in the request path-params is deprecated and will no longer be supported as of May 1, 2025.

March 2025

Connector SDK

fivetran-connector-sdk PyPI package

Fivetran AWS EU Servers

Lite Connectors

Logs

New attributes in log events

Transformations for dbt Core

Deprecated transformation log events

Updated dbt Quickstart packages

New connectors

Adobe Commerce

Db2 for LUW

Schema changes

Aha!

Alchemer

Auth0

BigCommerce

Chargebee Product Catalog 2.0

Cin7 Core

Close

Coupa

Facebook Pages

Factbird

FireHydrant

Fivetran Platform Connector

Kisi

Linear

Microsoft Advertising

Notion

Planful

Qmatic Data Connect

Retently

Rippling

Stripe

Workday Financial Management

Workday HCM

Wrike

Zip

Improvements

Afterpay

AWS CloudWatch

AWS Cost and Usage Reports

Braze

Close

Gmail

Google Sheets

Harvest

Oracle Business Intelligence Publisher

Pardot

Persona

Sailthru

Salesforce

Salesforce Marketing Cloud

SAP OData

Stripe

WooCommerce

Workday Financial Management

Workday HCM

Workday RaaS

Zip

REST API Improvements

Additional fields in the List all roles response

Enforcing Base64URL encoding for certificate and fingerprint hashes in path parameters

`fivetran-connector-sdk` PyPI package