[403] Permission Issues when trying to get a share link for a file I just created in my own drive

Hey everyone,

I’m create a file in Google Drive and then trying to get the Share Link. I’m receiving the error [403] The user does not have sufficient permissions for this file when I run the scenario. But if I run the Get a Share Link on it’s own and supply it the same File ID that it failed with it works file. Can anyone clue me in here?

Hi,

Sure- by default, Google assigns the same permission to a file as its parent folder.

So if you are creating a file/folder inside a non-shared folder, it is non-shared by default and you must change this setting to make URL work.

So why is there a link? According to my knowledge, this link is forever assigned to the file. So you can easily manage access to it.

Now. Why does the “Get a Share Link” module works? As you can see, you are setting the role and type. This request to Google endpoint changes the file sharing settings.

So if you want to save operations- try to upload files to previously shared folders. It should help but can not guarantee.

Have a great day,
Michal

1 Like

Thanks @mszymkowiak , appreciate your help!

I don’t think I’m explaining myself properly. I’ve recorded this Loom to demonstrate.

Thanks again.

1 Like

Ok, now I understand. Thank you!

“Get a Share Link” works when you run it alone because you are copy-pasting the input bundle, e.g., the original file ID.

When you copy ID from output bundle (this ID is used by variable)- module isn’t working.

So what’s happening here and why it does not work? Your module creates a file’s shortcut that directs to the file- as a shortcut does.

When you are using your browser interface and copying the shortcut share link, everything works because Google thought about it— the share link directs to the original file.
Looks like Make also thought about this (module does 2 requests) but it doesn’t work as expected.

Please report this case to support because, according to DevTools, the module first does a request to obtain the original file ID but then doesn’t use it and tries to share the shortcut instead.

1st request response contains original file ID
SC_2

Hmmmm, that’s a shame. Nice work for getting to the bottom of it though!

1 Like