Release Notes

April 2026

We've implemented a new mechanism to fetch source schema quicker when creating a new connection. Now, instead of deriving the schema from source data, we use fixed schema models. This allows you to see the schema blocking and hashing screen almost immediately after creating a new connection.

As a result of this improvement, you may see empty tables and columns in the Schema tab of existing connections that have not yet synced to your destination.

We've added the following new columns to the CONVERSATION table.

url
attributes
timer_date_inactive
timer_date_closed

We've added the following new columns to the CONVERSATION_MESSAGE table.

url
attributes
delivery_total
delivery_sent
delivery_delivered
delivery_read
delivery_failed
delivery_undelivered

We've added new columns, url and attributes, to the CONVERSATION_USER table.

We've added a new table, CONVERSATION_MESSAGE_MEDIA. The table contains one row per media attachment on a conversation message, including content type, filename, and size.

After optimizing schema fetch for the connectors below, these connections no longer use the pre-initial-sync schema capture flow described in schema_status.

Affected connectors

REST API request changes (breaking)

For the connectors listed above, the schema_status request field is no longer supported in:

Update a Connection

If your automation still sends schema_status for these connectors, requests may fail.

REST API response changes

For the connectors listed above, schema_status is no longer returned for flows that previously exposed it, including:

If your downstream transformations or orchestration rely on this field, update them to handle its absence.

Dashboard flow change

In the Fivetran dashboard, these connectors no longer show the schema prefetch and review step before initial sync. After connection creation, you proceed directly to the initial sync flow.

February 2026

We have added the following new TaskRouter API tables:

WORKSPACE contains workspace data from Twilio TaskRouter, which are organizational containers for TaskRouter resources.
WORKER contains worker data representing TaskRouter agents who handle tasks, including their availability status and activity information.
TASK contains task data representing work items that need to be assigned to workers within TaskRouter workflows.
TASK_QUEUE contains task queue data that organize and prioritize tasks before they are assigned to workers.
TASK_RESERVATION contains reservation data that links tasks to workers, tracking the status of task assignments and worker acceptance.
ACTIVITY contains activity data representing worker states (e.g., Available, Offline, Break) within TaskRouter.
EVENT contains event data that logs all activities and state changes within TaskRouter workspaces.
TASK_CHANNEL contains task channel data that categorize tasks by communication type (e.g., voice, SMS, chat).
WORKFLOW contains workflow data that defines the routing logic for assigning tasks to workers based on business rules.

We are gradually rolling out these changes to all existing connections.

December 2025

You can now select and deselect the core tables to be synced on the Schema tab of the connection details page in your Fivetran dashboard.

We now support syncing a child table without syncing its parent table. To support this enhancement, we have made the following changes:

We now automatically sync the child tables that were already selected for sync, but were previously excluded because their parent tables were not selected.
We now allow you to select child tables without selecting their parent tables on the Schema tab of the connection details page in your Fivetran dashboard.

October 2025

We unified each connector’s pre-built dbt Core–compatible data models into a single model. It standardizes and documents the Fivetran schemas created in your destination and outputs analytics-ready tables. Previously, most connectors used distinct source and transform models.

September 2025

We've added a new table, RECORDING. The table contains call recording data from the Twilio Voice API.

June 2025

We have added a new column, attributes, to the PARTICIPANT table.

February 2024

We have added a new table, VERIFICATION_SERVICE.

October 2023

We have added a new table, VERIFICATION_ATTEMPT.

August 2023

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.

May 2023

You can now exclude the following tables from your syncs:

ADDRESS
CALL
COACHED_CALL
CONFERENCE
CONFERENCE_PARTICIPANT
CONFERENCE_PARTICIPANT_EXTENDED
EXECUTION
EXECUTION_STEP
FLOW_HISTORY
INCOMING_PHONE_NUMBER
OUTGOING_CALLER_ID
TRUNK
USAGE_RECORD

March 2023

We have added a new table, MESSAGING_SERVICE.

We have added a new column, voice_url, to the INCOMING_PHONE_NUMBER table.

We have added a new column, messaging_service_sid, to the MESSAGE table.

We are gradually rolling out these changes to all existing connections.

March 2022

We are now testing an alternative approach using Twilio's Participant Summary resource to fetch data for conference participants. We have added two new tables, CONFERENCE_PARTICIPANT_EXTENDED and COACHED_CALL. If you'd like to enable this feature on your connector, contact our support team.

February 2022

The initial sync now extracts all available records to the CONVERSATION and related tables. Subsequent syncs only extract records that were updated up to seven days before the last sync. Previously, we extracted every record with each sync, potentially causing lengthy syncs.

November 2021

We have added the following new tables:

SERVICE stores service information
CONVERSATION stores conversation information
CONVERSATION_MESSAGE stores conversation message information
CONVERSATION_USER stores user information
PARTICIPANT stores participant information
ROLE stores role information
ROLE_PERMISSION stores role permission information
RECEIPT stores delivery receipt information

To sync these tables, select them in the Schema tab on the connector details page in your Fivetran dashboard.

January 2021

You can now exclude the MESSAGE table from your syncs. On your Connector Details page, go to the Schema tab and deselect the table. By default, we include the table in the sync.

November 2020

Our Twilio connector is now generally available.

Read our Twilio connector documentation.

September 2020

You can now select the accounts you want to sync in your Twilio connector. See our Twilio setup guide for details.

August 2020

We have released a new authentication mechanism using API Keys for our Twilio connector. Read Twilio's API Keys documentation for more information.

We are deprecating the old authentication mechanism using Account SID and AuthToken. Existing users will be notified to migrate and use the new authentication mechanism. Be sure to transition to the new authentication mechanism by September 1, 2020.

We have also updated the connector's REST API configuration parameters to use the new authentication mechanism. See our Twilio Connector Config documentation for more information.

We have updated the REST API configuration parameters to support new authentication mechanisms for the following connectors:

Adobe Analytics now supports JSON Web Token (JWT) Authentication. See our Adobe Analytics Connection Config documentation for more information.
Twilio now supports authentication using API Keys. See our Twilio Connector Config documentation for more information.

May 2020

Twilio is a cloud communications platform that allows users to programmatically make and receive phone calls, send and receive text messages.

Read our Twilio connector documentation.