DropBox API for creating a shared link - returns folder not file

Help
1

I am just starting my PipeDream journey, so apologies in advance if this is a silly mistake.

I have successfully created a Source which is looking for files created in a “/Instagram” folder in DropBox. The events are appearing correctly with the appropriate file names. I have a workflow that listens for these events and then calls the “create_update_share_link” and passes to it the file name using {{steps.trigger.event.path_display}}. However when the “create_update_share_link” runs, it returns a shared link to the “/Instagram” folder and not the file.

image
image2209×1206 188 KB

Hopefully you can see from the above that although the workflow says that it has created a link to the file, it is in fact to the folder. The file URL looks different and has the file name included in the URL name.

Any ideas what I am doing wrong?

Thanks

Robert

2

Hi @robertjohnhorton

I don’t believe you are mistaken at all, from the Dropbox API docs it sounds like there are several different types of responses from that create_update_share_link API endpoint.

It’s possible that our DropBox component is only returning the folder data response and not the specific file response.

As a workaround, perhaps you can use the search_files_folders action to find the file again after uploading?

I also encourage you to make a bug request on our Github issue tracker, this may just be an issue with the open source component.

3

@pierce Thanks for the suggestion, I will give the search_files_folders a try and will raise a bug request as well. I do think that the function should return a file shared link if a file is passed to it.