How does OCNORA authenticate with Google Serverless VPC Access?

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 Serverless VPC Access?

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

What if the Google Serverless VPC Access operation I need is not listed?

Where Google Serverless VPC Access 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 Serverless VPC Access?

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

How are Google Serverless VPC Access 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 Serverless VPC Access

Google CloudOAuth 2.0Connection test available

API for managing VPC access connectors (Google OAuth2).

OCNORA ships 5 typed Google Serverless VPC Access 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 Serverless VPC Access Google Serverless VPC Access API docs ↗

Before you connect Google Serverless VPC Access

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 Serverless VPC Access

Operations, grouped by what they do to your data.

Create and send 1

Create Connector

Read and search 2

Update 1

Update Connector

Delete and cancel 1

Delete Connector

A sample Google Serverless VPC Access workflow

1
A core trigger
Start the run from a chat, form, manual, schedule, webhook, workflow trigger — no Google Serverless VPC Access trigger is needed.
2
Get Connectorvpc_access.get_connector
Gets a Serverless VPC Access connector. Returns NOT_FOUND if the resource does not exist.
3
Create Connectorvpc_access.create_connector
Creates a Serverless VPC Access connector, returns an operation.

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 5