Gets a comment by ID in Google Drive
A documented Google Drive operation that only reads, so it can watch for changes without altering anything. Describe what you want to happen and HumDay builds it.
What this operation does
Gets a comment by ID.
- GETReads data · comments
www.googleapis.com/files/{fileId}/comments/{commentId}
How HumDay uses it
- You describe the outcome. Not this operation by name — what you want to happen. HumDay works out which operations it needs.
- The contract names it. Before anything is built, you see exactly which Google Drive operations the program may use, and this is one of them.
- You approve access. Read-only access is still yours to grant, and still limited to what the contract needs.
Other Google Drive operations
- Creates a filePOST · changes data
- Creates a comment on a filePOST · changes data
- Permanently deletes a file owned by the user without moving itDELETE · changes data
- Creates a copy of a file and applies any requested updatesPOST · changes data
- Permanently deletes all of the user's trashed filesDELETE · changes data
- Stop watching resources through this channelPOST · changes data
- Creates a reply to a commentPOST · changes data
- Updates a file's metadata and/or contentPATCH · changes data
Questions
- Can HumDay gets a comment by id in Google Drive?
- Yes. This operation is published in Google Drive's own API description, so HumDay can use it without a hand-built connector — once you have approved it for your automation.
- Does this change anything in my Google Drive account?
- No. This is a read-only operation, so it can be used to watch for changes or fetch data without altering anything in Google Drive.
- Do I need to write code?
- No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a proof run before anything touches your Google Drive account.
Where this came from
Read from a published API description for Google Drive at www.googleapis.com/discovery/v1/apis/drive/v3/rest. The description above is the provider’s own wording, not ours. Last published 2023-04-20.