Google Drive

Google Drive operations — list, search, upload, download, and manage files.

The node authenticates through a Google connection. No API key or service account setup is needed — connect a Google account once and pick it in the node's settings.

When to Use

Use Google Drive when:

  • You want to read or write files in Drive from a workflow (generated reports, exports, attachments)
  • You need to search Drive for files matching a query and pass them downstream
  • You want to give an AI Agent tool access to your Drive

Connection

Google Account — required. Pick a Google connection from the Connections page. Click Manage to add one; the picker reopens when a connection exists.

Inputs

HandleTypeDescription
inputanyUpstream data for {{ input.field }} template references in settings.

Output

HandleTypeDescription
resultobjectGoogle Drive operation result

The result (accessed as {{ google_drive.* }}) shape:

FieldTypeDescription
successbooleanWhether the operation succeeded
filesarrayMatching files (list/search operations)
responseobjectRaw Google Drive API response

Settings

Each node run executes a single operation. Set Operation, then configure the fields shown for that operation.

Operation

SettingTypeDefaultDescription
operationenumlist_filesDrive action to perform: list_files, search_files, get_file, create_folder, upload_file, download_file, delete_file, or move_file.

Agent Permissions

SettingTypeDefaultDescription
allowed_operationsmulti-selectAll operationsWhich operations are available when this plugin is used as an AI agent tool.

Target

Shown for operations that need a file or folder:

SettingTypeDefaultDescription
file_idstring—Google Drive file ID. Supports {{ }} bindings.
folder_idstring—Parent folder ID (root if empty). Supports {{ }} bindings.
querystring—Drive search query (e.g. name contains 'report'). Supports {{ }} bindings.

Content

Shown for create/upload operations:

SettingTypeDefaultDescription
file_namestring—File or folder name. Supports {{ }} bindings.
datacode editor—File content for upload operations. Supports {{ }} bindings.

Example

Append a generated report to Drive on a webhook:

Webhook Trigger → Google Drive (upload_file)

Google Drive settings:

  • Operation: upload_file
  • Folder ID: 1AbC... (destination folder)
  • File Name: report-{{ webhook.body.id }}.txt
  • Data: {{ webhook.body.content }}

See Also

On this page