Hey @joaosander 
Do you get an error message in the WeWeb workflow logs when testing the workflow action? If yes, can you share what it says?
If not, can you tell me if the workflow logs say “Succeeded 
” without any other info about the object you tried to delete or if it says “Succeeded ” with more info about the object that was deleted?
It seems we have a bug that doesn’t properly return the error from Supabase which can be misleading.
In any case, looking at your screenshots, it seems to me like your setup is correct: both the Supabase policy and WeWeb workflow action seem to be setup properly.
Things you might want to check:
- Are you logged in as a user of your app when testing the action in WeWeb?
- Are you logged in as the user who actually uploaded the file to the Supabase storage? (If you’re trying to delete a file that you uploaded via the Supabase UI or via the WeWeb app but when you were authenticated as another user, it will not work)
Hello, this is what it returns
i am authenticated with the user creator and uploader of the item i want to delete.
@Joyce
Mmm ok, so, the “Succeeded” message shows that your request reached the Supabase Storage API successfully but the fact that no object was returned confirms you’re not allowed to delete the file.
Can you check if you also have a SELECT policy on the bucket?
For Supabase Storage delete, you need both SELECT and DELETE policies, not just DELETE
Oh wait…. in this screenshot, you are binding the path to the id of the item, not the name of the file
When binding the file path in WeWeb, you want to bind: `filename.fileformat` or `folder/filename.fileformat`.
In the example below, the `showmanship.png` file is in the `test` folder in the `swag` bucket in Supabase:
In WeWeb, that translates to this:
Does that help?