Troubleshooting Buffer error when using Cloudconvert and Google Drive links
Here is my setup:
I had my setup work with Cloudconvert links for months. Suddenly, nothing works anymore. I keep getting the following error:
Cloudconvert (which was working well for months):
I tried using google drive but I get the following error - all of the googledrive links were enable to be readable by anyone with the link and the link structure follows Buffer’s requirements.
Google Drive:
I have also changed the method to schedule a post an hour later to give time for video to upload. However, I still get the same error.
Are you sure that the file is publicly accessible to anyone with the link? If it’s definitely public and still not being recognised by Buffer, you can try this:
Add a code or formatter step to extract the Google Drive File ID from the URL that you have in the Sheet (it’s just the string after the `id=` part in the URL
Add a Google Drive → Retrieve File or Folder by ID step, and retrieve the file using that ID
That action will return a hydrated file object, and you can pass that into the Buffer step instead of a URL, which should allow you to bypass any permissions restrictions on the file in Google Drive:
Hope this helps!
@DennisWF, thank you so much for providing support on this!
I tried your proposed solution and got an error:
Here is the setup that yielded the error above:
I am not sure why that google drive link did not work. Here is the download link:
Hey @apextherapy can you show what you’re passing into Step 2 in editor mode, and also the output if you do a test run on that step?
The Retrieve File or Folder ID action needs just the ID as the input, not the entire URL. In the case of your example URL, the ID part would be: 1urwhNAsMO6l7IF6Es4TBwoI--RrEQtA9&
In terms of Cloudconvert, I’m not sure what you’re doing with that since I don’t see it anywhere in your Zap. Could you share a little more context on what Cloudconvert is doing, and how it fits in here?
@DennisWF, I only inputed the file ID. That step worked and passed the test without any issues. I was able to use the Hydrate file output you see in the last screenshot, which still failed to upload.
Because googledrive did not work, I passed the files through cloudconvert using make.com. The link from cloudconvert was then uploaded to Buffer via Zapier. This process worked for the past couple of months with no issues till suddenly, I started getting the error about PreSigned URL.
@apextherapy this is a strange one - I have to admit I’m not sure what’s going on. Buffer shouldn’t have any permissions issues with receiving the hydrated file object, but here are a few other things you could try:
Buffer recently updated their Zapier integration, and you’re using an older version (2.2.4). You could try replacing that with the new version and see if that helps any
Sometimes there is a lag while Zapier is still hydrating the file, particularly with larger ones. Adding a Delay Step of a minute or so between the Retrieve File ID step and the Add to Queue step might help if that’s the issue - maybe this is it, actually, since it’s a video file and therefor presumably large.
@DennisWF
You were right!! It was about the Buffer version! You have saved me from the head banging I have been doing for the past few days and needing to go back and forth with Buffer (they couldn’t figure it out). Thank you so much!!
Happy to help - glad we finally figured it out!
Thank you @DennisWF for guiding our member to the right path.
