August 2023

Lite Connectors

Lite connectors are now available for the following sources:

Transformations for dbt Core

dbt Core versions 1.5.6, 1.6.0, 1.6.1 support

We now support dbt Core version 1.5.6, 1.6.0, and 1.6.1. You can use these versions to run your projects.

For the above-mentioned versions of dbt Core, we don't support SQL Server, Azure Synapse, and MySQL destinations. These destinations are not currently supported by custom dbt Core adapters.

Also, we now support SQL Server destination for 1.4.5 version of dbt Core.

* dbt Core is a trademark of dbt Labs, Inc. All rights therein are reserved to dbt Labs, Inc. Fivetran Transformations is not a product or service of or endorsed by dbt Labs, Inc.

Schema changes

BambooHR

We have deprecated the employee_id column from the GOAL table and added a new table, EMPLOYEE_GOAL, in order to sync data related to goals shared among several employees.

Chargebee Product Catalog 1.0

We have added the following new tables:

ADDON_METADATA
COUPON_ADDON
COUPON_SET_METADATA
CREDIT_NOTE_DISCOUNT
CREDIT_NOTE_LINKED_REFUND
CREDIT_NOTE_LINKED_TAX_WITHHELD_REFUND
CREDIT_NOTE_TAX
CUSTOMER_BALANCE
CUSTOMER_ENTITY_IDENTIFIER
CUSTOMER_METADATA
GIFT_TIMELINE
INVOICE_DISCOUNT
INVOICE_LINKED_ORDER
INVOICE_LINKED_PAYMENT
INVOICE_LINKED_TAXES_WITHHELD
INVOICE_NOTE
INVOICE_TAX
LINE_ITEM
LINE_ITEM_TAX
PAYMENT_SOURCE_MANDATE
PLAN_METADATA
QUOTE_DISCOUNT
QUOTE_TAX
SUBSCRIPTION_ESTIMATE
SUBSCRIPTION_METADATA
SUBSCRIPTION_RENEWAL_CREDIT_NOTE_ESTIMATE
SUBSCRIPTION_RENEWAL_ESTIMATE
SUBSCRIPTION_RENEWAL_INVOICE_LINE_ITEM
SUBSCRIPTION_RENEWAL_UNBILLED_CHARGE_ESTIMATE
TIER

We have renamed the following tables:

INVOICE_ALLOCATION to CREDIT_NOTE_INVOICE_ALLOCATION
ORDER to ORDERS
PLAN_COUPON to COUPON_PLAN

We have changed the primary keys of the following tables:

CREDIT_NOTE_LINE_ITEM_DISCOUNT
INVOICE
INVOICE_APPLIED_CREDIT
INVOICE_DUNNING_ATTEMPT
INVOICE_LINE_ITEM_DISCOUNT
ORDER_LINE_ITEM_DISCOUNT
ORDER_LINKED_CREDIT_NOTE
QUOTE_LINE_ITEM_DISCOUNT
QUOTE_LINE_ITEM_TIER
SUBSCRIPTION
SUBSCRIPTION_ADDON
SUBSCRIPTION_COUPON
SUBSCRIPTION_EVENT_BASED_ADDON

We have combined the following line item tables into the new table, LINE_ITEM:

CREDIT_NOTE_LINE_ITEM
INVOICE_LINE_ITEM
QUOTE_LINE_ITEM

We have combined the following line item tax tables into the new table, LINE_ITEM_TAX:

CREDIT_NOTE_LINE_ITEM_TAX
INVOICE_LINE_ITEM_TAX
ORDERS_LINE_ITEM_TAX
QUOTE_LINE_ITEM_TAX

We have combined the tiers column of the following tables into the new table, TIER:

ADDON
PLAN
UNBILLED_CHARGE

We have added a new column, customer_id, to the PROMOTIONAL_CREDIT table.

We have added a new column, cn_reason_code, to the TRANSACTION_LINKED_CREDIT_NOTE table.

We have added a new column, coupon_id, to the following tables:

CREDIT_NOTE_LINE_ITEM_DISCOUNT
INVOICE_LINE_ITEM_DISCOUNT
QUOTE_LINE_ITEM_DISCOUNT

We have added two new columns, invoice_date and invoice_status columns, to the CREDIT_NOTE_INVOICE_ALLOCATION table.

We have added two new columns, txn_amount and txn_status, to the INVOICE_DUNNING_ATTEMPT table.

We have added two new columns, apply_till and coupon_code, to the SUBSCRIPTION_COUPON table.

We have added the following new columns to the CREDIT_NOTE table:

business_enity_id
channel
credit_note_billing_address_*
credit_note_shipping_address_*
customer_id
deleted
e_invoice_id
e_invoice_message
e_invoice_status
generated_at
reference_invoice_id
subscription_id

We have added the following new columns to the INVOICE_APPLIED_CREDIT table:

cn_create_reason_code
cn_date
cn_reason_code
cn_status

We have added the following new columns to the TRANSACTION table:

customer_id
deleted
iin
last_4
payment_method_details
payment_source_id
reference_authorization_id
reference_transaction_id
refunded_txn_id
reversal_transaction_id
subscription_id

We have added the following new columns to the UNBILLED_CHARGE table:

customer_id
deleted
is_advance_charge
subscription_id
updated_id

We have made the following changes to the ADDON table:

added the following new columns:
- channel
- hsn_code
- object
removed the tiers column

We have made the following changes to the COUPON_SET table:

added a new column, coupon_id
removed the object column

We have made the following changes to the CUSTOMER table:

added the following new columns:
- backup_payment_source_id
- billing_month
- business_entity_id
- channel
- deleted
- einvoicing_method
- entity_identifier_scheme
- entity_identifier_standard
- is_einvoice_enabled
- primary_payment_source_id
removed the following columns:
- balances
- payment_method_gateway
- payment_method_gateway_account_id
- payment_method_object
- payment_method_reference_id
- payment_method_status
- payment_method_type

We have made the following changes to the GIFT table:

added a new column, claim_expiry_date
removed the gift_receiver_object column

We have made the following changes to the INVOICE table:

added the following new columns:
- channel
- customer_id
- deleted
- einvoice_id
- einvoice_message
- einvoice_status
- generated_at
- is_written_off
- subscription_id
- tax_override_reason
- use_for_proration
- write_off_date
removed the discounts and taxes columns

We have made the following changes to the ORDER_LINE_ITEM table:

added two new columns, invoice_id and invoice_line_item_id
renamed the line_items_id column to id

We have made the following changes to the ORDERS table:

added the following new columns:
- invoice_id
- subscription_id
- customer_id
- original_order_id
- deleted
- gift_id
- shipping_address_index
removed the order_line_item column

We have made the following changes to the PAYMENT_SOURCE table:

added the following new columns:
- amazon_payment_agreement_id
- amazon_payment_email
- bank_account_email
- bank_account_first_name
- bank_account_last_name
- business_entity_id
- customer_id
- deleted
- paypal_agreement_id
- paypal_email
- upi_vpa
renamed the following columns:
- bank_account_account_holder_type to bank_account_holder_type
- column bank_account_account_type to bank_account_type

We have made the following changes to the PLAN table:

added the following new columns:
- channel
- charge_model
- hsn_code
- object
removed the following columns:
- charge_once
- ending_unit_in_decimal
- on_event
- quantity_in_decimal
- starting_unit_in_decimal
- tiers
- type

We have made the following changes to the QUOTE table:

added the following new columns:
- customer_id
- deleted
- invoice_id
- shipping_address_index
- subscription_id
removed the shipping_address_object column

We have made the following changes to the SUBSCRIPTION table:

added the following new columns:
- business_entity_id
- changes_scheduled_at
- channel
- customer_id
- deleted
- gift_id
- payment_source_id
- plan_id
removed the contract_term_object and shipping_address_object columns

We have made the following changes to the VIRTUAL_BANK_ACCOUNT table:

added two new columns, customer_id and deleted
removed the customer_id column

We have removed the addon_ids column from the COUPON table.

We have removed the object column from the following tables:

COMMENT
COUPON_CODE
SITE_MIGRATION_DETAIL

If you want to sync historical data for these tables and columns, contact our support team.

In the CUSTOMER_REFERRAL_URL table, the customer_id column refers to the external customer ID in the referral system.

Chargebee Product Catalog 2.0

We have added the following new tables:

COUPON_METADATA
EVENT_METADATA
ITEM_METADATA
ITEM_PRICE_METADATA
PAYMENT_SOURCE_MANDATE
PRICE_TIER
SUBSCRIPTION_METADATA

We have combined the DIFFERENTIAL_PRICE_TIER and ITEM_PRICE_TIER tier tables into a new table, PRICE_TIER.

We have renamed the ORDER table to ORDERS.

We have made the following changes to the COUPON_ITEM_CONSTRAINT table:

Renamed the constraint column to constraints
Added the item_type column to the set of composite primary keys

We have made the following changes to the CREDIT_NOTE_LINKED_REFUND and INVOICE_LINKED_PAYMENT tables:

Renamed the txn_id column to transaction_id
Removed the txn_amount, txn_date, and txn_status columns

We have made the following changes to the EVENT table:

Renamed the user column to users
Removed the metadata_* column

We have made the following changes to the INVOICE_ADJUSTMENT_CREDIT_NOTE and INVOICE_ISSUED_CREDIT_NOTE tables:

Renamed the cn_id column to credit_note_id
Removed the cn_create_reason_code, cn_date, cn_reason_code, cn_status, and cn_total columns

We have made the following changes to the INVOICE_APPLIED_CREDIT table:

Renamed the cn_id column to credit_note_id
Removed the cn_create_reason_code, cn_date, cn_reason_code, and cn_status columns

We have made the following changes to the INVOICE_LINKED_ORDER table:

Renamed the id column to order_id
Removed the batch_id, created_at, document_number, fulfilment_status, order_type, reference_id, and status columns

We have made the following changes to the ITEM_PRICE table:

Added a new column, accounting_detail_sku
Removed the metadata_* column

We have made the following changes to the SUBSCRIPTION_ITEM_TIER_PRICE table:

Added a new column, index
Removed the price and price_in_decimal columns

We have made the following changes to the TRANSACTION_LINKED_CREDIT_NOTE table:

Renamed the cn_id column to credit_note_id
Removed the cn_create_reason_code, cn_date, and cn_reference_invoice_id columns

We have made the following changes to the TRANSACTION_LINKED_PAYMENT table:

Renamed the transaction_txn_id column to transaction_id
Removed the amount, date, and status columns

We have renamed the following columns in the COUPON_APPLICABLE_ITEM_PRICE table:

coupon_item_constraint_constraint to coupon_item_constraints
coupon_item_constraint_item_type to coupon_item_constraint_type

We have renamed the gift_receiver_customer_id column to gift_receiver in the GIFT table.

We have renamed the following columns in the SUBSCRIPTION table:

auto_close_invoices to auto_close_invoice
mrr to monthly_reccuring_revenue

We have renamed the following columns in the TRANSACTION table:

iin to issuer_identification_number
last4 to last_4
txn_id to refunded_transaction_id

We have renamed the following columns in the TRANSACTION_REFUND table:

refunded_txn_id to refunded_transaction_id
txn_amount to transaction_amount
txn_date to transaction_date
txn_status to transaction_status

We have added a new column, recurring, to the INVOICE table.

We have removed the metadata_* column from the COUPON and ITEM tables.

We have removed the following columns from the CREDIT_NOTE_INVOICE_ALLOCATION table:

allocated_at
invoice_date
invoice_status

We have removed the txn_amount and txn_status columns from the INVOICE_DUNNING_ATTEMPT table.

We have removed the following columns from the ORDER_LINKED_CREDIT_NOTE table:

amount
amount_adjusted
amount_refunded
status
type

We have removed the following columns from the SUBSCRIPTION_ITEM_PRICE table:

current_term_end
free_quantity
free_quantity_in_decimal
next_billing_at
trial_end

We have removed the following columns from the TRANSACTION_INVOICE table:

invoice_date
invoice_total
invoice_status

Freshservice

We have added a new column, display_key, to the PROJECT_TASK table.

GitHub

We have added the following new columns to the PULL_REQUEST table:

active_lock_reason
closed_at
created_at
updated_at

Google Ads

We have added three new Metadata tables:

CAMPAIGN_SHARED_SET
SHARED_CRITERION
SHARED_SET

Gorgias

We have added a new table, MESSAGES.

We have renamed the SURVEY table to SATISFACTION_SURVEY.

Height

We have added a new column, completedByUserId, to the TASK table.

Iterable

We have made the following schema changes for the connections created before August 10, 2023:

We have added a new table, SMS_LINK_PARAM_HISTORY.
We have added the following new columns to the CAMPAIGN_HISTORY table:
- message_medium
- updated_by_user_id
We have added the following new columns to the EMAIL_TEMPLATE_HISTORY table:
- cache_data_feed
- data_feed_id
- data_feed_ids
- is_default_locale
- merge_data_feed_context
We have added the following new columns to the EVENT_EXTENSION table:
- browser_token
- catalog_collection_count
- catalog_lookup_count
- city
- clicked_url
- country
- error_code
- expires_at
- from_phone_number
- in_app_body
- is_sms_estimation
- labels
- message_context
- message_status
- mms_send_count
- product_recommendation_count
- proxy_source
- reason
- sms_send_count
- web_push_body
- web_push_click_action
- web_push_icon
- web_push_message
We have added the following new columns to the IN_APP_TEMPLATE_HISTORY table:
- expiration_date_time
- expiration_duration
- in_app_display_settings
- inbox_metadata
- is_default_locale
- locale
- payload
- web_in_app_display_settings
We have added a new column, description, to the LIST table.
We have added the following new columns to the MESSAGE_TYPE table:
- created_at
- frequency_cap
- rate_limit_per_minute
- subscription_policy
- updated_at
We have added the following new columns to the PUSH_TEMPLATE_HISTORY table:
- buttons
- cache_data_feed
- data_feed_ids
- interruption_level
- is_default_locale
- is_silent_push
- merge_data_feed_context
- relevance_score
- rich_media_andriod
- rich_media_ios
- title
- wake
We have added the following new columns to the SMS_TEMPLATE_HISTORY table:
- google_analytics_campaign_name
- is_default_locale
- tracking_domain
We have added a new column, iterable_user_id, to the USER_HISTORY table.
We have deprecated the following columns from the IN_APP_TEMPLATE_HISTORY table:
- buttons
- client_template_id
- content
- content_version
- dismissible
- frequency_cap
- locale_code
- message_backend_content_id
- message_class
- message_format_id
- message_format
- message_id
- message_name
- message_type_id
- messages
- metadata
- name
- state

Iterable connections created on or after August 10, 2023 use a new schema. Find more information about the new schema in our connector overview documentation.

Jira

You can now exclude the ISSUE_BOARD and PROJECT_BOARD tables of the BOARD group from your sync.

On your connector details page, go to the Schema tab and deselect the tables you want to exclude.

Kantata

We have added the following new columns to the WORKWEEK_MEMBERSHIP and WORKWEEK tables:

created_at
updated_at

Magic Folder Connectors

We have updated our sync strategy regarding the Excel files containing formula cells. We now sync the date values of the formula cell results as TIMESTAMP. Previously, we synced them as DOUBLE in our destination.

Salesforce

We no longer sync your formula field translations into the FIVETRAN_FORMULA and FIVETRAN_FORMULA_HISTORY tables. We will roll out this change to all existing connections on October 1, 2023. However, we will continue syncing the formula field translations into the FIVETRAN_FORMULA_MODEL table and you can utilize them by setting the value of full_statement_version to true. For more information about the Salesforce formula utils model, see its documentation available on dbt hub.

Salesforce Commerce Cloud

We have added a new table, PRICE_ADJUSTMENT, to store the data from the PriceAdjustment endpoint. To sync the historical data of the PRICE_ADJUSTMENT table, you must re-sync the parent table, ORDER.

SAP Business ByDesign

We have added the following new tables:

EQUIPMENT
LABOUR
RETURN_TO_SUPPLIER
VEHICLE

To configure your webhooks to capture deletes for the LABOUR and VEHICLE tables, see our setup guide.

Shopify

We have added four new tables:

CUSTOMER_VISIT
FULFILLMENT_ORDER
FULFILLMENT_ORDER_FULFILLMENT_HOLD
FULFILLMENT_ORDER_LINE_ITEM

We can now sync data from the CUSTOMER VISIT and FULFILLMENT_ORDER endpoints. By default, we exclude these new tables from the sync as syncing them might reduce the sync performance. To sync the historical data of the FULFILLMENT_ORDER table, re-sync the ORDER table.

TikTok Ads

We have added a new table, VIDEO_HISTORY.

This change is applicable for all new connections, and we are gradually rolling out this change to all existing connections.

We have added new IN-APP METRICS, PAGE EVENT METRICS, and ATTRIBUTION METRICS fields to the following reports:

AD_REPORT_DAILY
AD_REPORT_HOURLY
AD_REPORT_LIFETIME
ADGROUP_REPORT_DAILY
ADGROUP_REPORT_HOURLY
ADGROUP_REPORT_LIFETIME
CAMPAIGN_REPORT_DAILY
CAMPAIGN_REPORT_HOURLY
CAMPAIGN_REPORT_LIFETIME

For more information about the fields, see our prebuilt reports documentation.

We are gradually rolling out these changes to all existing connections. If you want to sync the historical data for these fields, contact our support team.

Zendesk Support

We have added the following new columns to the TICKET table:

allow_attachments
from_messaging_channel
raw_subject

We have added the following new columns to the TICKET_CUSTOM_FIELD table:

agent_description
relationship_target_type
sub_type_id
tag

We have added two new columns, role_type and shared_phone_number, to the USER table.

We have added two new columns, metadata and plain_body, to the TICKET_COMMENT table.

We have added a new child table, TICKET_COMMENT_ATTACHMENT, to the TICKET_COMMENT table. This table stores the attachments in the ticket comments.

We have changed the composite primary key of the TICKET_SLA_POLICY table to ensure data integrity. The new composite key is a combination of the following columns:

policy_applied_at
sla_policy_id
ticket_id

We have added a new child table, TICKET_EMAIL_CC, to the TICKET table. This table stores the email_cc_ids in the ticket response.

We have deprecated the start_time_utc and end_time_utc columns from the SCHEDULE table and no longer sync data into these columns. To accurately calculate the schedule in the applicable time zone throughout the year, use the DAYLIGHT_TIME and TIME_ZONE tables. Be sure to remove the start_time_utc and end_time_utc columns from your queries. For more information, see our Zendesk Support documentation.

Improvements

Adobe Analytics Data Feed

We now support connecting to your Azure Blob storage container using an SSH tunnel. Learn more about it in our setup guide.

Aircall

You can now configure your Aircall connector using the Fivetran REST API. This feature is available only for the Free, Standard, Enterprise, and Business Critical accounts.

Airtable

OAuth 2.0 authentication is now available for all Airtable connections.

You can now migrate your existing Airtable connectors from API key-based authentication to OAuth 2.0 authentication. For more information, see our migration instructions.

We now re-import all the selected tables of the base associated with the webhooks if Airtable deletes your payloads from its servers. These re-imports count towards paid MAR.

Amazon DocumentDB

We have added support for Packed mode for Amazon DocumentDB Connectors to enable you to deliver your data in a different form.

All existing Amazon DocumentDB connections will continue to deliver data using the Unpacked mode. However, for new connections, you can select either Packed (recommended) or Unpacked mode for Fivetran to deliver you data. For more information, see our Pack modes document.

AppsFlyer

We can now sync Cohort analytics aggregate reports from Data Locker into the COHORT_EVENT table.

Azure Functions

You can now Add secrets as key-pair values while configuring the Azure Functions connector. Previously, you had to enter your secrets in JSON format. We will continue to support secret(s) in JSON format for Azure Functions connections created before August 9, 2023. For more information, see our Azure Functions setup guide.

Chargebee Product Catalog 1.0

You can now configure your Chargebee Product Catalog 1.0 connector using the Fivetran REST API. This feature is available only for Free, Standard, Enterprise, and Business Critical accounts.

Chargebee Product Catalog 2.0

You can now configure your Chargebee Product Catalog 2.0 connector using the Fivetran REST API. This feature is available only for Free, Standard, Enterprise, and Business Critical accounts.

commercetools

commercetools is a cloud-based commerce solution for global businesses. Read our commercetools connector documentation.

Drift

You can now configure your Drift connector using the Fivetran REST API. This feature is available only for Free, Standard, Enterprise, and Business Critical accounts.

File Connectors

We can now sync packed JSON files. We have added a new drop-down menu, JSON Delivery Mode, to the connector setup form. The drop-down menu provides you the option to choose how Fivetran should handle your JSON data. For more information, see our documentation.

We now support custom line separators for CSV files. You can specify a custom line separator in the Line Separator field of the connector setup form. For more information, see our documentation.

We now support multi-character delimiters for CSV files. You can specify a multi-character delimiter in the Delimiter field of the connector setup form. For more information, see our documentation.

We now support syncing PGP (Pretty Good Privacy) encrypted files. We have added a new advanced configuration, PGP Encryption Options, to the connector setup form. For more information, see our documentation.

We now support syncing XML files to your destination. We have added a new option, xml, to the File Type drop-down menu of the connector setup form. We load your XML data into the _data column without flattening it. For more information, see our documentation.

Fivetran Platform Connector

We have renamed our Fivetran Log Connector to Fivetran Platform Connector. This name change applies to the Fivetran dashboard and our documentation.

Front

We have added a new toggle, Sync Private Resources, to the connector setup form. You can now opt to sync private resources using API tokens. For more information, see our setup instructions.

GitHub

We have added the ability to include several personal access tokens in the setup form in order to avoid exceeding GitHub's request rate limit. This feature is available to all connectors set up after August 26, 2023. Learn more in our setup guide.

GoCardless

You can now configure your GoCardless connector using the Fivetran REST API. This feature is available only for Free, Standard, Enterprise, and Business Critical accounts.

Google Ad Manager

We have added a new configuration option, Custom fields, to the connector setup form. You can now select and sync up to 15 custom fields in a report. For more information, see our setup instructions.

Google Analytics 4 Export

You can now switch the Sync Mode for your Google Analytics 4 Export connector in your Fivetran dashboard. For more information, see our Google Analytics 4 Export documentation.

Google Cloud Functions

You can now Add secrets as key-pair values while configuring the Google Cloud Functions connector. Previously, you had to enter your secrets in JSON format. We will continue to support secret(s) in JSON format for Google Cloud Functions connections created before August 9, 2023. For more information, see our Google Cloud Functions setup guide.

Ironclad

You can now configure your Ironclad connector using the Fivetran REST API. This feature is available only for Free, Standard, Enterprise, and Business Critical accounts.

Iterable

We now support the following types of Iterable projects for connections created on or after August 10, 2023:

Kantata

We now incrementally sync the following tables:

ACCOUNT_MEMBERSHIP
ESTIMATE
ESTIMATE_SCENARIO
RATE_CARD_HISTORY
RATE_CARD_ROLE_HISTORY
RATE_CARD_SET_HISTORY
RATE_CARD_VERSION_HISTORY
ROLE
TIMESHEET_SUBMISSION
USER
WORKWEEK
WORKWEEK_MEMBERSHIP

Lightspeed Retail

The Lightspeed Retail connector now supports table blocking for all Lightspeed Retail tables. You can now choose which tables to sync and which to block from syncing to your destination. On your Connector Details page, go to the Schema tab and select or deselect the tables.

If you want to sync a child table, you must include the parent table in the sync.

Open Exchange Rates

You can now select the base currency for your connector. Previously, we used the United States Dollar as the default base currency. We have added a new drop-down menu, Base Currency, to the connector setup form.

Optimizely

The Optimizely connector now supports priority-first sync. Priority-first syncs fetch your most recent data first so that it's quickly ready for you to use. Optimizely's priority-first syncs fetch the most recent 30 days' worth of data from the DECISION and CONVERSION tables and their child tables.

To learn more, see our priority-first sync documentation.

Oracle Fusion Cloud Applications

Our Oracle Fusion Cloud Applications connectors are now generally available:

PayPal

We will now sync only the balance-affecting records in the TRANSACTION table. To align the existing data in your destination with this change, we recommend that you re-sync the TRANSACTION table or contact Fivetran Support to re-sync it for you.

PostgreSQL

We can now sync tables with TEXT primary keys using Fivetran Teleport Sync. For more information, see our PostgreSQL documentation.

We now support the XML data type in PostgreSQL destinations.

In existing tables, the STRING data types for XML will remain unaffected. We will create new tables and columns using the XML data type when the source supports it.

Qualtrics

We have released pre-built, dbt Core*-compatible data models for Qualtrics. Find the models in Fivetran's dbt hub or data models documentation. Learn more about our dbt Core integration in our Transformations for dbt Core documentation.

* dbt Core is a trademark of dbt Labs, Inc. All rights therein are reserved to dbt Labs, Inc. Fivetran Transformations is not a product or service of or endorsed by dbt Labs, Inc.

Redshift

We now support Redshift Serverless as a destination.

Salesforce

We now filter and exclude deleted child records in our Roll-up Summary field calculations.

SAP

We have released pre-built, dbt Core*-compatible data models for SAP Business ByDesign and SAP Concur. Find the models in Fivetran's dbt hub or data models documentation. Learn more about our dbt Core integration in our Transformations for dbt Core documentation.

* dbt Core is a trademark of dbt Labs, Inc. All rights therein are reserved to dbt Labs, Inc. Fivetran Transformations is not a product or service of or endorsed by dbt Labs, Inc.

Sonarqube

You can now configure your Sonarqube connector using the Fivetran REST API. This feature is available only for Free, Standard, Enterprise, and Business Critical accounts.

Subscript

You can now configure your Subscript connector using the Fivetran REST API. This feature is available only for Free, Standard, Enterprise, and Business Critical accounts.

Survicate

You can now configure your Survicate connector using the Fivetran REST API. This feature is available only for the Free, Standard, Enterprise, and Business Critical accounts.

Twilio

We have released pre-built, dbt Core*-compatible data models for Twilio. Find the models in Fivetran's dbt hub or data models documentation. Learn more about our dbt Core integration in our Transformations for dbt Core documentation.

* dbt Core is a trademark of dbt Labs, Inc. All rights therein are reserved to dbt Labs, Inc. Fivetran Transformations is not a product or service of or endorsed by dbt Labs, Inc.

REST API Improvements

Amazon S3

We now validate that the external_id value that you specify when creating the Amazon S3 connector using the REST API is the same as your Fivetran account's group_id. Make sure to choose any of the group_id from your Fivetran account as the external_id parameter value. To find the group_id, use the List All Groups endpoint.

Changes in REST API fields

For the Transformations for dbt Core Management API, we added a new field, environment_vars. You can now manage the list of environment variables defined as key-value pairs.
The enabled field in the Log Service Management API's Create a Log Service method now has the true value by default.
We added a new field, connector_class, in the Retrieve connector types and Retrieve connector type details methods.

This field contains the connector category (standard or lite). Learn more about connector categories in our Differences between Standard and Lite connectors documentation.

dbt Transformations Management API in Beta

Our dbt Transformations Management API is now Beta. You can now leverage the following features:

Fivetran provider for Terraform

Fivetran provider for Terraform is now generally available.

Iterable

You can now specify the events and custom events that you want to sync when you configure the Iterable connector using our REST API.

Log Service Management API

Our Log Service Management API resource is now in beta. You can now leverage the following features:

Postman Collection Update

We have added the Log Service Management API and Transformations for dbt Core Management API to our Postman collection.

Salesforce

We have changed the Salesfore connector's API response to the Retrieve Connection Details API request to return the connecting_user_email, organization_id, and username fields in the config section of the response instead of the source_sync_details section.

Webhook Management API in GA

Our Webhook Management API is now generally available.