Google Service Usage
Enables services that service consumers want to use on Google Cloud Platform, lists the available or enabled services, or disables services that servi (Google OAuth2).
OCNORA ships 3 typed Google Service Usage 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 Usage
- 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 Usage
Operations, grouped by what they do to your data.
Read and search 2
Other operations 1
A sample Google Service Usage workflow
- 1A core triggerStart the run from a chat, form, manual, schedule, webhook, workflow trigger — no Google Service Usage trigger is needed.
- 2Get Serviceservice_usage.get_serviceReturns the service configuration and enabled state for a given service.
- 3Batch Enableservice_usage.batch_enableEnable multiple services on a project. The operation is atomic: if enabling any service fails, then the entire batch fails, and no state changes occur.
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 3
- Batch EnableEnable multiple services on a project. The operation is atomic: if enabling any service fails, then the entire batch fails, and no state changes occur.service_usage.batch_enable
- Get ServiceReturns the service configuration and enabled state for a given service.service_usage.get_service
- List ServicesList all services available to the specified project, and the current state of those services with respect to the project.service_usage.list_services
Google Service Usage questions
- How does OCNORA authenticate with Google Service Usage?
- 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 Usage?
- 3 typed operations, each with a reference page listing its config fields and the shapes it emits.
- What if the Google Service Usage operation I need is not listed?
- Where Google Service Usage 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 Usage?
- Not yet. Start from a blank workflow, or describe the workflow to Build with AI.
- How are Google Service Usage 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 Usage 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.