Skip to main content

For an internal assistant tool I am trying to retrieve all transcripts we have for specific people who I want to fetch by email address.

 

I understand that get /v2/calls provides me with calls in a certain date range, and I could, in theory, then make a post /v2/calls/extensive to then go through the “parties” and then, based on the responses, go back to post /v2/calls/transcript to retrieve the transcript. But that seems like a lot of uncessary strain on the API. Is there a better way to get all IDs for all calls involving a person by email address?

I checked the search and someone was trying something similar by Account, and that didn’t work. But yeah, maybe someone else has an idea?

No emails are in extensive so you need to call each endpoint. 

I save basic data from /calls, save extensive data from /extensive, then with each downloaded log; add basic data at the beginning (basic) and replace all speaker IDs with their name (extensive).

Hey James - thanks for your suggestion. I saw your convo with Molly a week ago and was worried that this would be the answer.

On a practical POV, may I ask you: do you keep your own little “shadow database” of calls with the data from /calls and /extensive to query when needed, or do you run across the entire Gong API every time you’re looking to identify a transcript?

The second one sounds like more wokr, but at least it’s not firing hundreds of requests for every query.

I keep the .json files from calls and extensive to query for info, and once I had a collection started, I just grab the new ones by date. Another cool thing I did was grab the external domain and sort the calls into folders. You have to use the domain, because the company name isn’t available.

I am trying to set up an automation with Zapier to grab new transcripts, but there is a bug in Gong’s integration preventing me from connecting.

Hi ​@James Stafford - thanks for stepping in here. These are great tips.

 

I’m not aware of a Zapier bug but am happy to look into this with you. If you haven’t already, please submit a ticket here. 
 

​@BridgetFinegan, Zapier support told me that there was a bug and they would reach out to the Gong team. See their response below.

“Hello James,
Diana here from Zapier Support! Stepping in for my colleague. Michelle, while she's away. 
Thanks for sticking with me while I looked into this. This appears to be related to a bug with the app’s Zapier integration where we're getting Internal server error when trying to turn the Zap on.
I’ve confirmed that this matches an existing issue reported by other users, so I’ll let the Gong team know that you’re running into this. Please note that only the Gong team, who own and maintain this integration, can fix the problem.”

Thank you for sharing that ​@James Stafford. I’ve gone ahead and submitted a ticket on your behalf, and added myself as a follower. 

(ref: #192329)

 

 

Reply


Terms & ConditionsCookie settings