Skip to main content
Docs
Feature Requests Onboarding Trust Center Status Page

Community

Connector Improvement: Include more available properties from the twilio conversations API in destination tables

Answered
Conrad Cartmell User

There are a number of attributes returned by the twilio conversations API that are not included in the tables that fivetran extracts from that API:

  • from the conversation endpoint: links, timers, attributes, url
  • from the conversation message endpoint: attributes, url, delivery, links, media
  • from the conversation user endpoint: attributes, url, links

it would be excellent if fivetran could include these as columns in the extracts that it produces from twilio data.

Please sign in to leave a comment.

Comments

2 comments

Date Votes
  • Official comment
    Sandeep Preetam Saila Fivetranner

    Hi Conrad,


    This is a valuable idea. The request to include additional attributes—such as links, timers, attributes, and url from various Twilio Conversations API endpoints—has been added to our feature improvements backlog.


    To better understand your needs, could you share more about your use case or the specific problems you are aiming to solve with these additional fields? This context will help us prioritize and design enhancements that address your requirements.


    We will keep the community updated on this thread with any progress.


    Thanks,
    Sandeep

  • Conrad Cartmell User

    Of course! our product uses attributes to mark conversations and messages as relating to certain flows, events, and entities in our application. If these aren't available in the twilio data, it becomes very difficult or impossible to relate conversations and messages to data from our application in our data warehouse.

    I don't currently have use cases for links, timers, and urls, but I thought I would mention them in my feature request. It might not be difficult to add them if changes are being made to the schemas that they are associated with already.