DocumentationWorkflowsApps and services

Google Sheets node

Read tables from Google Sheets, append new rows or update individual cell ranges. Perfect for reports, logs or as a data source for downstream AI steps. Learn how to configure it, map inputs and outputs, run a test and resolve common errors.

9 min readUpdated

What this node does

Read tables from Google Sheets, append new rows or update individual cell ranges. Perfect for reports, logs or as a data source for downstream AI steps.

Use Google Sheets as a clearly defined step in an anymize workflow.

  • Processes one input.
  • Provides one output for following steps.
  • Runs as a regular step in the flow.

Set up the node

  1. 01Open a workflow and add Google Sheets from the node catalog.
  2. 02Select your google_byo connection. You can create it directly in the workflow if needed.
  3. 03Complete the required fields and map values from previous steps.
  4. 04Run the node with a small test record and inspect its output.
  5. 05Connect the successful output and activate the workflow after an end-to-end test.

Operations and modes

Choose the required function in Action. The panel then shows the relevant settings.

  • Append row
  • Read range
  • Update range
  • Append rows by column mapping

Settings

FieldMeaningArea
ActionChoices: Append row, Read range, Update range, Append rows by column mappingStandard
Spreadsheet (ID from the URL)Open your spreadsheet in Google Sheets and copy the code from the address: docs.google.com/spreadsheets/d/HERE/editStandard
RangeWhich cell range? Format like in Sheets: Sheet1!A:Z (whole columns) or Sheet1!A2:D10. Leave empty for the first column.Standard
ValuesOne cell per line or value. You do not need to type JSON.Standard
Import formatConfigure this value in the node panel.Standard
Google accountChoose the connected Google OAuth profile for this spreadsheet.Protected
SheetKeep the sheet from the template or enter its ID. In the options, you can switch to selection by name.Standard
Map columnsMap each field to a column or match field names automatically. All incoming records are written as one batch.Standard
Select spreadsheet byChoices: ID, Saved selection, LinkStandard
Select sheet byChoices: ID, Saved selection, Name, LinkStandard
Header rowConfigure this value in the node panel.Standard
Write valuesSheets can interpret numbers, dates and formulas. Exact values keep the supplied data unchanged.Standard
Write new headersChoices: Keep exact values, As entered in SheetsStandard
Append directlyReduces requests for sheets without gaps between rows or columns. Otherwise leave this off to write below the last populated row.Standard
Extra fieldsUsed with automatic mapping when input fields have no matching column.Standard
Run once per itemOff (default): the node runs once for the whole input. On: if it receives several items (e.g. from Split Out), it runs once PER item, and {{ $json }} is that one item each time. This is how you work through a file list entry by entry.Standard
If one item fails"Skip" writes an `error` field for the failed item and keeps processing the rest, instead of losing the whole run to a single unreadable file.Standard
Pause between items (milliseconds)Wait before every run except the first. 1000 = 1 second per item. Useful when the other side would otherwise throttle you. Maximum 300000 (5 minutes).Standard

Inputs and outputs

InputMeaningType
StandardReceives the complete result from the previous step.JSON
OutputMeaningType
StandardMakes the result available to the next step as JSON.JSON

This node can process lists item by item. Error handling and the delay between items are available in advanced settings.

Example and test run

Write a lead into a sheet: begin with a small, recognizable record. Inspect the output and only map fields that are present there.

Test-run example

{
  "range": "Leads!A:D",
  "values": [
    "Alice",
    "alice@example.com",
    "2026-04-19",
    "neu"
  ]
}

Access and security

This node uses a connected google_byo account. Review the requested permissions and grant only the required access.

Store keys and credentials in the protected connection manager. Never paste them into normal workflow fields, test data or descriptions.

Troubleshooting

  • No output: inspect the latest run and confirm that the previous node returned the expected fields.
  • Empty variable: open the previous step output and use a field name from the real test data.
  • Connection rejected: reconnect the service and grant the permissions required by this step.
  • List processed once: enable per-item execution in advanced settings.