Automate Google Directory
HumDay reads Google Directory’s own published API description and derives 14 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 Directory is
Service Directory is a platform for discovering, publishing, and connecting services.
API host: servicedirectory.googleapis.com
What HumDay can do in Google Directory
9 documented operations change something in Google Directory.
- POSTCreates a service, and returns the new service.
/v1beta1/{parent}/services - POSTCreates an endpoint, and returns the new endpoint.
/v1beta1/{parent}/endpoints - POSTCreates a namespace, and returns the new namespace.
/v1beta1/{parent}/namespaces - DELETEDeletes an endpoint.
/v1beta1/{name} - PATCHUpdates an endpoint.
/v1beta1/{name} - POSTReturns a service and its associated endpoints.
/v1beta1/{name}:resolve - POSTGets the IAM Policy for a resource
/v1beta1/{resource}:getIamPolicy - POSTSets the IAM Policy for a resource
/v1beta1/{resource}:setIamPolicy - POSTTests IAM permissions for a resource (namespace, service or service workload only).
/v1beta1/{resource}:testIamPermissions
What HumDay can read from Google Directory
These are the operations a schedule or a trigger can watch.
- GETGets an endpoint.
/v1beta1/{name} - GETLists information about the supported locations for this service.
/v1beta1/{name}/locations - GETLists all services belonging to a namespace.
/v1beta1/{parent}/services - GETLists all endpoints.
/v1beta1/{parent}/endpoints - GETLists all namespaces.
/v1beta1/{parent}/namespaces
How automating Google Directory 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 Directory account.
- Grant access, then go live. You approve the specific Google Directory operations it may use — and only those.
Automate Google Directory 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 Directory automation
- Can HumDay connect to Google Directory?
- Yes. HumDay reads Google Directory's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 14 operations are documented.
- Do I need to write code to automate Google Directory?
- 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 Directory account.
- What can HumDay do in Google Directory?
- 9 of the 14 documented operations change something in Google Directory, and 5 read from it. HumDay only ever uses the specific operations your approved contract needs.
- Is my Google Directory 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 Directory is held behind that approval.
Where this came from
The operations above are read from a published API description for Google Directory at servicedirectory.googleapis.com/$discovery/rest?version=v1beta1. Descriptions are the provider’s own words, not ours. Last published 2023-04-21.