Get Job
storage_batch_operations.get_job
ActionGoogle Cloudconnection required
Calls Storage Batch Operations GET /v1/projects/{projectsId}/locations/{locationsId}/jobs/{jobsId}.
Gets a batch job.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- OAuth 2.0
- Providers
- Google Storage Batch Operations
- Secret shape
- {"client_id", "client_secret", "refresh_token"}
- Config it needs
- location, project_id
- Resolved by
- config.connection_id, else node.connection_id
Configuration
3 fields, 1 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 |
|---|---|---|---|---|---|
project_id GCP project id (overrides connection). | string | No | — | — | — |
location Location / region (overrides connection). | string | No | — | — | — |
job Id of the job to act on, from storage_batch_operations.list_jobs — not its name. | string | Yes | — | — | — |
Output
One shape.
result
| Field | Type | Example |
|---|---|---|
ok | boolean | — |
bucketList | object | — |
completeTime | string | — |
description | string | — |
isMultiBucketJob | boolean | — |
deleteObject | object | — |
putObjectHold | object | — |
{
"bucketList": {},
"completeTime": "",
"deleteObject": {},
"description": "",
"isMultiBucketJob": false,
"ok": false,
"putObjectHold": {}
}Related Google Storage Batch Operations nodes
See Get Job run in a workflow.
In a technical demo we add the Google Storage Batch Operations connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.