Fetch from Google Drive
Import files from a Google Drive folder
Fetch from Google Drive
Node type: action:google_drive_fetch
Category: Integrations
Description
Import files from a Google Drive folder
Canvas ports
These appear as port handles on the left side of the node.
No input ports.
Sidebar config
These render as form fields in the right-side config panel when the node is selected.
| ID | Label | Details |
|---|---|---|
folderId |
Folder | TEXT |
folderName |
Folder name | TEXT |
fileTypes |
File types | ARRAY |
limit |
Max files | NUMBER |
Outputs
| ID | Label | Type |
|---|---|---|
url |
File URL | IMAGE |
items |
Items | ARRAY |
Connect an account, then pick a folder
Select the node and the config panel walks you through it: connect a Google account, then browse My Drive and click a folder to pick it. Search spans the whole drive; "Open" drills into a folder without selecting it. You come back to the same canvas after connecting.
With no folder picked the node card says so, and a run skips instead of failing.
What comes out
Every matching file is copied to Wireflow's CDN so downstream nodes can read it without a Google token. Items is the full list (url, name, mimeType, size) and is what you wire into an iterator for batch work. File URL is just the first item, for the common single-file case.
Only images, video and audio are imported. Google Docs, HTML, SVG, PDFs and anything else in the folder are skipped (never downloaded) and named in the run's warnings; a folder with nothing importable fails and says which files it passed over. Picking a type in File types does not change this.
Files over 100 MB are not imported. They, and any file whose download or copy fails, are named in the warnings with the reason, so a failed video is never reported as a file-type problem.
Max files caps the batch at 100 and files come back newest first, so a folder that grows past the cap keeps returning the most recent ones.
Scope
The connection is read-only for browsing (drive.readonly) plus write access
limited to files Wireflow itself creates (drive.file). Wireflow cannot
modify or delete files it did not upload.
Auto-generated from the Wireflow node registry.