How does OCNORA authenticate with Google Cloud Talent Solution?

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 Talent Solution?

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

What if the Google Cloud Talent Solution operation I need is not listed?

Where Google Cloud Talent Solution 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 Talent Solution?

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

How are Google Cloud Talent Solution 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 Cloud Talent Solution

Google CloudOAuth 2.0Connection test available

Cloud Talent Solution provides the capability to create, read, update, and delete job postings, as well as search jobs based on keywords and filters (Google OAuth2).

OCNORA ships 11 typed Google Cloud Talent Solution 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 Cloud Talent Solution Google Cloud Talent Solution API docs ↗

Before you connect Google Cloud Talent Solution

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 Cloud Talent Solution

Operations, grouped by what they do to your data.

Create and send 2

Read and search 5

Update 2

Delete and cancel 2

A sample Google Cloud Talent Solution workflow

1
A core trigger
Start the run from a chat, form, manual, schedule, webhook, workflow trigger — no Google Cloud Talent Solution trigger is needed.
2
Get Jobcloud_talent.get_job
Retrieves the specified job, whose status is OPEN or recently EXPIRED within the last 90 days.
3
Create Jobcloud_talent.create_job
Creates a new job.

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 11