Hey there @Ibiza Sonica, welcome to the Community!
That’s odd, are the audio files from Radio.co quite large?
You mentioned that the tracks are being added to Spotify, despite that 400 error. So I’m wondering if the issue is that it’s taking longer than expected to upload the file, due to its size. Meaning we get back that 400 response as it’s not been able to complete the upload in that time. Do you think that could be the case here?
Are you able to test this theory out by uploading a smaller file to see if that gets added by the Zap without running into any errors? Looking forward to hearing from you!
Hey Sam!! :)) nice to meet you
Many thanks for your answer,I did what you told me with a smaller file, and the zap gave me this error
The app returned "cURL error 6: Could not resolve host: True (see https://curl.haxx.se/libcurl/c/libcurl-errors.html)".
Do you know why this can happen? I don't know if I'm doing something wrong
Many thanks for your help
Hi @Ibiza Sonica!
Can I double-check that I understand what you’re trying to do? Is your Zap set up as:
- Trigger: Spotify - New Track Added to Playlist
- Action: Radio.co - Upload a Track When a New File Is Added
I can see that the Radio.co action needs the url of a track to upload it. I’m not familiar Radio.cc, do you know if you can add tracks using Spotify urls (ie if you do it manually)? Or does it need to be a link to a file (eg the url of a file in Google Drive/Dropbox)?
I took a look at the Radio.cc help docs about adding media and it mentioned using an FTP server, but I’m not sure if that’s applicable here.
I hope that helps to get you pointed in the right direction, let us know if you have any questions!