Google Drive

Store, share, and collaborate on files and folders in Google Drive.

Detail	Value
Category	Productivity
Base URL	https://www.googleapis.com/drive/v3
Authentication	OAuth2
Endpoints	6
Connector key	google-drive

Using Google Drive in a workflow

1. Go to Connections and click New Connection.
2. Pick Google Drive from the marketplace.
3. Enter your credentials (see Authentication above for what's expected).
4. In a workflow, drop an API Call node and select this connection.
5. Pick the operation you need from the Operation dropdown. The full list is below.

Available endpoints

Endpoint	Summary
GET /files	List files
POST /files	Create a file
GET /files/{fileId}	Get file metadata
PATCH /files/{fileId}	Update file metadata
DELETE /files/{fileId}	Delete a file
POST /files/{fileId}/permissions	Share a file

Each endpoint is documented in full below. Use the outline on the right to jump to one.

GET /files

List files

Detail	Value
Operation ID	productivity.listFiles
Method	GET
Path	/files

Parameters

Name	Location	Type	Required
q	query	string	No
pageSize	query	integer	No

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Google Drive connection from the Connection dropdown.
3. In the Operation dropdown, select productivity.listFiles.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Google Drive API reference.

POST /files

Create a file

Detail	Value
Operation ID	productivity.createFile
Method	POST
Path	/files

Parameters

No parameters.

Request Body

Field	Type
name	string
mimeType	string

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Google Drive connection from the Connection dropdown.
3. In the Operation dropdown, select productivity.createFile.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked: fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Google Drive API reference.

GET /files/{fileId}

Get file metadata

Detail	Value
Operation ID	productivity.getFile
Method	GET
Path	/files/{fileId}

Parameters

Name	Location	Type	Required
fileId	path	string	Yes

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Google Drive connection from the Connection dropdown.
3. In the Operation dropdown, select productivity.getFile.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked: fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Google Drive API reference.

PATCH /files/{fileId}

Update file metadata

Detail	Value
Operation ID	productivity.updateFile
Method	PATCH
Path	/files/{fileId}

Parameters

Name	Location	Type	Required
fileId	path	string	Yes

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Google Drive connection from the Connection dropdown.
3. In the Operation dropdown, select productivity.updateFile.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked: fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Google Drive API reference.

DELETE /files/{fileId}

Delete a file

Detail	Value
Operation ID	productivity.deleteFile
Method	DELETE
Path	/files/{fileId}

Parameters

Name	Location	Type	Required
fileId	path	string	Yes

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Google Drive connection from the Connection dropdown.
3. In the Operation dropdown, select productivity.deleteFile.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked: fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Google Drive API reference.

POST /files/{fileId}/permissions

Share a file

Detail	Value
Operation ID	productivity.createPermission
Method	POST
Path	/files/{fileId}/permissions

Parameters

Name	Location	Type	Required
fileId	path	string	Yes

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Google Drive connection from the Connection dropdown.
3. In the Operation dropdown, select productivity.createPermission.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked: fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Google Drive API reference.