Google Drive connector
The Google Drive connector lets you create and configure a Google Drive connection in Integration Connectors. You can use this connection in your business applications to securely exchange data and perform operations with Google Drive.
For the list of supported entities and operations, see Supported entities and operations. For information about the supported connector-specific actions, see Supported actions.
Google Drive connector versions
The Google Drive connector supports two versions:
- Google Drive v1: use this connector version to access the Google Drive v3 API.
- Google Drive v2: use this connector version to access the Google Drive v2 API.
For information about creating a Google Drive connection, see Create and configure a Google Drive connector.
Supported entities and operations
The Google Drive connector supports the following entities and operations:
| Entity | Description | Operations |
|---|---|---|
File |
Represents a file in Google Drive. | Get, List, Create, Update, Delete |
Folder |
Represents a folder in Google Drive. | Get, List, Create, Update, Delete |
Permission |
Represents a permission for a file or folder in Google Drive. | Get, List, Create, Update, Delete |
Drive |
Represents a drive in Google Drive. | Get, List, Create, Update, Delete |
For Application Integration usecase examples, see Use case examples in Application Integration.
Supported actions
The Google Drive connector supports the following actions:
- CopyResource
- Description: creates a copy of a specified resource in Google Drive. You can define a new name for the copied file and specify its destination folder by providing a list of parent folder IDs .
Input parameters
Parameter name Data type Required Description IdString Yes The ID of the resource to be copied. NewNameString Yes The new name of the copied file. ParentIDsString No A comma-separated list of parent folder IDs in which the copied file will be placed. If not specified, the file will be copied to the same folder where the file was located. IgnoreDefaultVisibilityBoolean No Determines whether to bypass the default visibility settings for the newly created file. If the domain is configured to make all uploaded files visible by default, setting this parameter to true overrides that behavior for this specific request. The default value is false.
IncludeLabelsString No A comma-separated list of IDs of labels to include in the labelInfo part of the response. IncludePermissionsForViewString Yes This field specifies which additional view permissions to include in the response. The supported value is published. KeepRevisionForeverBoolean No Indicates whether to keep the revisions of the file forever. This feature applies only to files with binary content in Google Drive. A maximum of 200 revisions can be kept forever per file. If the limit is reached, you must delete existing revisions to add new ones. The default value is false.
OCRLanguageString No This field provides a language hint for OCR (Optical Character Recognition) when importing image files. Specify the language using an ISO 639-1 two-letter language code, such as,
enfor English,defor German.SupportsAllDrivesBoolean Yes This parameter indicates whether to track the changes in My Drives and shared drives.
Set this parameter to true to enable access to shared drives. The default value is false.
Output parameters
Parameter name Data type Description CopiedFileIDString The ID of the copied file. SuccessString This parameter indicates whether the operation was successful or not. Usecase example
The following example shows how to configure the
CopyResourceaction in Application Integration:- In the Configure connector task dialog, click Actions.
- Select the
CopyResourceaction, and then click Done. - In the Task Input section of the Connectors task, click
connectorInputPayloadand then enter a value similar to the following in theDefault Valuefield:{ "Id": "10QIXnPK3DjiLnVL1QvpIsuHPo16zVkYQuJsTVvt_B-c", "NewName": "Copied of Untitles Document.txt1750848165952", "ParentIDs": "1uaAUsRZLLF07KypCDNUBvHn3Xx2lxmo5"}If the action is successful, the connector task's
connectorOutputPayloadresponse parameter will have a value similar to the following:[{"CopiedFileID": "15NUzJGarp-b8TdT0tXBGD9hJMnYjZbiydaE4lbZV0EU", "Success": "TRUE"}]
- CreateFolder
- Description: creates a new folder within your Google Drive. You must provide a name for the new folder and specify its location by providing the IDs of its parent folders. You can also add an optional description and mark the folder as starred.
Input parameters
Parameter name Data type Required Description NameString Yes The title for the folder. DescriptionString No The description for the folder. StarredBoolean No This parameter indicates whether the folder is starred. The default value is false.
ParentIdsString Yes A comma-separated list of IDs of the parent folders in which the new folder will be created. Output parameters
Parameter name Data type Description SuccessString This parameter indicates whether the operation was successful or not. IdString The ID of the new folder. Usecase example
The following example shows how to configure the
CreateFolderaction in Application Integration:- In the Configure connector task dialog, click Actions.
- Select the
CreateFolderaction, and then click Done. - In the Task Input section of the Connectors task, click
connectorInputPayloadand then enter a value similar to the following in theDefault Valuefield:{ "Name": "Test Folder", "ParentIds": "1uaAUsRZLLF07KypCDNUBvHn3Xx2lxmo5"}If the action is successful, the connector task's
connectorOutputPayloadresponse parameter will have a value similar to the following:[{"Success": "TRUE", "Id": "10QIXnPK3DjiLnVL1QvpIsuHPo16zVkYQuJsTVvt_B-c"}]
- DeleteResource
- Description: permanently removes a file or folder from Google Drive. To use this action, you need to provide the unique ID of the resource you wish to delete.
Input parameters
Parameter name Data type Required Description IdString Yes The ID of the resource to be deleted. Output parameters
Parameter name Data type Description SuccessString This parameter indicates whether the operation was successful or not. Usecase example
The following example shows how to configure the
DeleteResourceaction in Application Integration:- In the Configure connector task dialog, click Actions.
- Select the
DeleteResourceaction, and then click Done. - In the Task Input section of the Connectors task, click
connectorInputPayloadand then enter a value similar to the following in theDefault Valuefield:{ "Id": "10QIXnPK3DjiLnVL1QvpIsuHPo16zVkYQuJsTVvt_B-c"}If the action is successful, the connector task's
connectorOutputPayloadresponse parameter will have a value similar to the following:[{"Success": "TRUE"}]
- DownloadFile
- Description: downloads a file from Google Drive
Input parameters
Parameter name Data type Required Description IdString Yes The ID of the file to be downloaded. LocalFileString No The file path and file name where the file will be saved, leave empty to store the file in memory instead. EncodingString No The encoding type for the file data. If LocalFile is empty, the file data will be returned in the specified encoding. The allowed values are NONE, and BASE64. The default value is BASE64. OverwriteBoolean No This parameter determines whether to overwrite the file if it already exists when downloading.
The default value is false, set the parameter to TRUE to overwrite the file.FileFormatString No The format in which the file can be downloaded, maximum size of the file can be 10MB. Leave this parameter blank to download in its original format. The supported formats are DOCX, ODT, RTF, HTML, TXT, and PDF. Output parameters
Parameter name Data type Description FileDataString If LocalFile is not provided, the file data will be returned using the specified Encoding. SuccessString This parameter indicates whether the operation was successful or not. Usecase example
The following example shows how to configure the
DownloadFileaction in Application Integration:- In the Configure connector task dialog, click Actions.
- Select the
DownloadFileaction, and then click Done. - In the Task Input section of the Connectors task, click
connectorInputPayloadand then enter a value similar to the following in theDefault Valuefield:{ "Id": "10QIXnPK3DjiLnVL1QvpIsuHPo16zVkYQuJsTVvt_B-c", "LocalFile": "gs://test-bucket/test-file.txt", "Encoding": "NONE", "Overwrite": true, "FileFormat": "HTML"}If the action is successful, the connector task's
connectorOutputPayloadresponse parameter will have a value similar to the following:[{"FileData": "This is a test file.", "Success": "TRUE"}]
- MoveResource
- Description: moves a file or folder to a different location within Google Drive. You need to provide the ID of the resource to be moved and the IDs of the new parent folders.
Input parameters
Parameter name Data type Required Description IdString Yes The ID of the resource to be moved. ParentIDsString Yes A comma-separated list of IDs to be used as parent folders.
A resource within a shared drive must have exactly one parent folder, and only users with the 'file organizer' or 'organizer' role can move files and folders within a shared drive.Output parameters
Parameter name Data type Description SuccessString This parameter indicates whether the operation was successful or not. Usecase example
The following example shows how to configure the
MoveResourceaction in Application Integration:- In the Configure connector task dialog, click Actions.
- Select the
MoveResourceaction, and then click Done. - In the Task Input section of the Connectors task, click
connectorInputPayloadand then enter a value similar to the following in theDefault Valuefield:{ "Id": "10QIXnPK3DjiLnVL1QvpIsuHPo16zVkYQuJsTVvt_B-c", "ParentIDs": "1uaAUsRZLLF07KypCDNUBvHn3Xx2lxmo5"}If the action is successful, the connector task's
connectorOutputPayloadresponse parameter will have a value similar to the following:[{"Success": "TRUE"}]
- UpdateResource
- Description: updates the metadata of a file or folder in Google Drive. You can modify its name, description, MIME type, and whether it's starred.
Input parameters
Parameter name Data type Required Description IdString Yes The ID of the resource to be updated. NameString Yes The new name of the updated file. DescriptionString No A description of the file or folder. MIMETypeString No The MIME type of the file. StarredString No This parameter indiactes whether the resource is starred. The default value is false.
Output parameters
Parameter name Data type Description SuccessString This parameter indicates whether the operation was successful or not. Usecase example
The following example shows how to configure the
UpdateResourceaction in Application Integration:- In the Configure connector task dialog, click Actions.
- Select the
UpdateResourceaction, and then click Done. - In the Task Input section of the Connectors task, click
connectorInputPayloadand then enter a value similar to the following in theDefault Valuefield:{ "Id": "10QIXnPK3DjiLnVL1QvpIsuHPo16zVkYQuJsTVvt_B-c", "Name": "New Name", "Description": "New Description", "MIMEType": "application/vnd.google-apps.document", "Starred": true}If the action is successful, the connector task's
connectorOutputPayloadresponse parameter will have a value similar to the following:[{"Success": "TRUE"}]
- UploadFile
- Description: uploads a file to Google Drive. You must provide the file data and its MIME type. You can also specify the parent folder where the file will be placed and a filename for the uploaded file.
Input parameters
Parameter name Data type Required Description IdString Yes The ID of the file to be uploaded. FileDataString Yes The file data to be uploaded. MIMETypeString Yes The MIME type of the file. ParentIDsString No A comma-separated list of parent folder IDs in which the uploaded file will be placed. If not specified, the file will be uploaded to the root folder of the user's My Drive. FilenameString No The name of the file to be uploaded. Output parameters
Parameter name Data type Description SuccessString This parameter indicates whether the operation was successful or not. Usecase example
The following example shows how to configure the
UploadFileaction in Application Integration:- In the Configure connector task dialog, click Actions.
- Select the
UploadFileaction, and then click Done. - In the Task Input section of the Connectors task, click
connectorInputPayloadand then enter a value similar to the following in theDefault Valuefield:{ "Id": "10QIXnPK3DjiLnVL1QvpIsuHPo16zVkYQuJsTVvt_B-c", "FileData": "This is a test file.", "MIMEType": "text/plain", "ParentIDs": "1uaAUsRZLLF07KypCDNUBvHn3Xx2lxmo5", "Filename": "test-file.txt"}If the action is successful, the connector task's
connectorOutputPayloadresponse parameter will have a value similar to the following:[{"Success": "TRUE"}]
- SubscribeToFileChanges
- Description: subscribes to notifications for changes to a specific file in Google Drive.
Input parameters
Parameter name Data type Required Description IdString Yes The ID of the file to be subscribed to. TokenString Yes The token to be used for subscribing to file changes. Output parameters
Parameter name Data type Description SuccessString This parameter indicates whether the operation was successful or not. Usecase example
The following example shows how to configure the
SubscribeToFileChangesaction in Application Integration:- In the Configure connector task dialog, click Actions.
- Select the
SubscribeToFileChangesaction, and then click Done. - In the Task Input section of the Connectors task, click
connectorInputPayloadand then enter a value similar to the following in theDefault Valuefield:{ "FileId": "1o-SMcimUT91sfLNf6NoESirH9BsVqvym0YORLo2GAoY", "Id": "Id11752060129918", "Address": "https://cloudsearch.googleapis.net/notifications", "ChannelToken": "token" }If the action is successful, the connector task's
connectorOutputPayloadresponse parameter will have a value similar to the following:[ { "Kind": "api#channel", "Id": "Id11752060129918", "ResourceId": "BfrGPBKDiD1SH1dg6Ng73nLTfl0", "ResourceUri": "https://www.googleapis.com/drive/v3/files/1o-SMcimUT91sfLNf6NoESirH9BsVqvym0YORLo2GAoY?alt=json&supportsAllDrives=true", "Token": "token", "Expiration": "1752063731000" } ]
- SubscribeToUserChanges
- Description: subscribes to notifications for changes made by a specific user in Google Drive.
Input parameters
Parameter name Data type Required Description IdString Yes The ID of the user to be subscribed to. TokenString Yes The token to be used for subscribing to user changes. Usecase example
The following example shows how to configure the
SubscribeToUserChangesaction in Application Integration:- In the Configure connector task dialog, click Actions.
- Select the
SubscribeToUserChangesaction, and then click Done. - In the Task Input section of the Connectors task, click
connectorInputPayloadand then enter a value similar to the following in theDefault Valuefield:{ "Id": "11752060129918", "Address": "https://cloudsearch.googleapis.net/notifications", "ChannelToken": "token" }If the action is successful, the connector task's
connectorOutputPayloadresponse parameter will have a value similar to the following:[ { "Kind": "api#channel", "Id": "Id11752060129918", "ResourceId": "BfrGPBKDiD1SH1dg6Ng73nLTfl0", "ResourceUri": "https://www.googleapis.com/drive/v3/users/me?alt=json&supportsAllDrives=true", "Token": "token", "Expiration": "1752063731000" } ]
- StopWatchingResources
- Description: unsubscribes you from receiving notifications for a previously watched resource.
Input parameters
Parameter name Data type Required Description IdString Yes The ID of the resource to be stopped watching. TokenString Yes The token to be used for stopping watching resources. Usecase example
The following example shows how to configure the
StopWatchingResourcesaction in Application Integration:- In the Configure connector task dialog, click Actions.
- Select the
StopWatchingResourcesaction, and then click Done. - In the Task Input section of the Connectors task, click
connectorInputPayloadand then enter a value similar to the following in theDefault Valuefield:{ "Id": "Id11752060129918", "Token": "token" }If the action is successful, the connector task's
connectorOutputPayloadresponse parameter will have a value similar to the following:[ { "Kind": "api#channel", "Id": "stopid1751971586168", "ResourceId": "CXPNGzAnYjqSazkd9-nNTFHTkwo", "ResourceUri": "https://www.googleapis.com/drive/v3/files/11OsOCgkV5hsRai6UwpkLngvqnCcrA4sy1tqfPi_VJio?alt=json&supportsAllDrives=true", "Token": null, "Expiration": "1751975186000" } ]
System limitations
The Google Drive connector can process a maximum of 2QPS transactions per second, per node, and throttles any transactions beyond this limit. By default, Integration Connectors allocates 2 nodes (for better availability) for a connection.
For information on the limits applicable to Integration Connectors, see Limits.
What's next
- Learn how to create and configure a Google Drive connection.
- Understand how to suspend and resume a connection.
- Understand how to monitor connector usage.
- Understand how to view connector logs.