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.

  • Home
  • Get Help
  • Troubleshooting
  • Failed to create a transcription in OpenAI (GPT-3, DALL·E, Whisper): The app returned "Invalid file format.

Hi, 

I want to create a zap that transcribes slack voice messages to text via OpenAI's Whisper.

I can extract the link to a voice message from the slack message with the fields url_private or url_private_download (both links end with .mp4) but I still receive OpenAI’s feedback: 

Failed to create a transcription in OpenAI (GPT-3, DALL·E, Whisper)
The app returned "Invalid file format. Supported formats: r'm4a', 'mp3', 'webm', 'mp4', 'mpga', 'wav', 'mpeg']".

 

Here is my exact setup: 

  1. Trigger: New Message Posted to Channel in Slack channel

  2. Filter: Only continue if the text contains .mp4

  3. OpenAI: From the slack message, I take the input field url_private (ending with .mp4) and ask to transcribe it

  4. → I receive the above error

 

Anyone else who had this problem and found a solution?

Hi @Tim_wienboeker 

Good question.

Please post detailed screenshots with how your Zap steps are configured along with the encountered error in order for us to have full context, thanks.

@Tim_wienboeker 

This is likely why...https://api.slack.com/types/file#auth

 

Authentication

Authentication is required to retrieve file URLs.

The url_private property points to a URL to the file contents. Editable-mode files will also have a url_private_download parameter, which includes headers to force a browser download. Both url_private and url_private_download require an authorization header of the form:

 
Authorization: Bearer A_VALID_TOKEN

In this case, A_VALID_TOKEN is representative of a real OAuth token, bearing at least the files:read scope. Learn more about OAuth Scopes.

Fields providing URLs that require this form of authentication include:

  • url_private
  • url_private_download
  • thumb_64
  • thumb_80
  • thumb_160
  • thumb_360
  • thumb_480
  • thumb_720
  • thumb_960
  • thumb_1024

Please note that the url and url_download parameters have been deprecated. Please use url_private and url_private_download instead.

 

@Tim_wienboeker 

You can try using this Slack action:

 

@Tim_wienboeker

Actually, try using a “File” data point from the Slack step.

Search for “exists but not shown”.

This is a temp file that is available for you.

NOTE: There may be more than 1 file on a Slack message, in that case you would have to use the Looping app to iterate thru each.

 

Thanks a lot @Troy Tessalone - it worked!

Reply


Terms & Conditions