Google Cloud Spanner
Run SQL and DML on Google Cloud Spanner databases (Google OAuth2).
OCNORA ships 14 typed Google Cloud Spanner operations. Each node has a schema-driven form, input and output tables beside its settings, and is pre-flighted by Workflow Health before your first real run.
Before you connect Google Cloud Spanner
- Authentication
- OAuth 2.0
- Credential
- {"client_id", "client_secret", "refresh_token"}
- Connection test
- Available: the stored credential can be checked against the provider when you add it. This is not a record that a test was run or passed.
What you can do with Google Cloud Spanner
Operations, grouped by what they do to your data.
Create and send 4
Update 2
Delete and cancel 2
A sample Google Cloud Spanner workflow
- 1A core triggerStart the run from a chat, form, manual, schedule, webhook, workflow trigger — no Google Cloud Spanner trigger is needed.
- 2Get Databasespanner.get_databaseGets the state of a Cloud Spanner database.
- 3Create Databasespanner.create_databaseCreates a new Spanner database and starts to prepare it for serving.
An outline built from this provider’s node contracts, not a recorded run. Each step’s output fields are available to the next in the field picker.
Every node below has a reference page: what it does, the connection it needs, its config fields with types, constraints and examples, and the shapes it emits.
Operations 14
- Create DatabaseCreates a new Spanner database and starts to prepare it for serving.spanner.create_database
- Create InstanceCreates an instance and begins preparing it to begin serving.spanner.create_instance
- Delete InstanceDeletes an instance.spanner.delete_instance
- Delete SessionEnds a session, releasing server resources associated with it.spanner.delete_session
- Execute DMLRun an INSERT/UPDATE/DELETE on Spanner inside a read-write transaction.spanner.execute_dml
- Execute SQLRun a read-only SQL query on Spanner and return rows as plain dicts.spanner.execute_sql
- Get DatabaseGets the state of a Cloud Spanner database.spanner.get_database
- Get InstanceGets information about a particular instance.spanner.get_instance
- Get SessionGets a session.spanner.get_session
- List DatabasesList databases in a Spanner instance.spanner.list_databases
- List InstancesList Spanner instances in a project.spanner.list_instances
- List SessionsLists all sessions in a given database.spanner.list_sessions
- Update DatabaseUpdates a Cloud Spanner database.spanner.update_database
- Update InstanceUpdates an instance, and begins allocating or releasing resources as requested.spanner.update_instance
Google Cloud Spanner questions
- How does OCNORA authenticate with Google Cloud Spanner?
- With a stored OAuth 2.0 credential, shaped {"client_id", "client_secret", "refresh_token"}. A connection test can check it when you add it.
- What can I automate with Google Cloud Spanner?
- 14 typed operations, each with a reference page listing its config fields and the shapes it emits.
- What if the Google Cloud Spanner operation I need is not listed?
- Where Google Cloud Spanner has an HTTP API, call it from the HTTP node with the same credential, or describe the step to the AI builder, which asks our team for a typed node when one is missing.
- Are there templates that use Google Cloud Spanner?
- Not yet. Start from a blank workflow, or describe the workflow to Build with AI.
- How are Google Cloud Spanner calls controlled?
- Every call and every run step is audited, runs count against the execution budget, and Workflow Health pre-flights the workflow when you save it.
See your first Google Cloud Spanner workflow run.
Book a technical demo. We add the connection, pick a template or describe the workflow to Build with AI, and Workflow Health checks it before it runs.