Create Backup Plan

gke_backup.create_backup_plan
ActionGoogle Cloudconnection required

Calls gkebackup v1 POST /v1/projects/{projectsId}/locations/{locationsId}/backupPlans.

Creates a new BackupPlan in a given location.

Connection

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

Configuration

3 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———
body
The BackupPlan resource, as the API defines it.
objectYes———
backup_plan_id
The client-provided short name for the BackupPlan resource. Required.
stringYes———

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 Create Backup Plan run in a workflow.

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