Google OS Config

Google CloudOAuth 2.0Connection test available

OS management tools that can be used for patch management, patch compliance, and configuration management on VM instances (Google OAuth2).

OCNORA ships 8 typed Google OS Config 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 OS Config

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

Operations, grouped by what they do to your data.

A sample Google OS Config workflow

  1. 1
    A core trigger
    Start the run from a chat, form, manual, schedule, webhook, workflow trigger — no Google OS Config trigger is needed.
  2. 2
    Get Patch Deploymentos_config.get_patch_deployment
    Get an OS Config patch deployment.
  3. 3
    Create Patch Deploymentos_config.create_patch_deployment
    Create an OS Config patch deployment.

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 OS Config questions

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