Can HumDay connect to Google Cloud Dataplex?

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

Do I need to write code to automate Google Cloud Dataplex?

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 Cloud Dataplex account.

What can HumDay do in Google Cloud Dataplex?

20 of the 40 documented operations change something in Google Cloud Dataplex, and 20 read from it. HumDay only ever uses the specific operations your approved contract needs.

Is my Google Cloud Dataplex 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 Cloud Dataplex is held behind that approval.

Automate Google Cloud Dataplex

HumDay reads Google Cloud Dataplex’s own published API description and derives 40 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 Cloud Dataplex is

Dataplex API is used to manage the lifecycle of data lakes.

API host: dataplex.googleapis.com

What HumDay can do in Google Cloud Dataplex

20 documented operations change something in Google Cloud Dataplex.

POSTCreates a task resource within a lake./v1/{parent}/tasks
POSTRun an on demand execution of a Task./v1/{name}:run
POSTCreates a lake resource./v1/{parent}/lakes
POSTCreates a zone resource within a lake./v1/{parent}/zones
POSTCreates an asset resource./v1/{parent}/assets
POSTCreate a content./v1/{parent}/content
POSTCreate a metadata entity./v1/{parent}/entities
POSTCreates a DataScan resource./v1/{parent}/dataScans
POSTCreate a DataAttribute resource./v1/{parent}/attributes
POSTCreate a metadata partition./v1/{parent}/partitions
POSTCreate a content./v1/{parent}/contentitems
POSTCreate an environment resource./v1/{parent}/environments
POSTCreate a DataTaxonomy resource./v1/{parent}/dataTaxonomies
POSTCreate a DataAttributeBinding resource./v1/{parent}/dataAttributeBindings
DELETEDeletes a long-running operation./v1/{name}
PATCHUpdates an asset resource./v1/{name}
PUTUpdate a metadata entity./v1/{name}
POSTStarts asynchronous cancellation on a long-running operation./v1/{name}:cancel
POSTSets the access control policy on the specified resource./v1/{resource}:setIamPolicy
POSTReturns permissions that a caller has on the specified resource./v1/{resource}:testIamPermissions

What HumDay can read from Google Cloud Dataplex

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

GETLists Jobs under the given task./v1/{parent}/jobs
GETLists tasks under the given lake./v1/{parent}/tasks
GETList content./v1/{parent}/content
GETList metadata entities in a zone./v1/{parent}/entities
GETList metadata partitions of an entity./v1/{parent}/partitions
GETList content./v1/{parent}/contentitems
GETGets the latest state of a long-running operation./v1/{name}
GETGets the access control policy for a resource./v1/{resource}:getIamPolicy
GETLists lake resources in a project and location./v1/{parent}/lakes
GETLists zone resources in a lake./v1/{parent}/zones
GETLists asset resources in a zone./v1/{parent}/assets
GETLists information about the supported locations for this service./v1/{name}/locations
GETLists action resources in an asset./v1/{parent}/actions
GETLists operations that match the specified filter in the request./v1/{name}/operations
GETLists session resources in an environment./v1/{parent}/sessions
GETLists DataScans./v1/{parent}/dataScans
GETLists Data Attribute resources in a DataTaxonomy./v1/{parent}/attributes
GETLists environments under the given lake./v1/{parent}/environments
GETLists DataTaxonomy resources in a project and location./v1/{parent}/dataTaxonomies
GETLists DataAttributeBinding resources in a project and location./v1/{parent}/dataAttributeBindings

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