Can HumDay connect to Google Cloud Data Fusion?

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

Do I need to write code to automate Google Cloud Data Fusion?

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 Data Fusion account.

What can HumDay do in Google Cloud Data Fusion?

10 of the 18 documented operations change something in Google Cloud Data Fusion, and 8 read from it. HumDay only ever uses the specific operations your approved contract needs.

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

Automate Google Cloud Data Fusion

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

Cloud Data Fusion is a fully-managed, cloud native, enterprise data integration service for quickly building and managing data pipelines. It provides a graphical interface to increase time efficiency and reduce complexity, and allows business users, developers, and data scientists to easily and reliably build scalable data integration solutions to cleanse, prepare, blend, transfer and transform da

API host: datafusion.googleapis.com

What HumDay can do in Google Cloud Data Fusion

10 documented operations change something in Google Cloud Data Fusion.

POSTCreates a new Data Fusion instance in the specified project and location./v1beta1/{parent}/instances
POSTCreates DNS peering on the given resource./v1beta1/{parent}/dnsPeerings
DELETEDeletes a long-running operation./v1beta1/{name}
PATCHUpdates a single Data Fusion instance./v1beta1/{name}
POSTStarts asynchronous cancellation on a long-running operation./v1beta1/{name}:cancel
POSTRestart a single Data Fusion instance./v1beta1/{name}:restart
POSTUpgrade a single Data Fusion instance./v1beta1/{name}:upgrade
POSTSets the access control policy on the specified resource./v1beta1/{resource}:setIamPolicy
POSTReturns permissions that a caller has on the specified resource./v1beta1/{resource}:testIamPermissions
POSTRemove IAM policy that is currently set on the given resource./v1beta1/{resource}:removeIamPolicy

What HumDay can read from Google Cloud Data Fusion

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

GETList namespaces in a given instance/v1beta1/{parent}/namespaces
GETGets the latest state of a long-running operation./v1beta1/{name}
GETGets the access control policy for a resource./v1beta1/{resource}:getIamPolicy
GETLists information about the supported locations for this service./v1beta1/{name}/locations
GETLists operations that match the specified filter in the request./v1beta1/{name}/operations
GETLists possible versions for Data Fusion instances in the specified project and location./v1beta1/{parent}/versions
GETLists Data Fusion instances in the specified project and location./v1beta1/{parent}/instances
GETLists DNS peerings for a given resource./v1beta1/{parent}/dnsPeerings

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