Can HumDay connect to Google Dataform?

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

Do I need to write code to automate Google Dataform?

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 Dataform account.

What can HumDay do in Google Dataform?

22 of the 38 documented operations change something in Google Dataform, and 16 read from it. HumDay only ever uses the specific operations your approved contract needs.

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

Automate Google Dataform

HumDay reads Google Dataform’s own published API description and derives 38 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 HumDay can do in Google Dataform

22 documented operations change something in Google Dataform.

POSTMoves a file (inside a Workspace) to a new location./v1beta1/{workspace}:moveFile
POSTCreates a new Workspace in a given Repository./v1beta1/{parent}/workspaces
POSTCreates a new Repository in a given project and location./v1beta1/{parent}/repositories
POSTCreates a new ReleaseConfig in a given Repository./v1beta1/{parent}/releaseConfigs
POSTCreates a new WorkflowConfig in a given Repository./v1beta1/{parent}/workflowConfigs
POSTCreates a new CompilationResult in a given project and location./v1beta1/{parent}/compilationResults
POSTCreates a new WorkflowInvocation in a given Repository./v1beta1/{parent}/workflowInvocations
POSTPerforms a Git reset for uncommitted files in a Workspace./v1beta1/{name}:reset
POSTApplies a Git commit for uncommitted files in a Workspace./v1beta1/{name}:commit
POSTWrites to a file (inside a Workspace)./v1beta1/{workspace}:writeFile
POSTDeletes a file (inside a Workspace)./v1beta1/{workspace}:removeFile
POSTCreates a directory inside a Workspace./v1beta1/{workspace}:makeDirectory
POSTMoves a directory (inside a Workspace), and all of its contents, to a new location./v1beta1/{workspace}:moveDirectory
DELETEDeletes a single Workspace./v1beta1/{name}
PATCHUpdates a single WorkflowConfig./v1beta1/{name}
POSTPulls Git commits from the Repository's remote into a Workspace./v1beta1/{name}:pull
POSTPushes Git commits from a Workspace to the Repository's remote./v1beta1/{name}:push
POSTRequests cancellation of a running WorkflowInvocation./v1beta1/{name}:cancel
POSTSets the access control policy on the specified resource./v1beta1/{resource}:setIamPolicy
POSTDeletes a directory (inside a Workspace) and all of its contents./v1beta1/{workspace}:removeDirectory
POSTReturns permissions that a caller has on the specified resource./v1beta1/{resource}:testIamPermissions
POSTInstalls dependency NPM packages (inside a Workspace)./v1beta1/{workspace}:installNpmPackages

What HumDay can read from Google Dataform

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

GETReturns WorkflowInvocationActions in a given WorkflowInvocation./v1beta1/{name}:query
GETReturns the contents of a file (inside a Workspace)./v1beta1/{workspace}:readFile
GETFetches Git diff for an uncommitted file in a Workspace./v1beta1/{workspace}:fetchFileDiff
GETFetches Git statuses for the files in a Workspace./v1beta1/{name}:fetchFileGitStatuses
GETFetches a single Workspace./v1beta1/{name}
GETGets the access control policy for a resource./v1beta1/{resource}:getIamPolicy
GETFetches Git ahead/behind against a remote branch./v1beta1/{name}:fetchGitAheadBehind
GETFetches a Repository's remote branches./v1beta1/{name}:fetchRemoteBranches
GETReturns the contents of a given Workspace directory./v1beta1/{workspace}:queryDirectoryContents
GETLists information about the supported locations for this service./v1beta1/{name}/locations
GETLists Workspaces in a given Repository./v1beta1/{parent}/workspaces
GETLists Repositories in a given project and location./v1beta1/{parent}/repositories
GETLists ReleaseConfigs in a given Repository./v1beta1/{parent}/releaseConfigs
GETLists WorkflowConfigs in a given Repository./v1beta1/{parent}/workflowConfigs
GETLists CompilationResults in a given Repository./v1beta1/{parent}/compilationResults
GETLists WorkflowInvocations in a given Repository./v1beta1/{parent}/workflowInvocations

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