Symptoms
When using either the Google Drive Upload File or Move File action in your Zaps, you see the error message "Nothing could be found". You may see this error when setting up a Zap or in the details of a Zap run in your Zap history.
Causes
This happens:
- When the mapped field from the previous step is blank and is required to upload or move a file in Google Drive.
- Your file URL is not publicly accessible or downloadable.
- The mapped field does not contain the file ID that Google Drive expects.
How to fix it
To fix this issue:
Upload File
- If you have mapped a field containing a file URL in the File field, test if the file's URL is accessible or downloadable:
- Open an incognito browser and copy and paste the URL into the address bar.
- Press Enter on your keyboard.
- One of the following will happen:
- The file will display in the browser window if it’s a viewable format.
- The browser will download the file to your computer.
- If the file cannot be accessed, you may see an error message. This means Zapier cannot access the file. Learn more about sending files in Zaps.
- Ensure the data from the previous step is consistently sent to the Google Drive step, or replace the current mapped field with one that consistently provides a value.
- If you cannot change the current mapped field, you can add conditional logic using a filter or branching logic with paths to your Zap. This will allow you to define what the Zap should do if the File field receives no data from the previous step.
Move File
- Check the File field either has a file selected or contains a mapped field with the file ID.
- If you are using the Find a File action, before your Move File action:
- Go to your Find a File action step.
- Select No in the Should this step be considered a “success” when nothing is found” dropdown menu. This will halt the Zap run, and prevent any subsequent steps from continuing. In your Zap run, you’ll see the message “Halted Exception: Nothing could be found for the search.”