Google Service Control
Provides admission control and telemetry reporting for services integrated with Service Infrastructure (Google OAuth2).
OCNORA ships 2 typed Google Service Control 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 Control
- 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 Control
Operations, grouped by what they do to your data.
Read and search 1
Other operations 1
A sample Google Service Control workflow
- 1A core triggerStart the run from a chat, form, manual, schedule, webhook, workflow trigger — no Google Service Control trigger is needed.
- 2Check Serviceservice_control.check_serviceThis method provides admission control for services that are integrated with [Service Infrastructure](https://cloud.google.com/service-infrastructure).
- 3Report Serviceservice_control.report_serviceThis method provides telemetry reporting for services that are integrated with [Service Infrastructure](https://cloud.google.com/service-infrastructure).
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 2
- Check ServiceThis method provides admission control for services that are integrated with [Service Infrastructure](https://cloud.google.com/service-infrastructure).service_control.check_service
- Report ServiceThis method provides telemetry reporting for services that are integrated with [Service Infrastructure](https://cloud.google.com/service-infrastructure).service_control.report_service
Google Service Control questions
- How does OCNORA authenticate with Google Service Control?
- 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 Control?
- 2 typed operations, each with a reference page listing its config fields and the shapes it emits.
- What if the Google Service Control operation I need is not listed?
- Where Google Service Control 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 Control?
- Not yet. Start from a blank workflow, or describe the workflow to Build with AI.
- How are Google Service Control 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 Control 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.