How does OCNORA authenticate with Google Data Lineage?

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 Data Lineage?

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

What if the Google Data Lineage operation I need is not listed?

Where Google Data Lineage 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 Data Lineage?

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

How are Google Data Lineage 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 Data Lineage

Google CloudOAuth 2.0Connection test available

Data Lineage (Google OAuth2).

OCNORA ships 10 typed Google Data Lineage 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 Data Lineage Google Data Lineage API docs ↗

Before you connect Google Data Lineage

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 Data Lineage

Operations, grouped by what they do to your data.

Create and send 2

Read and search 4

Update 2

Delete and cancel 2

A sample Google Data Lineage workflow

1
A core trigger
Start the run from a chat, form, manual, schedule, webhook, workflow trigger — no Google Data Lineage trigger is needed.
2
Get Processdata_lineage.get_process
Gets the details of the specified process.
3
Create Processdata_lineage.create_process
Creates a new process.

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