Automate Google Discovery Engine
HumDay reads Google Discovery Engine’s own published API description and derives 11 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 Discovery Engine is
Discovery Engine API.
API host: discoveryengine.googleapis.com
What HumDay can do in Google Discovery Engine
7 documented operations change something in Google Discovery Engine.
- POSTMakes a recommendation, which requires a contextual user event.
/v1beta/{servingConfig}:recommend - POSTCreates a Document.
/v1beta/{parent}/documents - POSTWrites a single user event.
/v1beta/{parent}/userEvents:write - POSTBulk import of User events.
/v1beta/{parent}/userEvents:import - DELETEDeletes a Document.
/v1beta/{name} - PATCHUpdates a Document.
/v1beta/{name} - POSTBulk import of multiple Documents.
/v1beta/{parent}/documents:import
What HumDay can read from Google Discovery Engine
These are the operations a schedule or a trigger can watch.
- GETWrites a single user event from the browser.
/v1beta/{parent}/userEvents:collect - GETGets a list of Documents.
/v1beta/{parent}/documents - GETGets the latest state of a long-running operation.
/v1beta/{name} - GETLists operations that match the specified filter in the request.
/v1beta/{name}/operations
How automating Google Discovery Engine 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 Discovery Engine account.
- Grant access, then go live. You approve the specific Google Discovery Engine operations it may use — and only those.
Automate Google Discovery Engine with these
- Gmail79 operations
- Google+9 operations
- Google Abusive Experience Report2 operations
- Google Accelerated Mobile Pages (AMP) URL1 operations
- Google Access Approval7 operations
- Google Access Context Manager9 operations
- Google ACME DNS2 operations
- Google Ad Exchange Buyer38 operations
- Google Ad Exchange Buyer II50 operations
- Google Ad Experience Report2 operations
- Google Admin SDK122 operations
- Google AdMob7 operations
Categories
Questions about Google Discovery Engine automation
- Can HumDay connect to Google Discovery Engine?
- Yes. HumDay reads Google Discovery Engine's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 11 operations are documented.
- Do I need to write code to automate Google Discovery Engine?
- 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 Discovery Engine account.
- What can HumDay do in Google Discovery Engine?
- 7 of the 11 documented operations change something in Google Discovery Engine, and 4 read from it. HumDay only ever uses the specific operations your approved contract needs.
- Is my Google Discovery Engine 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 Discovery Engine is held behind that approval.
Where this came from
The operations above are read from a published API description for Google Discovery Engine at discoveryengine.googleapis.com/$discovery/rest?version=v1beta. Descriptions are the provider’s own words, not ours. Last published 2023-04-13.