Automate Google Drive Labels
HumDay reads Google Drive Labels’s own published API description and derives 16 operations from it. Describe the outcome you want in plain words — you get a program that is written, proven on real data, and run for you.
What Google Drive Labels is
An API for managing Drive Labels
API host: drivelabels.googleapis.com
What HumDay can do in Google Drive Labels
11 documented operations change something in Google Drive Labels.
- POSTCreates a new Label.
/v2beta/labels - POSTUpdates a single Label by applying a set of update requests resulting in a new draft revision.
/v2beta/{name}:delta - POSTEnable a disabled Label and restore it to its published state.
/v2beta/{name}:enable - POSTDisable a published Label.
/v2beta/{name}:disable - POSTPublish all draft changes to the Label.
/v2beta/{name}:publish - POSTUpdates a Label's CopyMode.
/v2beta/{name}:updateLabelCopyMode - PATCHUpdates a Label's permissions.
/v2beta/{parent}/permissions - POSTUpdates a Label's permissions.
/v2beta/{parent}/permissions - POSTDeletes Label permissions.
/v2beta/{parent}/permissions:batchDelete - POSTUpdates Label permissions.
/v2beta/{parent}/permissions:batchUpdate - DELETEDeletes a Label's permission.
/v2beta/{name}
What HumDay can read from Google Drive Labels
These are the operations a schedule or a trigger can watch.
- GETGets the user capabilities.
/v2beta/{name} - GETList labels.
/v2beta/labels - GETGet the constraints on the structure of a Label; such as, the maximum number of Fields allowed and maximum length of the label title.
/v2beta/limits/label - GETLists the LabelLocks on a Label.
/v2beta/{parent}/locks - GETLists a Label's permissions.
/v2beta/{parent}/permissions
How automating Google Drive Labels works
- Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
- 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.
- See it proven. The program runs and shows you the result before it is allowed near your live Google Drive Labels account.
- Grant access, then go live. You approve the specific Google Drive Labels operations it may use — and only those.
Automate Google Drive Labels 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
Questions about Google Drive Labels automation
- Can HumDay connect to Google Drive Labels?
- Yes. HumDay reads Google Drive Labels's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 16 operations are documented.
- Do I need to write code to automate Google Drive Labels?
- 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 Labels account.
- What can HumDay do in Google Drive Labels?
- 11 of the 16 documented operations change something in Google Drive Labels, and 5 read from it. HumDay only ever uses the specific operations your approved contract needs.
- Is my Google Drive Labels 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 Labels is held behind that approval.
Where this came from
The operations above are read from a published API description for Google Drive Labels at drivelabels.googleapis.com/$discovery/rest?version=v2beta. Descriptions are the provider’s own words, not ours. Last published 2023-04-21.