Can HumDay connect to Google Recommendations AI (Beta)?

Yes. HumDay reads Google Recommendations AI (Beta)'s own published API description and derives the operations from it, so there is no hand-built connector to wait for. 17 operations are documented.

Do I need to write code to automate Google Recommendations AI (Beta)?

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 Recommendations AI (Beta) account.

What can HumDay do in Google Recommendations AI (Beta)?

10 of the 17 documented operations change something in Google Recommendations AI (Beta), and 7 read from it. HumDay only ever uses the specific operations your approved contract needs.

Is my Google Recommendations AI (Beta) 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 Recommendations AI (Beta) is held behind that approval.

Automate Google Recommendations AI (Beta)

HumDay reads Google Recommendations AI (Beta)’s own published API description and derives 17 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 Recommendations AI (Beta) is

Note that we now highly recommend new customers to use Retail API, which incorporates the GA version of the Recommendations AI funtionalities. To enable Retail API, please visit https://console.cloud.google.com/apis/library/retail.googleapis.com. The Recommendations AI service enables customers to build end-to-end personalized recommendation systems without requiring a high level of expertise in m

API host: recommendationengine.googleapis.com

What HumDay can do in Google Recommendations AI (Beta)

10 documented operations change something in Google Recommendations AI (Beta).

POSTCreates a catalog item./v1beta1/{parent}/catalogItems
POSTDeletes permanently all user events specified by the filter provided./v1beta1/{parent}/userEvents:purge
POSTWrites a single user event./v1beta1/{parent}/userEvents:write
POSTBulk import of User events./v1beta1/{parent}/userEvents:import
POSTTriggers a user event rejoin operation with latest catalog data./v1beta1/{parent}/userEvents:rejoin
PATCHUpdates a catalog item./v1beta1/{name}
POSTBulk import of multiple catalog items./v1beta1/{parent}/catalogItems:import
DELETEUnregister an apiKey from using for predict method./v1beta1/{name}
POSTMakes a recommendation prediction./v1beta1/{name}:predict
POSTRegister an API key for use with predict method./v1beta1/{parent}/predictionApiKeyRegistrations

What HumDay can read from Google Recommendations AI (Beta)

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

GETGets a list of user events within a time range, with potential filtering./v1beta1/{parent}/userEvents
GETGets a list of catalog items./v1beta1/{parent}/catalogItems
GETWrites a single user event from the browser./v1beta1/{parent}/userEvents:collect
GETList the registered apiKeys for use with predict method./v1beta1/{parent}/predictionApiKeyRegistrations
GETGets the latest state of a long-running operation./v1beta1/{name}
GETLists operations that match the specified filter in the request./v1beta1/{name}/operations
GETLists all the catalog configurations associated with the project./v1beta1/{parent}/catalogs

How automating Google Recommendations AI (Beta) 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 Recommendations AI (Beta) account.
Grant access, then go live. You approve the specific Google Recommendations AI (Beta) operations it may use — and only those.