FL Google Drive Downloader

Someone shared a Google Drive link with a model, a dataset, or a folder of reference images, and you want it inside your ComfyUI without the download-then-move-then-unzip dance. FL_GoogleDriveDownloader takes a Drive share link, pulls the file down, unzips it if it's a ZIP, and drops the contents into a named folder - all from inside your graph. For anyone building workflows on a rented/remote GPU where dragging files around is a pain, it's a real time-saver.

The mechanism is straightforward: you give it a public share link and a folder name, it fetches, and if what comes down is a ZIP archive it extracts it and cleans up the temp files. What you get back is the path where everything landed, as a string, so a downstream node can go read from there.

The inputs and output

• google_drive_link (STRING) - the Drive share URL. It has to be a link that's actually shareable - "Anyone with the link" access - or the download fails, because the node isn't logging into your account, it's fetching a public URL.
• output_folder_name (default gdrive_download) - the folder it creates and drops the contents into.

Output is a single STRING: the path to the downloaded/extracted result, ready to wire into whatever consumes it.

It's an output node, so it does its work when the graph runs even if you don't wire the path anywhere.

Installing it

Part of ComfyUI_Fill-Nodes. ComfyUI Manager: search Fill-Nodes, install, restart. Or:

cd ComfyUI/custom_nodes
git clone https://github.com/filliptm/ComfyUI_Fill-Nodes

then restart ComfyUI. No model download for the node itself.

The "should I be worried?" thing - and the real gotchas

Worth addressing head-on, because it comes up: some people install Fill-Nodes, restart, and notice a wall of text scroll past during startup mentioning Google Drive, and briefly panic that they've installed something sketchy. It's benign - that's the pack's Google Drive integration announcing itself, not malware. That said, the underlying instinct is a good one to keep: every ComfyUI custom node runs arbitrary Python with your user permissions, there's no sandbox, and a real malware-via-custom-node incident (LLMVISION, 2024) is why the community is jumpy. Fill-Nodes is a widely-used, openly-developed pack, so this node isn't the threat - but "read what a node does before you run it" is always the right posture.

Practical failure modes: the link must be public ("anyone with the link"), or the fetch 403s. Very large files can hit Google's download quota or its virus-scan interstitial for big files, which breaks a naive fetch. And if the archive isn't actually a ZIP, don't expect the auto-extract to do anything - it hands you the file as-is. Get those three right - public link, reasonable size, ZIP if you want auto-unzip - and it just works.