Can HumDay connect to Google Replica Pool?

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

Do I need to write code to automate Google Replica Pool?

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 Replica Pool account.

What can HumDay do in Google Replica Pool?

6 of the 10 documented operations change something in Google Replica Pool, and 4 read from it. HumDay only ever uses the specific operations your approved contract needs.

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

Automate Google Replica Pool

HumDay reads Google Replica Pool’s own published API description and derives 10 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 Replica Pool is

The Replica Pool API allows users to declaratively provision and manage groups of Google Compute Engine instances based on a common template.

API host: www.googleapis.com

What HumDay can do in Google Replica Pool

6 documented operations change something in Google Replica Pool.

POSTInserts a new replica pool./{projectName}/zones/{zone}/pools
POSTDeletes a replica pool./{projectName}/zones/{zone}/pools/{poolName}
POSTResize a pool. This is an asynchronous operation, and multiple overlapping resize requests can be made. Replica Pools will use the information from the last resize request./{projectName}/zones/{zone}/pools/{poolName}/resize
POSTUpdate the template used by the pool./{projectName}/zones/{zone}/pools/{poolName}/updateTemplate
POSTDeletes a replica from the pool./{projectName}/zones/{zone}/pools/{poolName}/replicas/{replicaName}
POSTRestarts a replica in a pool./{projectName}/zones/{zone}/pools/{poolName}/replicas/{replicaName}/restart

What HumDay can read from Google Replica Pool

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

GETList all replica pools./{projectName}/zones/{zone}/pools
GETGets information about a single replica pool./{projectName}/zones/{zone}/pools/{poolName}
GETLists all replicas in a pool./{projectName}/zones/{zone}/pools/{poolName}/replicas
GETGets information about a specific replica./{projectName}/zones/{zone}/pools/{poolName}/replicas/{replicaName}

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