Google Cloud Support
Manages Google Cloud technical support cases for Customer Care support offerings (Google OAuth2).
OCNORA ships 8 typed Google Cloud Support 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 Cloud Support
- 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 Cloud Support
Operations, grouped by what they do to your data.
Create and send 2
Read and search 5
Update 1
A sample Google Cloud Support workflow
- 1A core triggerStart the run from a chat, form, manual, schedule, webhook, workflow trigger — no Google Cloud Support trigger is needed.
- 2Get Casecloud_support.get_caseRetrieve a case.
- 3Create Casecloud_support.create_caseCreate a new case and associate it with a parent.
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 CaseCreate a new case and associate it with a parent.cloud_support.create_case
- Create CommentAdd a new comment to a case.cloud_support.create_comment
- Get CaseRetrieve a case.cloud_support.get_case
- Get CommentRetrieve a comment.cloud_support.get_comment
- List CasesRetrieve all cases under a parent, but not its children.cloud_support.list_cases
- List CommentsList all the comments associated with a case.cloud_support.list_comments
- Search CasesSearch for cases using a query.cloud_support.search_cases
- Update CaseUpdate a case.cloud_support.update_case
Google Cloud Support questions
- How does OCNORA authenticate with Google Cloud Support?
- 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 Cloud Support?
- 8 typed operations, each with a reference page listing its config fields and the shapes it emits.
- What if the Google Cloud Support operation I need is not listed?
- Where Google Cloud Support 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 Cloud Support?
- Not yet. Start from a blank workflow, or describe the workflow to Build with AI.
- How are Google Cloud Support 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 Cloud Support 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.