F
AI Connector Agent
The AI Connector Agent is now generally available.Read our AI Connector Agent documentation.
F
Intercom
We have added the following new tables: COMPANY_NOTE_HISTORY CONTACT_MERGE CONVERSATION_EXTERNAL_REFERENCE CONVERSATION_MONITOR_EVALUATION CONVERSATION_SCORECARD DATA_CONNECTOR DATA_CONNECTOR_EXECUTION SIDE_CONVERSATION_PART We have added the following new columns: Table Columns ARTICLE_HISTORY ai_chatbot_availability, ai_copilot_availability, ai_sales_agent_availability, body_markdown, created_by…
F
Azure DevOps
We have made the following changes to improve incremental syncs for the COMMIT table: We now maintain a separate sync cursor for each repository, which reduces unnecessary re-fetching of historical commits. We now send the cursor to Azure DevOps in 24-hour UTC format with an explicit Z timezone designator. Previously, the cursor used a 12-hour format without a timezone, which could cause Fivetran…
F
commercetools
We have added a new column, purchase_order_number, to the ORDERS table.
F
TikTok Organic
We have added a new field, TikTok API rate limit tier, to the connection setup form. The field lets you match the connector's request rate to the rate limit tier TikTok has approved for your developer app (Basic, Advanced, Premium, or Ultimate), so that your syncs can run faster if your app has a higher tier.The field defaults to Basic, so existing connections continue to sync at the same rate. Se…
F
Slack
For CHANNEL_MEMBER, we now sync members from all channels to the existing table. Previously, we synced only members from channels where the app is installed.
F
QuickBooks
We have fixed an issue that incorrectly deleted records in the TAX_RATE_DETAIL table when either the sales or purchase tax rate list associated with a tax code was empty. By default, we will re-sync the TAX_CODE and TAX_RATE_DETAIL tables to restore these records. This re-sync counts toward free Monthly Active Rows (MAR). We are gradually rolling out this enhancement to all existing connections.
F
Managed Data Lake Service
We have deprecated the Retain All Snapshots option for the Snapshot Retention Period setting in the destination setup form. You can no longer select it for new destinations, and you can't switch an existing destination to it in the setup form or with the REST API. If your destination already uses Retain All Snapshots, you don't need to do anything. Otherwise, select another retention period.We are…
F
Release Notes
Fivetran Connector SDK We now support deferred truncate for Connector SDK connections. Refer to deferred truncate for more details.fivetran-connector-sdk PyPI package We have released version 3.1.0 of the fivetran-connector-sdk PyPI package. This release includes the following updates: Added support for deferred truncate, which marks a table's existing rows as deleted only after the sync completes…
F
Modify Destination Schema Names Before the Initial Sync
The Update a Connection endpoint now accepts the destination_schema_names parameter. Previously, the endpoint ignored this parameter, so you could change the setting only in the dashboard.You can set destination_schema_names to FIVETRAN_NAMING or SOURCE_NAMING only before the connection's initial sync. After the initial sync starts, you can only send the value that's already set. Attempting to cha…
F
Oracle Fusion Cloud Applications
We have added a new toggle, Disable Effective Date Filtering, to the connection setup form to support the extraction of historical data without applying any filters for an effective date. You must set the toggle to ON if you want to disable Oracle BICC effective date filtering and include records outside Oracle's default effective date range across all datastores in the connection.{% note %} This…
F
Managed Data Lake Service
We’ve added a Storage region drop-down field to the Managed Data Lake Service setup form for all storage providers. When setting up a new destination, you can now select a region from the drop-down menu, which lists only regions supported by Fivetran. Choosing one of these regions helps us process your data closer to where it’s stored, which can help reduce data egress costs.For existing destinati…
F
Katana
We now support syncing empty batch stock records with an inventory value of 0 to the BATCH table. To support this enhancement, we have added a new parameter, include_empty=true, to the Katana API to retrieve these records.
F
Connector SDK Package ID in Connection Details
The Retrieve Connection Details endpoint now returns a connector_sdk_package_id field for Connector SDK connections. The field contains the ID of the package currently used for the connection.Use the package ID with the Retrieve Connector SDK Package Details and Download Connector SDK Package endpoints to inspect or download the connection's source code, for example to investigate a sync failure.…
F
MaintainX
We have changed our sync strategy for the ASSET table. We now re-import this table weekly to capture updates. Previously, we incremental synced this table.
F
Loop
We have changed the data type of the purchase_price column of the ADVANCED_SHIPPING_NOTICE table to STRING.
F
Maxio SaaSOptics
We now sync fields that the Maxio SaaSOptics API returns for the TRANSACTION table but that are not part of our predefined schema. You can find these fields as additional columns in your destination, named after the API field names. To backfill historical data, re-sync the TRANSACTION table.
F
Hybrid Deployment
We have updated the hostnames used by the Hybrid Deployment Agent: gateway.fivetran.com replaces ldp.orchestrator.fivetran.com hdt.gateway.fivetran.com replaces hdt.orchestrator.fivetran.com Fivetran will retire the existing hostnames on January 31, 2027. Before then, add the new hostnames to your outbound firewall or security group rules to ensure uninterrupted connectivity.The associated IP addr…
F
Claude
Our Claude connector is now generally available.Read our Claude connector documentation.
F
dbt platform
We have renamed the dbt Cloud connector to dbt platform.
F
Ceridian Dayforce
We now sync future data for the following tables: AVAILABILITY: up to 12 months from the current date. EMPLOYEE_SCHEDULE: up to 13 days from the current date.
F
Firebase
Starting November 15, 2026, the Capture Deletes option applies only to top-level collections. We no longer detect deletions in subcollections during incremental syncs. To reflect these deletions in your destination, re-sync the affected table. For more information, see Deleted rows.
F
Salesforce
We have changed our sync strategy for the Salesforce tables with the Attribute or Attr suffix. We now re-import these tables.We now apply your Salesforce row filters while fetching data during your tables' historical syncs and re-imports. We retrieve only the rows that match your filter, so your connection uses fewer API calls. For more information, see our Salesforce documentation.You can now inc…
F
Salesforce
We have changed our sync strategy for the Salesforce tables with the Attribute or Attr suffix. We now re-import these tables.You can now include inactive records (soft-deleted records and historical versions) in transformation-based formula field models by enabling Include inactive records in formula field models under Show Advanced Options in your connection setup form. For inactive records, cros…
F
ServiceTitan
We now capture deletes for the EMPLOYEE_PAYROLL_SETTING and TECHNICIAN_PAYROLL_SETTING tables. When a record is deleted in the source, we set the _fivetran_deleted column to true for the corresponding row in your destination. Previously, we did not capture these source deletions in your destination.
F
Sentry
We now capture deletes for the PROJECT_ISSUE table. When a record is deleted in the source, we set the _fivetran_deleted column to true for the corresponding row in your destination. Previously, we did not capture these source deletions in your destination.
F
Rootly
We now capture deletes for the ACTION_ITEM table. When a record is deleted in the source, we set the _fivetran_deleted column to true for the corresponding row in your destination. Previously, we did not capture these source deletions in your destination.
F
Maxio Chargify
We now capture deletes for the COUPON table. When a record is deleted in the source, we set the _fivetran_deleted column to true for the corresponding row in your destination. Previously, we did not capture these source deletions in your destination.
F
Linear
We now capture deletes for the INITIATIVE_HISTORY table. When a record is deleted in the source, we set the _fivetran_deleted column to true for the corresponding row in your destination. Previously, we did not capture these source deletions in your destination.
F
Heartland Retail POS
We now capture deletes for the SALE_TICKET_LINE table. When a record is deleted in the source, we set the _fivetran_deleted column to true for the corresponding row in your destination. Previously, we did not capture these source deletions in your destination.