Studio Project workflows for Google Drive files, folders, Shared Drives, and permissions
Google Drive is a cloud file storage and collaboration service — files and folders, Shared Drives, permissions/sharing, comments, and revision history, accessible over a REST API.
This project provides OpenAPI specs for automating against the Google Drive REST API via an Integration Model. The -latest spec is a curated subset covering common CRUD for automation — see OpenAPIs below.
| Asset | Description |
|---|---|
| OpenAPIs/ | Google Drive REST API OpenAPI specs — curated -latest plus the full dated spec |
| Studio Projects/Google Drive | 21 workflows covering common CRUD automation |
| Requirement | Version |
|---|---|
| Itential Platform | 6.x |
| Google Drive API | v3 |
| Google Drive Integration Model | Required to build automation against the OpenAPI spec |
Import the OpenAPI spec from OpenAPIs/ as an Integration Model in Admin > Integrations, then create an integration pointing at https://www.googleapis.com/drive/v3.
Authentication is a Google OAuth2 access token, sent as a Bearer token in the Authorization header:
Authorization: Bearer <access_token> Obtain an access token via the Google Cloud Console → Service Accounts, granted a Drive API OAuth scope (e.g. https://www.googleapis.com/auth/drive), using the client_credentials flow for a service account or a delegated-user OAuth2 authorization-code flow.
The instance's authentication/server properties should look like this once configured:
{
"authentication": {
"Oauth2c": {
"client_id": "<your-client-id>",
"client_secret": "<your-client-secret>",
"token_url": "https://accounts.google.com/o/oauth2/token",
"refresh_url": "",
"scope": "",
"token": {
"access_token": ""
},
"authorization_url": "https://accounts.google.com/o/oauth2/auth"
}
},
"server": {
"protocol": "https",
"host": "www.googleapis.com",
"base_path": "/drive/v3"
}
} | Spec | Version | Operations | Description |
|---|---|---|---|
google_drive-latest.json | latest (curated) | 35 | Actively-maintained spec, trimmed to 35 of 48 upstream operations — see breakdown below |
google_drive-v3.json | v3 | 48 | Full spec for the Google Drive v3 API (48 operations) |
google_drive-latest.jsonActively-maintained spec (x-vendor-api-version: v3). Trimmed to 35 of 48 upstream operations covering common CRUD for automation.
Resources included, by category:
Not included: change/activity polling and push-notification channels (changes, channels — sync-client tooling), the legacy teamdrives resource (superseded by drives), file ID pre-generation (files.generateIds), file watch/push notifications (files.watch), and the Drive Labels endpoints (files.listLabels, files.modifyLabels — a separate, optional Google Workspace add-on).
google_drive-v3.jsonFull, unmodified vendor spec for the Google Drive v3 API (48 operations) — the vendor's complete API surface, preserved as-is. See google_drive-latest.json above for the curated subset if you just need common CRUD automation.
Backed by the Google Drive:latest Integration Model (see google_drive-latest.json above). The project contains 21 workflows organized into 4 folders, one atomic workflow per API operation, covering the common-CRUD subset of the curated spec.
| Folder | Workflows | Scope |
|---|---|---|
| Files | List, Get, Create, Update, Delete, Copy File | File lifecycle |
| Drives | List, Get, Create, Update, Delete Drive | Shared drive lifecycle |
| Permissions | List, Get, Create, Update, Delete Permission | File/drive sharing |
| Comments | List, Get, Create, Update, Delete Comment | File comments |
| Dependency | Notes |
|---|---|
Google Drive:latest Integration Model | Import from google_drive-latest.json before importing the project |
Google Drive integration instance | Create in Admin > Integrations with the connection properties above. Workflows are wired to an integration instance named Google Drive — update the adapter_id value in each workflow task if yours is named differently |