Update Many Ranges
google_sheets.batch_update
ActionFiles & storageconnection required
Calls Sheets values.batchUpdate with the connection's OAuth2 credential.
Overwrite several ranges across tabs in one request.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- OAuth 2.0
- Providers
- Google Sheets
- Secret shape
- {"client_id", "client_secret", "refresh_token"}
- Config it needs
- token_uri
- Resolved by
- config.connection_id, else node.connection_id
Configuration
3 fields, 2 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 |
|---|---|---|---|---|---|
spreadsheet_id The id from the sheet URL. | string | Yes | — | — | — |
clear_first Blank each range before writing — what a sync needs. Off by default; a plain write only sets the cells it is given and leaves the rest of the range alone, so rows from a longer previous run survive. | boolean | No | — | — | — |
data Entries of {"range": "Jan!A2", "values": [[...]]}. Each range's tab must already exist — see google_sheets.add_sheets. | array | Yes | — | array of object | — |
Output
One shape.
result
| Field | Type | Example |
|---|---|---|
updated_ranges The A1 range each entry actually wrote. | array | — |
updated_rows | number | — |
updated_cells | number | — |
updated_sheets | number | — |
{
"updated_cells": 0,
"updated_ranges": [],
"updated_rows": 0,
"updated_sheets": 0
}Notes
- Writes exactly where told, like update — it does not append.
- Without clear_first a shrinking dataset leaves the old surplus rows behind.
- An entry whose tab does not exist fails the whole call.
- The refresh token must have the spreadsheets scope.
Related Google Sheets nodes
Templates that use Google Sheets
Solutions with Google Sheets
See Update Many Ranges run in a workflow.
In a technical demo we add the Google Sheets connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.