Can HumDay connect to Google Certificate Manager?

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

Do I need to write code to automate Google Certificate 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 Certificate Manager account.

What can HumDay do in Google Certificate Manager?

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

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

Automate Google Certificate Manager

HumDay reads Google Certificate Manager’s own published API description and derives 18 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 Certificate Manager

9 documented operations change something in Google Certificate Manager.

POSTCreates a new Certificate in a given project and location./v1/{parent}/certificates
POSTCreates a new TrustConfig in a given project and location./v1/{parent}/trustConfigs
POSTCreates a new CertificateMap in a given project and location./v1/{parent}/certificateMaps
POSTCreates a new DnsAuthorization in a given project and location./v1/{parent}/dnsAuthorizations
POSTCreates a new CertificateMapEntry in a given project and location./v1/{parent}/certificateMapEntries
POSTCreates a new CertificateIssuanceConfig in a given project and location./v1/{parent}/certificateIssuanceConfigs
DELETEDeletes a single TrustConfig./v1/{name}
PATCHUpdates a TrustConfig./v1/{name}
POSTStarts asynchronous cancellation on a long-running operation./v1/{name}:cancel

What HumDay can read from Google Certificate Manager

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

GETGets details of a single TrustConfig./v1/{name}
GETLists information about the supported locations for this service./v1/{name}/locations
GETLists operations that match the specified filter in the request./v1/{name}/operations
GETLists Certificates in a given project and location./v1/{parent}/certificates
GETLists TrustConfigs in a given project and location./v1/{parent}/trustConfigs
GETLists CertificateMaps in a given project and location./v1/{parent}/certificateMaps
GETLists DnsAuthorizations in a given project and location./v1/{parent}/dnsAuthorizations
GETLists CertificateMapEntries in a given project and location./v1/{parent}/certificateMapEntries
GETLists CertificateIssuanceConfigs in a given project and location./v1/{parent}/certificateIssuanceConfigs

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