Can HumDay connect to Google Storage Transfer?

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

Do I need to write code to automate Google Storage Transfer?

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 Storage Transfer account.

What can HumDay do in Google Storage Transfer?

10 of the 15 documented operations change something in Google Storage Transfer, and 5 read from it. HumDay only ever uses the specific operations your approved contract needs.

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

Automate Google Storage Transfer

HumDay reads Google Storage Transfer’s own published API description and derives 15 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 Storage Transfer is

Transfers data from external data sources to a Google Cloud Storage bucket or between Google Cloud Storage buckets.

API host: storagetransfer.googleapis.com

What HumDay can do in Google Storage Transfer

10 documented operations change something in Google Storage Transfer.

POSTCreates a transfer job that runs periodically./v1/transferJobs
POSTStarts a new operation for the specified transfer job./v1/{jobName}:run
DELETEDeletes an agent pool./v1/{name}
PATCHUpdates an existing agent pool resource./v1/{name}
DELETEDeletes a transfer job./v1/{jobName}
PATCHUpdates a transfer job./v1/{jobName}
POSTCreates an agent pool resource./v1/projects/{projectId}/agentPools
POSTPauses a transfer operation./v1/{name}:pause
POSTCancels a transfer. Use the transferOperations.get method to check if the cancellation succeeded or if the operation completed despite the cancel request. When you cancel an opera…/v1/{name}:cancel
POSTResumes a transfer operation that is paused./v1/{name}:resume

What HumDay can read from Google Storage Transfer

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

GETLists transfer jobs./v1/transferJobs
GETLists transfer operations./v1/{name}
GETGets a transfer job./v1/{jobName}
GETReturns the Google service account that is used by Storage Transfer Service to access buckets in the project where transfers run or in other projects./v1/googleServiceAccounts/{projectId}
GETLists agent pools./v1/projects/{projectId}/agentPools

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