Failed to create a track in Radio.co: The app returned "File is not an mp3 or m4a"
I set up a Zap that is supposed to upload a file to my Radio.co media library whenever a new file is uploaded to a certain Dropbox folder.
Everything works/validates in the trigger part -- and then, when it gets down to the bottom of the action section, it gives me this error:
Failed to create a track in Radio.co
The app returned "File is not an mp3 or m4a".
The thing is -- they totally are mp3 files. I’ve tried several files -- and double/triple checked them. At a point (and, I’ve been at this for a couple of hours) I set the Dropbox folder to automate that any file that can be is changed in to being an mp3 upon upload -- and, still no dice.
Kind of going a bit nuts with this.
Can anyone help -- or does anyone have any ideas?
Page 1 / 1
Hmm @RFM, I certainly understand the frustration with this. I’m glad you stopped through the Community so we can try and work through this together.
My first request is if you can please add some screenshots of your Zap set up from both your trigger and any actions. With this request, we like to remind you to please omit any sensitive or identifying information upon upload (you can totally just strike a line through or blur it out).
It sounds like your Zap is on and published and not in the “test” phase, is that correct? If yes, can you please add some screenshots of the data pulled in from your Zap History? If it is just in the test phase, then any screenshots of the data received from the “test” would be fantastic as well.
Thanks for your response! I managed to figure it out.
In the Action section, the text says “Upload URL: Choose 'Direct Media Link'.” -- but, the screenshot shows that you need to select File: (Exists but not shown).
Once I made it the File: (Exists but not shown), it started working.
Thanks!
That’s awesome - way to troubleshoot this on your own.
Thanks for coming back around to share your solution with us too. Always appreciated.
Happy zapping!
Hi All, need your support, im facing the same issue automating file transfer from Monday.com to Radio.co using Zapier. File is directly uploaded to MOnday.com, file can be downloaded when the URL is opened in browser. I also tried uploading the file to Google Drive first however the issue seems the file cannot be downloaded directly using the link. During testing im getting “The error message "File is not an mp3 or m4a" indicates that the file being uploaded in the "upload_track" step is not recognized as an mp3 or m4a file, which are the expected formats. However, based on the data from the previous step, the file URL (files_1) does indeed point to an mp3 file. This suggests that the issue might be with how the file is being fetched or processed before the upload. To resolve this, ensure that the file URL is correctly passed to the "upload_track" step. Double-check that the upload_url field in the RadioCLIAPI step is correctly mapped to the files_1 output from the MondayCLIAPI step. You can do this by editing the Zap and confirming the field mapping. Additionally, verify that the file at the URL is accessible and not behind any authentication barriers that might prevent it from being fetched by Zapier. If the file is protected, consider using a file-sharing service that provides direct access links or adjust the permissions to allow Zapier to access the file.” REached out to Monday.com support and was referred to contact Zapier
