Google Cloud DNS

Google CloudOAuth 2.0Connection test available

Manage Cloud DNS zones and record sets (Google OAuth2).

OCNORA ships 39 typed Google Cloud DNS 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 DNS

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.

A sample Google Cloud DNS workflow

  1. 1
    A core trigger
    Start the run from a chat, form, manual, schedule, webhook, workflow trigger — no Google Cloud DNS trigger is needed.
  2. 2
    Get Changecloud_dns.get_change
    Fetches the representation of an existing Change.
  3. 3
    Create Managed Zonecloud_dns.create_managed_zone
    Creates a new ManagedZone.

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 39

Google Cloud DNS questions

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