How does OCNORA authenticate with Google Looker (Google Cloud core)?

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 Looker (Google Cloud core)?

10 typed operations, each with a reference page listing its config fields and the shapes it emits.

What if the Google Looker (Google Cloud core) operation I need is not listed?

Where Google Looker (Google Cloud core) 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 Looker (Google Cloud core)?

Not yet. Start from a blank workflow, or describe the workflow to Build with AI.

How are Google Looker (Google Cloud core) 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.

Google Looker (Google Cloud core)

Google CloudOAuth 2.0Connection test available

Looker (Google Cloud core) (Google OAuth2).

OCNORA ships 10 typed Google Looker (Google Cloud core) 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.

Ask about Google Looker (Google Cloud core)Google Looker (Google Cloud core) API docs ↗

Before you connect Google Looker (Google Cloud core)

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 Looker (Google Cloud core)

Operations, grouped by what they do to your data.

Create and send 2

Read and search 5

Update 1

Update Instance

Delete and cancel 2

A sample Google Looker (Google Cloud core) workflow

1
A core trigger
Start the run from a chat, form, manual, schedule, webhook, workflow trigger — no Google Looker (Google Cloud core) trigger is needed.
2
Export Instancelooker.export_instance
Export instance.
3
Create Backuplooker.create_backup
Backup Looker 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 10