Skip to main content

Hi,

I have an issue with a very simple Zap. 

 

The trigger finds the file, and I pass the path to the Delete step, but it cannot find it:

 

 

If I try to use the Static file name, I get this:

 

The same Zap works if I use the Personal space in the Team Dropbox.

I am an Admin in Dropbox and tried to set the access to the folder in the team workspace to only me, but it does not work either.

Do you have any suggestions on how to fix the problem with the team workspace? I can upload and move files but not delete them.

Thank you

vittorio

Hi ​@VittorioP 

Help links for using Dropbox in Zaps: https://zapier.com/apps/dropbox/integrations#help

Can you post screenshots of the encountered Zap step error from Dropbox in the TEST tab?

 


Hi ​@Troy Tessalone ,

 

here it goes:

 

thank you!

 


@VittorioP 

Does the file_path value you are testing with still exist in Dropbox?

Make sure to test with an existing file in Dropbox.

Try testing your Zap trigger step again to get fresh example records to use to test Zap step 2.


@Troy Tessalone 

Just did both again, same results

 

 

 

I believe this is related to the permissions on the ‘Team Space’. On the ‘personal space’, the exact same zap works.


@VittorioP 

Do you have the same Space set for Zap step 1 and Zap step 2?


@VittorioP 

If you wanted to try using an API request, here’s how…

Zap action: Dropbox - API Request

https://www.dropbox.com/developers/documentation/http/documentation#file_requests-delete

 

 


@Troy Tessalone 

Both steps have the same space

 

Tried with API, too, and I got the same error:

 

 


@VittorioP 

I believe this is related to the permissions on the ‘Team Space’.

On the ‘personal space’, the exact same zap works.

That may be the case.


Hi there ​@VittorioP👋

It looks like you’re running into a recently reported issue with the Dropbox app where deleting files in a Team folder/space returns a “path_lookup/not_found/...” error. We can’t provide a timeline for when it will be fixed, but I’ve added you to the bug report as an affected user, so you’ll be notified via email as soon as it’s sorted.

In the meantime, in the API Request action can you try setting the Dropbox-API-Path-Root in the header section? Suggesting that I as came across this old discussion on Dropbox’s community where it was mentioned that the Dropbox-API-Path-Root needs to be set in the header to work with files in a team space:

52d8bde911fc18533cab672df9800c2e.png
 

Can you give that a try and let us know how it goes?


Hey there,

A fix has been implemented for this issue. If you’re still seeing errors with your Delete File or Delete Folder actions for Dropbox, please open a ticket from

https://zapier.com/app/get-help