Google Recommender
Google CloudOAuth 2.0Connection test available
Recommender (Google OAuth2).
OCNORA ships 5 typed Google Recommender 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.
Before you connect Google Recommender
- 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 Recommender
Operations, grouped by what they do to your data.
Read and search 4
Update 1
A sample Google Recommender workflow
- 1A core triggerStart the run from a chat, form, manual, schedule, webhook, workflow trigger — no Google Recommender trigger is needed.
- 2Get Insightrecommender.get_insightGets the requested insight.
- 3Mark Claimedrecommender.mark_claimedMarks the Recommendation State as Claimed. Users can use this method to indicate to the Recommender API that they are starting to apply the recommendation themselves.
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
- Get InsightGets the requested insight.recommender.get_insight
- Get RecommendationGets the requested recommendation. Requires the recommender.*.get IAM permission for the specified recommender.recommender.get_recommendation
- List InsightsLists insights for the specified Cloud Resource. Requires the recommender.*.list IAM permission for the specified insight type.recommender.list_insights
- List RecommendationsLists recommendations for the specified Cloud Resource. Requires the recommender.*.list IAM permission for the specified recommender.recommender.list_recommendations
- Mark ClaimedMarks the Recommendation State as Claimed. Users can use this method to indicate to the Recommender API that they are starting to apply the recommendation themselves.recommender.mark_claimed
Google Recommender questions
- How does OCNORA authenticate with Google Recommender?
- 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 Recommender?
- 5 typed operations, each with a reference page listing its config fields and the shapes it emits.
- What if the Google Recommender operation I need is not listed?
- Where Google Recommender 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 Recommender?
- Not yet. Start from a blank workflow, or describe the workflow to Build with AI.
- How are Google Recommender 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.
See your first Google Recommender workflow run.
Book a technical demo. We add the connection, pick a template or describe the workflow to Build with AI, and Workflow Health checks it before it runs.