Can HumDay connect to Google Cloud Source Repositories?

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

Do I need to write code to automate Google Cloud Source Repositories?

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 Source Repositories account.

What can HumDay do in Google Cloud Source Repositories?

7 of the 11 documented operations change something in Google Cloud Source Repositories, and 4 read from it. HumDay only ever uses the specific operations your approved contract needs.

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

Automate Google Cloud Source Repositories

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

Accesses source code repositories hosted by Google.

API host: sourcerepo.googleapis.com

What HumDay can do in Google Cloud Source Repositories

7 documented operations change something in Google Cloud Source Repositories.

POSTCreates a repo in the given project with the given name./v1/{parent}/repos
DELETEDeletes a repo./v1/{name}
PATCHUpdates information about a repo./v1/{name}
POSTSynchronize a connected repo./v1/{name}:sync
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
PATCHUpdates the Cloud Source Repositories configuration of the project./v1/{name}/config

What HumDay can read from Google Cloud Source Repositories

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

GETReturns information about a repo./v1/{name}
GETGets the access control policy for a resource./v1/{resource}:getIamPolicy
GETReturns all repos belonging to a project./v1/{name}/repos
GETReturns the Cloud Source Repositories configuration of the project./v1/{name}/config

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