Automate Google Drive

What Google Drive is

Manages files in Drive including uploading, downloading, searching, detecting changes, and updating sharing permissions.

API host: www.googleapis.com

Things people automate with Google Drive

• Get a Slack notice when a file lands in Google DriveGoogle Drive → Slack
• Get a Telegram notice when a file lands in Google DriveGoogle Drive → Telegram
• Get a Google Chat notice when a file lands in Google DriveGoogle Drive → Google Chat

What HumDay can do in Google Drive

28 documented operations change something in Google Drive.

• POSTCreates a file./files
• POSTCreates a comment on a file./files/{fileId}/comments
• DELETEPermanently deletes a file owned by the user without moving it to the trash./files/{fileId}
• POSTCreates a copy of a file and applies any requested updates with patch semantics./files/{fileId}/copy
• DELETEPermanently deletes all of the user's trashed files./files/trash
• POSTStop watching resources through this channel/channels/stop
• POSTCreates a reply to a comment./files/{fileId}/comments/{commentId}/replies
• PATCHUpdates a file's metadata and/or content./files/{fileId}
• DELETEDeletes a comment./files/{fileId}/comments/{commentId}
• PATCHUpdates a comment with patch semantics./files/{fileId}/comments/{commentId}
• POSTCreates a shared drive./drives
• POSTSubscribes to changes to a file./files/{fileId}/watch
• POSTModifies the set of labels on a file./files/{fileId}/modifyLabels
• POSTSubscribes to changes for a user./changes/watch
• DELETEPermanently deletes a shared drive for which the user is an organizer./drives/{driveId}
• DELETEPermanently deletes a file version./files/{fileId}/revisions/{revisionId}
• DELETEDeletes a reply./files/{fileId}/comments/{commentId}/replies/{replyId}
• PATCHUpdates a reply with patch semantics./files/{fileId}/comments/{commentId}/replies/{replyId}
• PATCHUpdates the metadata for a shared drive./drives/{driveId}
• PATCHUpdates a revision with patch semantics./files/{fileId}/revisions/{revisionId}
• POSTHides a shared drive from the default view./drives/{driveId}/hide
• POSTRestores a shared drive to the default view./drives/{driveId}/unhide
• POSTCreates a permission for a file or shared drive./files/{fileId}/permissions
• POSTDeprecated use drives.create instead./teamdrives
• DELETEDeprecated use drives.delete instead./teamdrives/{teamDriveId}
• PATCHDeprecated use drives.update instead/teamdrives/{teamDriveId}
• DELETEDeletes a permission./files/{fileId}/permissions/{permissionId}
• PATCHUpdates a permission with patch semantics./files/{fileId}/permissions/{permissionId}

What HumDay can read from Google Drive

These are the operations a schedule or a trigger can watch.

• GETGenerates a set of file IDs which can be provided in create or copy requests./files/generateIds
• GETLists a file's comments./files/{fileId}/comments
• GETGets a file's metadata or content by ID./files/{fileId}
• GETGets information about the user, the user's Drive, and system capabilities./about
• GETLists or searches files./files
• GETGets a comment by ID./files/{fileId}/comments/{commentId}
• GETLists the user's shared drives./drives
• GETLists the changes for a user or shared drive./changes
• GETExports a Google Workspace document to the requested MIME type and returns exported byte content./files/{fileId}/export
• GETLists a file's revisions./files/{fileId}/revisions
• GETLists the labels on a file./files/{fileId}/listLabels
• GETLists a file's or shared drive's permissions./files/{fileId}/permissions
• GETLists a comment's replies./files/{fileId}/comments/{commentId}/replies
• GETGets a reply by ID./files/{fileId}/comments/{commentId}/replies/{replyId}
• GETGets the starting pageToken for listing future changes./changes/startPageToken
• GETGets a shared drive's metadata by ID./drives/{driveId}
• GETGets a revision's metadata or content by ID./files/{fileId}/revisions/{revisionId}
• GETDeprecated use drives.list instead./teamdrives
• GETDeprecated use drives.get instead./teamdrives/{teamDriveId}
• GETGets a permission by ID./files/{fileId}/permissions/{permissionId}

How automating Google Drive works

1. Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
2. Approve the contract. HumDay writes down exactly what it will do, what it will touch, and what it will never do. You approve it before anything is built.
3. See it proven. The program runs and shows you the result before it is allowed near your live Google Drive account.
4. Grant access, then go live. You approve the specific Google Drive operations it may use — and only those.

Popular Google Drive integrations

Connect Google Drive to the tools people pair it with most.

• Google Drive and OData for namespace microsoft.graphintegration
• Google Drive and Cloudflareintegration
• Google Drive and NetBoxintegration
• Google Drive and GitHubintegration
• Google Drive and Mistintegration
• Google Drive and Loket.nlintegration
• Google Drive and Atlassian The Jira Cloud platformintegration
• Google Drive and Magento B2Bintegration
• Google Drive and Stripeintegration
• Google Drive and Zuora Reference Billingintegration
• Google Drive and bunqintegration
• Google Drive and DocuSignintegration

Automate Google Drive with these

• Gmail79 operations
• Google+9 operations
• Google Abusive Experience Report2 operations
• Google Accelerated Mobile Pages (AMP) URL1 operations
• Google Access Approval7 operations
• Google Access Context Manager9 operations
• Google ACME DNS2 operations
• Google Ad Exchange Buyer38 operations
• Google Ad Exchange Buyer II50 operations
• Google Ad Experience Report2 operations
• Google Admin SDK122 operations
• Google AdMob7 operations

Categories

• Analytics
• Media

Questions about Google Drive automation

Can HumDay connect to Google Drive?

Yes. HumDay reads Google Drive's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 48 operations are documented.

Do I need to write code to automate Google Drive?

No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a test run before anything touches your Google Drive account.

What can HumDay do in Google Drive?

28 of the 48 documented operations change something in Google Drive, and 20 read from it. HumDay only ever uses the specific operations your approved contract needs.

Is my Google Drive account safe?

Your credentials are stored encrypted and are never shown in chat, code, or logs. Every run is limited to the operations you explicitly approved, and anything that writes to Google Drive is held behind that approval.

Where this came from

The operations above are read from a published API description for Google Drive at www.googleapis.com/discovery/v1/apis/drive/v3/rest. Descriptions are the provider’s own words, not ours. Last published 2023-04-20.