Google Bare Metal Solution
Provides ways to manage Bare Metal Solution hardware installed in a regional extension located near a Google Cloud data center (Google OAuth2).
OCNORA ships 7 typed Google Bare Metal Solution 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 Bare Metal Solution
- 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 Bare Metal Solution
Operations, grouped by what they do to your data.
Read and search 4
Update 2
Other operations 1
A sample Google Bare Metal Solution workflow
- 1A core triggerStart the run from a chat, form, manual, schedule, webhook, workflow trigger — no Google Bare Metal Solution trigger is needed.
- 2Get Instancebare_metal_solution.get_instanceGet details about a single server.
- 3Detach Lunbare_metal_solution.detach_lunDetach LUN from Instance.
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 7
- Detach LunDetach LUN from Instance.bare_metal_solution.detach_lun
- Get InstanceGet details about a single server.bare_metal_solution.get_instance
- Get VolumeGet details of a single storage volume.bare_metal_solution.get_volume
- List InstancesList servers in a given project and location.bare_metal_solution.list_instances
- List VolumesList storage volumes in a given project and location.bare_metal_solution.list_volumes
- Update InstanceUpdate details of a single server.bare_metal_solution.update_instance
- Update VolumeUpdate details of a single storage volume.bare_metal_solution.update_volume
Google Bare Metal Solution questions
- How does OCNORA authenticate with Google Bare Metal Solution?
- 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 Bare Metal Solution?
- 7 typed operations, each with a reference page listing its config fields and the shapes it emits.
- What if the Google Bare Metal Solution operation I need is not listed?
- Where Google Bare Metal Solution 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 Bare Metal Solution?
- Not yet. Start from a blank workflow, or describe the workflow to Build with AI.
- How are Google Bare Metal Solution 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 Bare Metal Solution 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.