Google Service Directory
Service Directory is a platform for discovering, publishing, and connecting services (Google OAuth2).
OCNORA ships 10 typed Google Service Directory operations. Each node has a schema-driven form, input and output tables beside its settings, and is pre-flighted by Workflow Health before your first real run.
Before you connect Google Service Directory
- Authentication
- OAuth 2.0
- Credential
- {"client_id", "client_secret", "refresh_token"}
- Connection test
- Available: the stored credential can be checked against the provider when you add it. This is not a record that a test was run or passed.
What you can do with Google Service Directory
Operations, grouped by what they do to your data.
Create and send 2
Read and search 4
Update 2
Delete and cancel 2
A sample Google Service Directory workflow
- 1A core triggerStart the run from a chat, form, manual, schedule, webhook, workflow trigger — no Google Service Directory trigger is needed.
- 2Get Namespaceservice_directory.get_namespaceGets a namespace.
- 3Create Namespaceservice_directory.create_namespaceCreates a namespace, and returns the new namespace.
An outline built from this provider’s node contracts, not a recorded run. Each step’s output fields are available to the next in the field picker.
Every node below has a reference page: what it does, the connection it needs, its config fields with types, constraints and examples, and the shapes it emits.
Operations 10
- Create NamespaceCreates a namespace, and returns the new namespace.service_directory.create_namespace
- Create ServiceCreates a service, and returns the new service.service_directory.create_service
- Delete NamespaceDeletes a namespace.service_directory.delete_namespace
- Delete ServiceDeletes a service.service_directory.delete_service
- Get NamespaceGets a namespace.service_directory.get_namespace
- Get ServiceGets a service.service_directory.get_service
- List NamespacesLists all namespaces.service_directory.list_namespaces
- List ServicesLists all services belonging to a namespace.service_directory.list_services
- Update NamespaceUpdates a namespace.service_directory.update_namespace
- Update ServiceUpdates a service.service_directory.update_service
Google Service Directory questions
- How does OCNORA authenticate with Google Service Directory?
- With a stored OAuth 2.0 credential, shaped {"client_id", "client_secret", "refresh_token"}. A connection test can check it when you add it.
- What can I automate with Google Service Directory?
- 10 typed operations, each with a reference page listing its config fields and the shapes it emits.
- What if the Google Service Directory operation I need is not listed?
- Where Google Service Directory has an HTTP API, call it from the HTTP node with the same credential, or describe the step to the AI builder, which asks our team for a typed node when one is missing.
- Are there templates that use Google Service Directory?
- Not yet. Start from a blank workflow, or describe the workflow to Build with AI.
- How are Google Service Directory calls controlled?
- Every call and every run step is audited, runs count against the execution budget, and Workflow Health pre-flights the workflow when you save it.
See your first Google Service Directory workflow run.
Book a technical demo. We add the connection, pick a template or describe the workflow to Build with AI, and Workflow Health checks it before it runs.