I have not used the interface file browse to handle a .zip file. But I have created a staging location (one that the gallery has access to) as sort of a "drop box" for users to place the .zip file into. Then when they initiate the workflow, it searches that location, moves the .zip from there (so that no human intervention can jeopardize the running process) into a new staging or temp folder, then unzips it from that secure location and processes the data.
Since we know the directory tool + dynamic import, for example, can reach into .zip files; this is how we've solved for this type of behavior.
You could also just have your python process handle the file from there. But in essence, using a "dropbox" location is something worth considering.
Hope that sparks some ideas, -Jay
