Can HumDay connect to Google Secret Manager?

Yes. HumDay reads Google Secret Manager'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 Secret Manager?

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 Secret Manager account.

What can HumDay do in Google Secret Manager?

9 of the 15 documented operations change something in Google Secret Manager, and 6 read from it. HumDay only ever uses the specific operations your approved contract needs.

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

Automate Google Secret Manager

HumDay reads Google Secret Manager’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 Secret Manager is

Stores sensitive data such as API keys, passwords, and certificates. Provides convenience while improving security.

API host: secretmanager.googleapis.com

What HumDay can do in Google Secret Manager

9 documented operations change something in Google Secret Manager.

POSTCreates a new SecretVersion containing secret data and attaches it to an existing Secret./v1beta1/{parent}:addVersion
POSTCreates a new Secret containing no SecretVersions./v1beta1/{parent}/secrets
DELETEDeletes a Secret./v1beta1/{name}
PATCHUpdates metadata of an existing Secret./v1beta1/{name}
POSTEnables a SecretVersion./v1beta1/{name}:enable
POSTDestroys a SecretVersion./v1beta1/{name}:destroy
POSTDisables a SecretVersion./v1beta1/{name}:disable
POSTSets the access control policy on the specified secret./v1beta1/{resource}:setIamPolicy
POSTReturns permissions that a caller has for the specified secret./v1beta1/{resource}:testIamPermissions

What HumDay can read from Google Secret Manager

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

GETGets metadata for a SecretVersion./v1beta1/{name}
GETAccesses a SecretVersion./v1beta1/{name}:access
GETGets the access control policy for a secret./v1beta1/{resource}:getIamPolicy
GETLists information about the supported locations for this service./v1beta1/{name}/locations
GETLists Secrets./v1beta1/{parent}/secrets
GETLists SecretVersions. This call does not return secret data./v1beta1/{parent}/versions

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