Can HumDay connect to Google Cloud Filestore?

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

Do I need to write code to automate Google Cloud Filestore?

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 Filestore account.

What can HumDay do in Google Cloud Filestore?

8 of the 14 documented operations change something in Google Cloud Filestore, and 6 read from it. HumDay only ever uses the specific operations your approved contract needs.

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

Automate Google Cloud Filestore

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

The Cloud Filestore API is used for creating and managing cloud file servers.

API host: file.googleapis.com

What HumDay can do in Google Cloud Filestore

8 documented operations change something in Google Cloud Filestore.

POSTRestores an existing instance's file share from a backup./v1/{name}:restore
POSTCreates an instance. When creating from a backup, the capacity of the new instance needs to be equal to or larger than the capacity of the backup (and also equal to or larger than…/v1/{parent}/instances
POSTRevert an existing instance's file system to a specified snapshot./v1/{name}:revert
POSTCreates a backup./v1/{parent}/backups
POSTCreates a snapshot./v1/{parent}/snapshots
DELETEDeletes a long-running operation./v1/{name}
PATCHUpdates the settings of a specific snapshot./v1/{name}
POSTStarts asynchronous cancellation on a long-running operation./v1/{name}:cancel

What HumDay can read from Google Cloud Filestore

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

GETGets the latest state of a long-running operation./v1/{name}
GETLists information about the supported locations for this service./v1/{name}/locations
GETLists all backups in a project for either a specified location or for all locations./v1/{parent}/backups
GETLists operations that match the specified filter in the request./v1/{name}/operations
GETLists all instances in a project for either a specified location or for all locations./v1/{parent}/instances
GETLists all snapshots in a project for either a specified location or for all locations./v1/{parent}/snapshots

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