---
title: "Save to Google Drive"
description: "Upload workflow output to Google Drive"
updated: 2026-09-10
---

# Save to Google Drive

**Node type:** `action:google_drive_save`  
**Category:** `Integrations`

## Description

Upload workflow output to Google Drive

## Canvas ports

These appear as port handles on the left side of the node.

| ID        | Label        | Details              |
| --------- | ------------ | -------------------- |
| `fileUrl` | **File URL** | `IMAGE` _(required)_ |

## 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`  |
| `fileName`   | **File name**   | `TEXT`  |

## Outputs

| ID    | Label         | Type   |
| ----- | ------------- | ------ |
| `url` | **Drive URL** | `TEXT` |

## Wire the file, pick the folder

**File URL** is a port, not a setting: wire the node whose output you want
uploaded. Running the node with that port unwired refuses with "Connect
required input: File URL" rather than uploading nothing quietly.

The target folder comes from the config panel, same picker as the fetch node.
Leave **File name** blank and the name is generated from the file type.

## Skips instead of failing a whole run

Inside a full workflow run, a missing file URL or folder makes this node skip
with the reason on the card, and the rest of the run continues. That is
deliberate: one unwired action node at the end of a long workflow should not
mark a run FAILED after every generation already succeeded.

## What comes out

**Drive URL** is the shareable webViewLink for the uploaded file, and the node
card links straight to it after a run.

---

_Auto-generated from the Wireflow node registry._

---

Documentation index: fetch https://www.wireflow.ai/llms.txt for the full list of Wireflow docs.