Replace Permission
google_drive.replace_permission
ActionFiles & storageconnection required
Calls drive v3 PATCH /files/{fileId}/permissions/{permissionId}.
Updates a permission with patch semantics.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- OAuth 2.0
- Providers
- Google Drive
- Secret shape
- {"client_id", "client_secret", "refresh_token"}
- Config it needs
- token_uri
- Resolved by
- config.connection_id, else node.connection_id
Configuration
3 fields, 3 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
file File name or id. | string | Yes | — | — | — |
permission Permission name or id. | string | Yes | — | — | — |
body The Permission resource, as the API defines it. | object | Yes | — | — | — |
Output
One shape.
result
| Field | Type | Example |
|---|---|---|
id | string | — |
name | string | — |
{
"id": "",
"name": ""
}Related Google Drive nodes
See Replace Permission run in a workflow.
In a technical demo we add the Google Drive connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.