Update Backup

filestore.update_backup
ActionGoogle Cloudconnection required

Calls file v1 PATCH /v1/projects/{projectsId}/locations/{locationsId}/backups/{backupsId}.

Updates the settings of a specific backup.

Connection

Required
Yes — the node will not save without one
Auth type
OAuth 2.0
Providers
Google Cloud Filestore
Secret shape
{"client_id", "client_secret", "refresh_token"}
Config it needs
project_id, location
Resolved by
config.connection_id, else node.connection_id

Configuration

4 fields, 2 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.

FieldTypeRequiredDefaultConstraintsExample
location
Location or region; taken from the connection when unset.
stringNo———
backup
Backup name or id.
stringYes———
body
The Backup resource, as the API defines it.
objectYes———
update_mask
Mask of fields to update. Optional.
stringNo———

Output

One shape.

result

Extra keys beyond the ones listed can appear.

FieldTypeExample
done
boolean—
error
object—
metadata
object—
name
string—
response
object—
{
  "done": false,
  "error": {},
  "metadata": {},
  "name": "",
  "response": {}
}

See Update Backup run in a workflow.

In a technical demo we add the Google Cloud Filestore connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.