Subject: Feature Request: Add channel Column to conversation_time Table in Fivetran Connector

Description:

Hi Fivetran Team,

I would like to request a new feature for the Fivetran connector. Specifically, we need to add the channel column to the conversation_time table.

This is the ticket were discussion on this topic was handled : #224868 , please check for further details, this ticket contains a deep explanation on the case and we're advised by Sara (Lead Support Engineer) to raise a new feature request .

Really appreciate your help on this since this is critical for our operations.

Background:

Currently, the channel column is available in a nested form in the API response but is not available in our Fivetran connector. This limitation prevents us from differentiating between values for the same conversation_time_id. The conversation_channel_history table does not have a conversation_time_id column to join, only the conversation_id, which is different.

Proposed Solution:

Sync the channel JSON array in the conversations/{conversation_id}/times endpoint as a CONVERSATION_TIME_CHANNEL table. This table can have both conversation_id and conversation_time_id as primary keys.

Business Impact:

Adding this feature will significantly improve our data integration process by allowing us to accurately track and analyze conversation times across different channels. This enhancement will enable better data-driven decisions and improve our overall operational efficiency.

Thank you for considering this request. Please let me know if you need any additional information.

Best regards,