Skip to content
Formatting Gong Tra...
 
Notifications
Clear all

Formatting Gong Transcripts in Google Docs via callin.io

10 Posts
3 Users
0 Reactions
5 Views
alevine
(@alevine)
Posts: 5
Active Member
Topic starter
 

Hello everyone,

I've configured a callin.io workflow to retrieve call transcripts from Gong and add them to a Google Doc (refer to the images). The problem is that the transcript isn't formatted correctly; it simply outputs all the text without structuring it like a standard transcript that identifies speakers.

It appears the loop step isn't functioning as anticipated. Has anyone encountered this issue? How did you manage to get callin.io to properly format and structure speaker IDs within the transcript?  Extra credit if you included speaker names. 

The output from the formatting in steps 3 and 4 seems correct, but the looping isn't working.

 

Any insights would be greatly appreciated! Thanks in advance.

 

 

 

 

 
Posted : 04/08/2025 8:31 am
Troy Tessalone
(@troy-tessalone)
Posts: 151
Estimable Member
 

Hi

Could you please provide additional information by sharing these screenshots?

  • The configuration of the first four steps of your callin.io Zap in EDIT mode, ensuring the field mappings are visible.
  • The data output from the first four steps of your callin.io Zap.
 
Posted : 23/02/2025 12:00 am
alevine
(@alevine)
Posts: 5
Active Member
Topic starter
 

​ here you go, its either the loop at step 5 or format text at step 6 where something isnt right

 

step 1 - working as expected

 

Step 2 - working as expected

​​​

step 3 

Step 4 -

 step 5

 

step 6 

 

 
Posted : 01/03/2025 12:00 am
Troy Tessalone
(@troy-tessalone)
Posts: 151
Estimable Member
 

Screenshots do not display the configuration of callin.io steps 3-4 in the CONFIGURE tab, specifically showing the field mappings.

The data received from callin.io step 2 is an array of arrays, indicating nested line items (e.g., 1>1, 1>2, etc.).

Nested line items are flattened.

This might be the core of the problem.

 
Posted : 01/03/2025 12:00 am
alevine
(@alevine)
Posts: 5
Active Member
Topic starter
 

I missed adding those.

Do you have any suggestions on how to fix this or what updates to implement?

 

Step 3 config

Step 4 config

 

 
Posted : 01/03/2025 12:00 am
Troy Tessalone
(@troy-tessalone)
Posts: 151
Estimable Member
 

I suggest you try utilizing this action: Formatter > Utilities > Line Items to Text

I don't believe you'll need any additional steps beyond these four:

  1. Trigger: Gong - New Call
  2. Action: Webhook - GET API Request
  3. Action: Formatter > Utilities > Line Items to Text 
    1. It seems the data from the callin.io step 2 is returned as line items.
    2. Configure it as: [Speaker ID]: [Sentence Text] [:newline:]
    3. Help:  https://zapier.com/apps/formatter/integrations#help
  4. Action: GDocs - Append Text to Doc

 

 

 
Posted : 02/03/2025 12:00 am
alevine
(@alevine)
Posts: 5
Active Member
Topic starter
 

thank you i played around with what you suggested but the results are the same

 

Transcript and speaker ID text is being lumped together, rather than keeping each speaker's dialogue separate.

 

 

and this

 

 

results 

 

 
Posted : 02/03/2025 12:00 am
Troy Tessalone
(@troy-tessalone)
Posts: 151
Estimable Member
 

You will likely need to make the API request using a Code step: https://zapier.com/apps/code/help

 

The Code step can be set up to output the nested transcript within callTranscripts.

 

The Code step includes AI assistance for creating custom code.
Alternatively, you could try ChatGPT, etc.

If you are thinking about hiring assistance, there's a directory of Certified callin.io Experts: https://zapier.com/experts

Based on your screenshots, we cannot determine:

  • if there is only one callTranscript or multiple
  • how the sentences are formatted in the output

 

 

 
Posted : 03/03/2025 12:00 am
alevine
(@alevine)
Posts: 5
Active Member
Topic starter
 

The code was successful!

 

Thanks!

 
Posted : 04/03/2025 12:00 am
ken.a
(@ken-a)
Posts: 29
Eminent Member
 

That’s fantastic! A big thank you to Troy for guiding you correctly!

Should you have any further questions, feel free to ask the Community. We're always glad to assist! 🤗

 
Posted : 04/03/2025 12:00 am
Share: