Can HumDay connect to Google Cloud Key Management (KMS)?

Yes. HumDay reads Google Cloud Key Management (KMS)'s own published API description and derives the operations from it, so there is no hand-built connector to wait for. 29 operations are documented.

Do I need to write code to automate Google Cloud Key Management (KMS)?

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 Key Management (KMS) account.

What can HumDay do in Google Cloud Key Management (KMS)?

19 of the 29 documented operations change something in Google Cloud Key Management (KMS), and 10 read from it. HumDay only ever uses the specific operations your approved contract needs.

Is my Google Cloud Key Management (KMS) 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 Key Management (KMS) is held behind that approval.

Automate Google Cloud Key Management (KMS)

HumDay reads Google Cloud Key Management (KMS)’s own published API description and derives 29 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 Key Management (KMS) is

Manages keys and performs cryptographic operations in a central cloud service, for direct use by other cloud resources and applications.

API host: cloudkms.googleapis.com

What HumDay can do in Google Cloud Key Management (KMS)

19 documented operations change something in Google Cloud Key Management (KMS).

POSTCreate a new KeyRing in a given Project and Location./v1/{parent}/keyRings
POSTCreate a new CryptoKey within a KeyRing./v1/{parent}/cryptoKeys
POSTCreate a new ImportJob within a KeyRing./v1/{parent}/importJobs
POSTCreates a new EkmConnection in a given Project and Location./v1/{parent}/ekmConnections
POSTCreate a new CryptoKeyVersion in a CryptoKey./v1/{parent}/cryptoKeyVersions
POSTSchedule a CryptoKeyVersion for destruction./v1/{name}:destroy
PATCHUpdate a CryptoKeyVersion's metadata./v1/{name}
POSTDecrypts data that was protected by Encrypt./v1/{name}:decrypt
POSTEncrypts data, so that it can only be recovered by a call to Decrypt./v1/{name}:encrypt
POSTSigns data using a CryptoKeyVersion with CryptoKey.purpose MAC, producing a tag that can be verified by another source with the same key./v1/{name}:macSign
POSTRestore a CryptoKeyVersion in the DESTROYSCHEDULED state./v1/{name}:restore
POSTVerifies MAC tag using a CryptoKeyVersion with CryptoKey.purpose MAC, and returns a response that indicates whether or not the verification was successful./v1/{name}:macVerify
POSTSigns data using a CryptoKeyVersion with CryptoKey.purpose ASYMMETRICSIGN, producing a signature that can be verified with the public key retrieved from GetPublicKey./v1/{name}:asymmetricSign
POSTSets the access control policy on the specified resource./v1/{resource}:setIamPolicy
POSTDecrypts data that was encrypted with a public key retrieved from GetPublicKey corresponding to a CryptoKeyVersion with CryptoKey.purpose ASYMMETRICDECRYPT./v1/{name}:asymmetricDecrypt
POSTUpdate the version of a CryptoKey that will be used in Encrypt./v1/{name}:updatePrimaryVersion
POSTReturns permissions that a caller has on the specified resource./v1/{resource}:testIamPermissions
POSTGenerate random bytes using the Cloud KMS randomness source in the provided location./v1/{location}:generateRandomBytes
POSTImport wrapped key material into a CryptoKeyVersion./v1/{parent}/cryptoKeyVersions:import

What HumDay can read from Google Cloud Key Management (KMS)

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

GETReturns metadata for a given ImportJob./v1/{name}
GETGets the access control policy for a resource./v1/{resource}:getIamPolicy
GETVerifies that Cloud KMS can successfully connect to the external key manager specified by an EkmConnection./v1/{name}:verifyConnectivity
GETLists information about the supported locations for this service./v1/{name}/locations
GETReturns the public key for the given CryptoKeyVersion./v1/{name}/publicKey
GETLists KeyRings./v1/{parent}/keyRings
GETLists CryptoKeys./v1/{parent}/cryptoKeys
GETLists ImportJobs./v1/{parent}/importJobs
GETLists EkmConnections./v1/{parent}/ekmConnections
GETLists CryptoKeyVersions./v1/{parent}/cryptoKeyVersions

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