Execute DML
spanner.execute_dml
ActionGoogle Cloudconnection required
Calls Spanner REST sessions:beginTransaction → :executeSql → :commit.
Run an INSERT/UPDATE/DELETE on Spanner inside a read-write transaction.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- OAuth 2.0
- Providers
- Google Cloud Spanner
- Secret shape
- {"client_id", "client_secret", "refresh_token"}
- Config it needs
- project_id, instance, database
- Resolved by
- config.connection_id, else node.connection_id
Configuration
5 fields, 1 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
project_id GCP project id (overrides connection). | string | No | — | — | — |
instance Spanner instance id (overrides connection). | string | No | — | — | — |
database Database id (overrides connection). | string | No | — | — | — |
sql DML statement. Use @name for parameters. | string | Yes | — | — | — |
params Statement parameters as JSON object. | object | No | — | — | — |
Output
One shape.
result
| Field | Type | Example |
|---|---|---|
row_count | number | — |
commit_timestamp | string | — |
{
"commit_timestamp": "",
"row_count": 0
}Related Google Cloud Spanner nodes
See Execute DML run in a workflow.
In a technical demo we add the Google Cloud Spanner connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.