integrations.google_drive
Google Drive (integrations.google_drive)
Move files between your workflows and Drive: upload an item's $binary
file, download a file into $binary, or list a folder. Folder and file
pickers are live; free-text ids work everywhere.
Operations
| Operation | What it does |
|---|---|
upload | Uploads the item's binary field (default data) — one file per item. Optional file_name override and new_folder_name (created once, all files go inside). |
download | Fetches file_id per item — metadata in the json, bytes in $binary.data. |
list | Emits one item per file in folder_id (blank = everything not trashed). |
Credential: oauth2_google (Drive scope).
Quirks & tips
- Google-native files (Docs, Sheets, Slides) can't be downloaded — they have no binary content, and Drive answers 403 "Only files with binary content can be downloaded". Export conversion isn't supported; keep native files in Sheets-node territory.
listruns once (params resolved at the first item), not per item — it's a folder listing, not a per-item search.folder_idis sanitized to Drive's id alphabet before it enters the search query — an expression feeding it something quote-y can't rewrite the query.- The file picker for
downloadcascades off the chosen folder; picking no folder lists your most recent files. - Uploaded file metadata (
id,name,mimeType,size) is the item's json output — chain theidstraight into another Drive call.
Related
- Extract From File — parse the downloaded binary into row items.
- Create File / Base64 — produce binaries to upload.
- Gmail Send — attach the same
$binaryfiles to email instead.