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

Community

Connector Improvement: Gong connector missing required attributes but those are available in gong api

Completed
Ravi Vennapu User

Hi Team,

we are looking for calls related attributes transcripts, highlights, call outcomes, call briefings, key points, and next steps which are not available in gong connector as i refer to find those in fivetran ERD https://fivetran.com/docs/connectors/applications/gong#schemainformation.

Here Below we are fetching gong data from api to snowflake, those attributes which are not available in fivetran gong connector.

1) calls_transcript which is available in gong api and it is not available in connector, Expected attributes call_id, transcript. In connector i can see transcript but there is no related attributes. please find below.

2) Scorecards table all attributes available but questions attribute is missed.

3) users table all columns are available but email_aliases, personal_meeting_urls, spoken_languages are not available.

 

Please sign in to leave a comment.

Comments

3 comments

Date Votes
  • Official comment
    Vishal Ray User
    • Edited

    Hi Ravi,

    We have started rolling out this new feature improvement for our Gong Connector.

    We have added "brief" field in the CALLS table, and other data are added in tables below: 

    • CALL_KEYPOINT

    • CALL_HIGHLIGHT

    • CALL_HIGHLIGHT_ITEM

    • CALL_OUTLINE

    • CALL_OUTLINE_ITEM

     

    We have added your connection to have these tables synced.

    We would really appreciate your feedback on this data.

    Thank You,

    Vishal

  • Ayan Putatunda User

    Fivetran Team, 

    Do we have any response on this?

  • Vishal Ray User
    • Edited

    Hi Ravi and Ayan,

     

    I really apologies for the delayed response on this :

    Here's update on your queries :

    1. calls_transcript table - transcript is all the “sentences’ relating to a call_id. This is how gong API is providing this information.
    2. scorecard  table - we have separate table called scorecard_question which stores this data
    3. users table - we have separate tables user_email_aliases , user_meeting_urls and user_spoken_language

    We are already working on adding new data by mid-duly:

    • brief
    • outline
    • highlights
    • callOutcome
    • keyPoints

    I will provide an update here when it is available.