Batch Enable
service_usage.batch_enable
ActionGoogle Cloudconnection required
Calls Service Usage POST /v1/{v1Id}/{v1Id1}/services:batchEnable.
Enable multiple services on a project. The operation is atomic: if enabling any service fails, then the entire batch fails, and no state changes occur.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- OAuth 2.0
- Providers
- Google Service Usage
- Secret shape
- {"client_id", "client_secret", "refresh_token"}
- 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 |
|---|---|---|---|---|---|
scope_type Scope kind for the search. | string | No | projects | one of "projects", "folders", "organizations" | — |
scope_id Id of the scope to act on, from its Service Usage URL or console — not its name. | string | Yes | — | — | — |
body Request body (BatchEnableServicesRequest) as JSON. | object | No | — | — | — |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"scope_type": "projects"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
ok | boolean | — |
error | object | — |
response | object | — |
metadata | object | — |
name | string | — |
done | boolean | — |
{
"done": false,
"error": {},
"metadata": {},
"name": "",
"ok": false,
"response": {}
}Related Google Service Usage nodes
See Batch Enable run in a workflow.
In a technical demo we add the Google Service Usage connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.