Create Namespace
service_directory.create_namespace
ActionGoogle Cloudconnection required
Calls servicedirectory v1 POST /v1/projects/{projectsId}/locations/{locationsId}/namespaces.
Creates a namespace, and returns the new namespace.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- OAuth 2.0
- Providers
- Google Service Directory
- 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.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
location Location or region; taken from the connection when unset. | string | No | — | — | — |
body The Namespace resource, as the API defines it. | object | Yes | — | — | — |
namespace_id The Resource ID must be 1-63 characters long, and comply with RFC1035. Required. | string | Yes | — | — | — |
Output
One shape.
result
Extra keys beyond the ones listed can appear.
| Field | Type | Example |
|---|---|---|
labels | object | — |
name | string | — |
uid | string | — |
{
"labels": {},
"name": "",
"uid": ""
}Related Google Service Directory nodes
See Create Namespace run in a workflow.
In a technical demo we add the Google Service Directory connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.