The Google Sheets Node

What it actually does

The Google Sheets node lets a workflow read from, and write to, a Google Sheet directly — no manual copy-pasting, no exporting CSVs. It’s one of the most common “output” nodes in n8n precisely because a spreadsheet is something everyone already knows how to open and read, making it a natural landing place for data an automation has gathered, cleaned, or generated.

The core operations are straightforward: Append adds a new row, Update changes an existing row (matched by a column you choose, like an ID), Append or Update does whichever is appropriate automatically, and there are corresponding read operations for pulling rows back out. You pick the specific spreadsheet and sheet/tab from a dropdown once connected, and map your workflow’s data onto the sheet’s columns — either automatically by matching column names, or manually field by field.

This node needs a Google credential connected before it’ll do anything — if you haven’t set one up yet, there’s a full walkthrough for that here. It’s a one-time setup; once connected, Gmail and other Google nodes can reuse the same credential.

A worked example

A form submission comes in via Webhook, gets tidied up with Edit Fields, and lands in a Google Sheets node set to Append — each submission becomes a new row, arriving in the sheet within a second or two, building a live log with zero manual data entry.

A read-then-update pattern: a Schedule Trigger runs daily, a Google Sheets node reads all rows where a “status” column is blank, an HTTP Request node processes each one against an external service, and a second Google Sheets node (Update mode, matched on row ID) writes the result back into that same row — turning a spreadsheet into a genuine, if lightweight, task queue.

The mistake almost everyone makes first

Forgetting to share the spreadsheet with the Google account the credential is connected to, if they’re different accounts (e.g. building with a personal Google account but the sheet lives under a work one). The node’s dropdown simply won’t show a sheet it doesn’t have access to — which looks like a bug at first, but is almost always a sharing/permissions issue rather than anything wrong with the node’s configuration.