¶ Description
Delete file(s) from google Drive.
¶ Parameters
¶ Parameters tab
Parameters:
- File id to delete
- Client id
- Client secret
- Refresh token
- Debug information level
- Number of retries on connection error
- Error management:
¶ Description tab
See dedicated page for more information.
¶ Configuration tab
See dedicated page for more information.
¶ About
¶ What it does
Permanently deletes one or more Google Drive files using their File ID.
This is a hard delete (not “move to trash”).
¶ Prerequisites
- A Google Cloud OAuth client with Drive API enabled.
- Client ID, Client Secret, and a Refresh Token with scope
https://www.googleapis.com/auth/drive. - The File ID(s) of the item(s) to delete (from the file’s URL or API list).
¶ Minimal pipeline
InlineTable → GDrive Delete → RunToFinishLine
¶ InlineTable (input)
Create a single column named FileID and put one File ID per row.
¶ GDriveDelete (configure)
Open Parameters and set:
-
File id to delete (idFile): bind to the FileID column
(click the “…” picker and chooseInlineTable → FileID). -
Client id:
<YOUR_CLIENT_ID> -
Client secret:
<YOUR_CLIENT_SECRET> -
Refresh token:
<YOUR_REFRESH_TOKEN> -
Debug information level:
nothing/basic/verbose(pickverbosewhile testing). -
Optional: extra parameters for cURL (idOptional): (optional)
Recommended while testing:-L --fail-with-body -
Number of retries on connection error (nRetry):
2–3 -
Error Management:
abort pipeline execution with error(strict) orcontinue with status ERROR(keeps the run going and marks the row)
¶ Run & verify
- Click Run.
- Open Log and look for a green Success! line. With
verbose, you’ll also see the HTTP calls. - If your version of the action writes a status table, check Data for something like
_GDrive_Status = OK(or an error).
Screenshot placeholders:
[C] Pipeline – three nodes
[D] Process Log – Success
¶ Tips & common errors
-
404 Not Found
- Wrong File ID, or the token has no access to that file (e.g., in a shared drive you don’t belong to).
-
403 Forbidden / insufficientFilePermissions
- The account behind the refresh token lacks permission to delete the file.
-
Invalid Credentials
- Client/secret/refresh token mismatch or expired refresh token. Re-authenticate and obtain a new refresh token with offline access.
-
Shared drives
- Ensure the user has permission to delete in that drive. If you still get “file not found,” confirm the File ID really belongs to that drive and your token can see it.
