Update Transfer Job
storage_transfer.update_transfer_job
ActionGoogle Cloudconnection required
Calls storagetransfer v1 PATCH /v1/transferJobs/{transferJobsId}.
Updates a transfer job.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- OAuth 2.0
- Providers
- Google Storage Transfer
- Secret shape
- {"client_id", "client_secret", "refresh_token"}
- Resolved by
- config.connection_id, else node.connection_id
Configuration
2 fields, 2 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 |
|---|---|---|---|---|---|
transfer_job Transfer job name or id. | string | Yes | — | — | — |
body The UpdateTransferJobRequest resource, as the API defines it. | object | Yes | — | — | — |
Output
One shape.
result
Extra keys beyond the ones listed can appear.
| Field | Type | Example |
|---|---|---|
creationTime | string | — |
deletionTime | string | — |
description | string | — |
eventStream | object | — |
lastModificationTime | string | — |
latestOperationName | string | — |
loggingConfig | object | — |
name | string | — |
notificationConfig | object | — |
projectId | string | — |
replicationSpec | object | — |
schedule | object | — |
serviceAccount | string | — |
status | string | — |
transferSpec | object | — |
{
"creationTime": "",
"deletionTime": "",
"description": "",
"eventStream": {},
"lastModificationTime": "",
"latestOperationName": "",
"loggingConfig": {},
"name": "",
"notificationConfig": {},
"projectId": "",
"replicationSpec": {},
"schedule": {},
"serviceAccount": "",
"status": "",
"transferSpec": {}
}Related Google Storage Transfer nodes
See Update Transfer Job run in a workflow.
In a technical demo we add the Google Storage Transfer connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.