Google Service Management
Google Service Management allows service producers to publish their services on Google Cloud Platform so that they can be discovered and used by servi (Google OAuth2).
OCNORA ships 8 typed Google Service Management 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 Management
- 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 Management
Operations, grouped by what they do to your data.
Create and send 3
Read and search 4
Delete and cancel 1
A sample Google Service Management workflow
- 1A core triggerStart the run from a chat, form, manual, schedule, webhook, workflow trigger — no Google Service Management trigger is needed.
- 2Get Configservice_management.get_configGets a service configuration (version) for a managed service.
- 3Create Configservice_management.create_configCreates a new service configuration (version) for a managed service.
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 8
- Create ConfigCreates a new service configuration (version) for a managed service.service_management.create_config
- Create ServiceCreates a new managed service.service_management.create_service
- Delete ServiceDeletes a managed service.service_management.delete_service
- Generate Config ReportGenerates and returns a report (errors, warnings and changes from existing configurations) associated with GenerateConfigReportRequest.new_value If…service_management.generate_config_report
- Get ConfigGets a service configuration (version) for a managed service.service_management.get_config
- Get ServiceGets a managed service. Authentication is required unless the service is public.service_management.get_service
- List ConfigsLists the history of the service configuration for a managed service, from the newest to the oldest.service_management.list_configs
- List ServicesLists managed services. Returns all public services. For authenticated users, also returns all services the calling user may get.service_management.list_services
Google Service Management questions
- How does OCNORA authenticate with Google Service Management?
- 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 Management?
- 8 typed operations, each with a reference page listing its config fields and the shapes it emits.
- What if the Google Service Management operation I need is not listed?
- Where Google Service Management 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 Management?
- Not yet. Start from a blank workflow, or describe the workflow to Build with AI.
- How are Google Service Management 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 Management 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.