Search Placements

retail_search.search_placements
ActionGoogle Cloudconnection required

Calls AI Commerce Search POST /v2/projects/{projectsId}/locations/{locationsId}/catalogs/{catalogsId}/placements/{placementsId}:search.

Performs a search. This feature is only available for users who have Retail Search enabled. Enable Retail Search on Cloud Console before using this feature.

Connection

Required
Yes — the node will not save without one
Auth type
OAuth 2.0
Providers
Google AI Commerce Search
Secret shape
{"client_id", "client_secret", "refresh_token"}
Config it needs
location, project_id
Resolved by
config.connection_id, else node.connection_id

Configuration

5 fields, 2 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.

FieldTypeRequiredDefaultConstraintsExample
project_id
GCP project id (overrides connection).
stringNo———
location
Location / region (overrides connection).
stringNo———
catalog
Id of the catalog to act on, from retail_search.list_catalogs — not its name.
stringYes———
placement
Placement id.
stringYes———
body
Request body (GoogleCloudRetailV2SearchRequest) as JSON.
objectNo———

Output

One shape.

result

FieldTypeExample
ok
boolean—
redirectUri
string—
facets
array—
totalSize
number—
queryExpansionInfo
object—
appliedControls
array—
conversationalSearchResult
object—
{
  "appliedControls": [],
  "conversationalSearchResult": {},
  "facets": [],
  "ok": false,
  "queryExpansionInfo": {},
  "redirectUri": "",
  "totalSize": 0
}

See Search Placements run in a workflow.

In a technical demo we add the Google AI Commerce Search connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.