Skip to main content

Get Support
Have a question? Let's get you an answer!

How Do I...? Troubleshooting Code & Webhooks Developer Zone

Other Help Resources
Wait, there's more! Check out these Community sourced spaces for additional resources.

Zapier Help Center Hire an Expert

Learning Resources
All of our best learning resources can be found here.

Featured Articles Show & Tell Zapier's products AI Hub Zapier Tools Hub

Share your knowledge
Give back to the Community by sharing your automation wins and helping to answer questions.

Share your success See unanswered questions User Groups

Other Learning Resources
Some of our favorite additional ways to upskill your Zapier knowledge.

Zapier Learn Zapier Blog Zapier Webinars

Product Updates
Check out what is new and upcoming with Zapier with our regular product updates.

Product Updates

Early Access Program
Want to join Early Access? Learn more here.

Please help. Probably a newbie question.

 

I want to create a simple Zap that monitors a Google Drive directory for audio files, submits the files to Temi for transcription, and then writes the transcribed output to a notion.so page.

 

Temi only has one action event available: Submit Transcription job. This runs successfully. However, the downstream Notion “Add Content to Page” action only has four fields available from the Temi step:

  • ID
  • Status
  • Created On
  • Reference Name

 

Can someone please help me figure out how to access the transcribed content and use that in a downstream step?

I may have figured it out. Looks like I need ANOTHER Zap. In that one the trigger event will be the Temi “New Transcript” event, which is available for a new trigger Step in the new Zap

I guess the next questions are:
1. What should I put in the “Reference Name” field? (I’ve tried a few things and nothing worked - job fails Temi step because a valid audio file is not being sent to that service)
2. Where is the documentation for these functions?

 

 

Actually that ReferenceName probably doesn’t matter. I’ve investigated the failures from the Temi side. Clearly, the wrong information to download the file is being provided, even though I was quite sure that the input for “Media Url” is the Google Drive “download URL”.  

Temi job info:
 

{"id":"sd900122348","status":"failed",
"failure":"download_failure",
"failure_detail":"Failed to download source file",
"created_on":"2024-09-30T20:21:10.643Z",
"name":"www.googleapis"}

 

Hi there @grachtdog,

Before we dig deeper into this, have you tried publishing the Zap and triggering the Zap to see if it’ll run into the same error?

I'll be keeping an eye out for your response!

Hi @ken.a Thanks for responding. Yes, I have published each iteration so I could test it.  I’ve verified that Temi works when I just submit a file through the Temi web interface, so the problem must be with my Zapier set up.

I’ve tried setting the ‘media URL’ key for the ‘Send Transcription to Temi’ step to either ‘download URL’ or ‘Web Content Link’. Each is an available output from the previous “Google Drive - New File in Folder” step. They both fail. Here is a screenshot of the Temi jobs dashboard, and the associated Zapier configurations.

This seems like it should be so easy, but I spent much of yesterday banging my head against the wall with this. Hope someone can help me figure it out

 

 

Thanks for the additional information @grachtdog! Have you tried using the file object instead? The file object data from Google Drive should look like this: 8591320459a345a59dd755aaa5426a89.png
(view larger)

If the file object did not work, please try using the “Alternate Link” instead.

Kindly give it a try and let me know how it goes? I'll keep an eye out for your response!

I’ll be darned. Using the “File” object worked perfectly. It seems so logical now that you’ve told me. It was actually the AI Copilot within Zapier that got me off on the wrong foot by suggesting to use ‘download Url’. Oh well, that is still a work in progress. 

Now, my Zap is working. Thank you @ken.a 

Terms & Conditions