Google Cloud OS Login

Google CloudOAuth 2.0Connection test available

You can use OS Login to manage access to your VM instances using IAM roles (Google OAuth2).

OCNORA ships 6 typed Google Cloud OS Login 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 OS Login

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 OS Login

Operations, grouped by what they do to your data.

A sample Google Cloud OS Login workflow

  1. 1
    A core trigger
    Start the run from a chat, form, manual, schedule, webhook, workflow trigger — no Google Cloud OS Login trigger is needed.
  2. 2
    Get Login Profileos_login.get_login_profile
    Retrieves the profile information used for logging in to a virtual machine on Google Compute Engine.
  3. 3
    Create Ssh Public Keyos_login.create_ssh_public_key
    Create an SSH public key…

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.

Google Cloud OS Login questions

How does OCNORA authenticate with Google Cloud OS Login?
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 OS Login?
6 typed operations, each with a reference page listing its config fields and the shapes it emits.
What if the Google Cloud OS Login operation I need is not listed?
Where Google Cloud OS Login 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 OS Login?
Not yet. Start from a blank workflow, or describe the workflow to Build with AI.
How are Google Cloud OS Login 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 OS Login 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.