Google AI Commerce Search
The AI Commerce Search API is made up of Retail Search, Browse and Recommendations (Google OAuth2).
OCNORA ships 8 typed Google AI Commerce Search 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 AI Commerce Search
- 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 AI Commerce Search
Operations, grouped by what they do to your data.
Create and send 1
Read and search 4
Update 2
Delete and cancel 1
A sample Google AI Commerce Search workflow
- 1A core triggerStart the run from a chat, form, manual, schedule, webhook, workflow trigger — no Google AI Commerce Search trigger is needed.
- 2Get Productretail_search.get_productGets a Product.
- 3Create Productretail_search.create_productCreates a Product.
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 8
- Create ProductCreates a Product.retail_search.create_product
- Delete ProductDeletes a Product.retail_search.delete_product
- Get ProductGets a Product.retail_search.get_product
- List CatalogsLists all the Catalogs associated with the project.retail_search.list_catalogs
- List ProductsGets a list of Products.retail_search.list_products
- Search PlacementsPerforms a search. This feature is only available for users who have Retail Search enabled. Enable Retail Search on Cloud Console before using this feature.retail_search.search_placements
- Update CatalogUpdates the Catalogs.retail_search.update_catalog
- Update ProductUpdates a Product.retail_search.update_product
Google AI Commerce Search questions
- How does OCNORA authenticate with Google AI Commerce Search?
- 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 AI Commerce Search?
- 8 typed operations, each with a reference page listing its config fields and the shapes it emits.
- What if the Google AI Commerce Search operation I need is not listed?
- Where Google AI Commerce Search 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 AI Commerce Search?
- Not yet. Start from a blank workflow, or describe the workflow to Build with AI.
- How are Google AI Commerce Search 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 AI Commerce Search 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.