Can HumDay connect to Google Retail?

Yes. HumDay reads Google Retail's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 42 operations are documented.

Do I need to write code to automate Google Retail?

No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a test run before anything touches your Google Retail account.

What can HumDay do in Google Retail?

31 of the 42 documented operations change something in Google Retail, and 11 read from it. HumDay only ever uses the specific operations your approved contract needs.

Is my Google Retail account safe?

Your credentials are stored encrypted and are never shown in chat, code, or logs. Every run is limited to the operations you explicitly approved, and anything that writes to Google Retail is held behind that approval.

Automate Google Retail

HumDay reads Google Retail’s own published API description and derives 42 operations from it. Describe the outcome you want in plain words — you get a program that is written, proven on real data, and run for you.

What Google Retail is

Cloud Retail service enables customers to build end-to-end personalized recommendation systems without requiring a high level of expertise in machine learning, recommendation system, or Google Cloud.

API host: retail.googleapis.com

What HumDay can do in Google Retail

31 documented operations change something in Google Retail.

POSTPerforms a search. This feature is only available for users who have Retail Search enabled. Enable Retail Search on Cloud Console before using this feature./v2alpha/{placement}:search
POSTCreates a new model./v2alpha/{parent}/models
POSTCreates a Control. If the Control to create already exists, an ALREADYEXISTS error is returned./v2alpha/{parent}/controls
POSTDeletes permanently all user events specified by the filter provided./v2alpha/{parent}/userEvents:purge
POSTWrites a single user event./v2alpha/{parent}/userEvents:write
POSTBulk import of User events./v2alpha/{parent}/userEvents:import
POSTStarts a user-event rejoin operation with latest product catalog./v2alpha/{parent}/userEvents:rejoin
POSTCreates a MerchantCenterAccountLink./v2alpha/{name}
POSTUpdates local inventory information for a Product at a list of places, while respecting the last update timestamps of each inventory field./v2alpha/{product}:addLocalInventories
POSTRemove local inventory information for a Product at a list of places at a removal timestamp./v2alpha/{product}:removeLocalInventories
POSTCreates a Product./v2alpha/{parent}/products
POSTAdds the specified CatalogAttribute to the AttributesConfig./v2alpha/{attributesConfig}:addCatalogAttribute
POSTCreates a ServingConfig./v2alpha/{parent}/servingConfigs
DELETEDeletes a ServingConfig./v2alpha/{name}
PATCHUpdates a ServingConfig./v2alpha/{name}
POSTTunes an existing model./v2alpha/{name}:tune
POSTPauses the training of an existing model./v2alpha/{name}:pause
POSTResumes the training of an existing model./v2alpha/{name}:resume
POSTUpdates inventory information for a Product while respecting the last update timestamps of each inventory field./v2alpha/{name}:setInventory
POSTMakes a recommendation prediction./v2alpha/{placement}:predict
POSTSet a specified branch id as default branch./v2alpha/{catalog}:setDefaultBranch
POSTEnables a Control on the specified ServingConfig./v2alpha/{servingConfig}:addControl
POSTDisables a Control on the specified ServingConfig./v2alpha/{servingConfig}:removeControl
POSTIt is recommended to use the ProductService.AddLocalInventories method instead of ProductService.AddFulfillmentPlaces./v2alpha/{product}:addFulfillmentPlaces
POSTIt is recommended to use the ProductService.RemoveLocalInventories method instead of ProductService.RemoveFulfillmentPlaces./v2alpha/{product}:removeFulfillmentPlaces
POSTRemoves the specified CatalogAttribute from the AttributesConfig./v2alpha/{attributesConfig}:removeCatalogAttribute
POSTReplaces the specified CatalogAttribute in the AttributesConfig by updating the catalog attribute with the same CatalogAttribute.key./v2alpha/{attributesConfig}:replaceCatalogAttribute
POSTPermanently deletes all selected Products under a branch./v2alpha/{parent}/products:purge
POSTBulk import of multiple Products./v2alpha/{parent}/products:import
POSTRemoves all specified CatalogAttributes from the AttributesConfig./v2alpha/{attributesConfig}:batchRemoveCatalogAttributes
POSTBulk import of processed completion dataset./v2alpha/{parent}/completionData:import

What HumDay can read from Google Retail

These are the operations a schedule or a trigger can watch.

GETWrites a single user event from the browser./v2alpha/{parent}/userEvents:collect
GETLists all the models linked to this event store./v2alpha/{parent}/models
GETGets a list of Products./v2alpha/{parent}/products
GETGets the latest state of a long-running operation./v2alpha/{name}
GETCompletes the specified prefix with keyword suggestions./v2alpha/{catalog}:completeQuery
GETGet which branch is currently default branch set by CatalogService.SetDefaultBranch method under a specified parent catalog./v2alpha/{catalog}:getDefaultBranch
GETLists operations that match the specified filter in the request./v2alpha/{name}/operations
GETLists all the Catalogs associated with the project./v2alpha/{parent}/catalogs
GETLists all Controls by their parent Catalog./v2alpha/{parent}/controls
GETLists all ServingConfigs linked to this catalog./v2alpha/{parent}/servingConfigs
GETLists all MerchantCenterAccountLinks under the specified parent Catalog./v2alpha/{parent}/merchantCenterAccountLinks

How automating Google Retail works

Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
Approve the contract. HumDay writes down exactly what it will do, what it will touch, and what it will never do. You approve it before anything is built.
See it proven. The program runs and shows you the result before it is allowed near your live Google Retail account.
Grant access, then go live. You approve the specific Google Retail operations it may use — and only those.