How does OCNORA authenticate with Google Secure Source Manager?

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 Secure Source Manager?

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

What if the Google Secure Source Manager operation I need is not listed?

Where Google Secure Source Manager 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 Secure Source Manager?

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

How are Google Secure Source Manager 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 Secure Source Manager

Google CloudOAuth 2.0Connection test available

Regionally deployed, single-tenant managed source code repository hosted on Google Cloud (Google OAuth2).

OCNORA ships 9 typed Google Secure Source Manager 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 Secure Source Manager Google Secure Source Manager API docs ↗

Before you connect Google Secure Source Manager

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 Secure Source Manager

Operations, grouped by what they do to your data.

Create and send 2

Read and search 4

Update 1

Update Repository

Delete and cancel 2

A sample Google Secure Source Manager workflow

1
A core trigger
Start the run from a chat, form, manual, schedule, webhook, workflow trigger — no Google Secure Source Manager trigger is needed.
2
Get Instancesecure_source_manager.get_instance
Gets details of a single instance.
3
Create Instancesecure_source_manager.create_instance
Creates a new instance in a given project and location.

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 9