Can HumDay connect to Google Cloud Spanner?

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

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

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

What can HumDay do in Google Cloud Spanner?

26 of the 39 documented operations change something in Google Cloud Spanner, and 13 read from it. HumDay only ever uses the specific operations your approved contract needs.

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

Automate Google Cloud Spanner

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

Cloud Spanner is a managed, mission-critical, globally consistent and scalable relational database service.

API host: spanner.googleapis.com

What HumDay can do in Google Cloud Spanner

26 documented operations change something in Google Cloud Spanner.

POSTCreates a set of partition tokens that can be used to execute a query operation in parallel./v1/{session}:partitionQuery
POSTCreates a new Cloud Spanner database and starts to prepare it for serving./v1/{parent}/databases
POSTCreates a new session./v1/{database}/sessions
POSTCreate a new database by restoring from a completed backup./v1/{parent}/databases:restore
POSTCreates multiple new sessions./v1/{database}/sessions:batchCreate
POSTReads rows from the database using key lookups and scans, as a simple key/value style alternative to ExecuteSql./v1/{session}:read
POSTExecutes an SQL statement, returning all results in a single reply./v1/{session}:executeSql
POSTCreates a set of partition tokens that can be used to execute a read operation in parallel./v1/{session}:partitionRead
POSTBegins a new transaction./v1/{session}:beginTransaction
POSTStarts creating a new Cloud Spanner Backup./v1/{parent}/backups
POSTCreates an instance and begins preparing it to begin serving./v1/{parent}/instances
POSTCreates an instance config and begins preparing it to be used./v1/{parent}/instanceConfigs
DELETEDeletes a long-running operation./v1/{name}
PATCHUpdates a Cloud Spanner database./v1/{name}
DELETEDrops (aka deletes) a Cloud Spanner database./v1/{database}
POSTStarts asynchronous cancellation on a long-running operation./v1/{name}:cancel
POSTCommits a transaction./v1/{session}:commit
POSTRolls back a transaction, releasing any locks it holds./v1/{session}:rollback
POSTGets the access control policy for a database or backup resource./v1/{resource}:getIamPolicy
POSTSets the access control policy on a database or backup resource./v1/{resource}:setIamPolicy
POSTLike Read, except returns the result set as a stream./v1/{session}:streamingRead
POSTExecutes a batch of SQL DML statements./v1/{session}:executeBatchDml
POSTReturns permissions that the caller has on the specified database or backup resource./v1/{resource}:testIamPermissions
POSTLike ExecuteSql, except returns the result set as a stream./v1/{session}:executeStreamingSql
PATCHUpdates the schema of a Cloud Spanner database by creating/altering/dropping tables, columns, indexes, etc./v1/{database}/ddl
POSTStarts copying a Cloud Spanner Backup./v1/{parent}/backups:copy

What HumDay can read from Google Cloud Spanner

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

GETReturns the schema of a Cloud Spanner database as a list of formatted DDL statements./v1/{database}/ddl
GETLists the user-managed instance config long-running operations in the given project./v1/{parent}/instanceConfigOperations
GETLists operations that match the specified filter in the request./v1/{name}
GETReturn available scans given a Database-specific resource name./v1/{parent}
GETRequest a specific scan with Database-specific data for Cloud Key Visualizer./v1/{name}/scans
GETLists completed and pending backups./v1/{parent}/backups
GETLists Cloud Spanner databases./v1/{parent}/databases
GETLists all instances in the given project./v1/{parent}/instances
GETLists all sessions in a given database./v1/{database}/sessions
GETLists Cloud Spanner database roles./v1/{parent}/databaseRoles
GETLists the supported instance configurations for a given project./v1/{parent}/instanceConfigs
GETLists the backup long-running operations in the given instance./v1/{parent}/backupOperations
GETLists database longrunning-operations./v1/{parent}/databaseOperations

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