Push-sync design for Google Sheets and n8n avoids full re-reads on every run
Cron workflows that read an entire Google Sheet each run incur heavy costs, since the Sheets node downloads everything before narrowing results, which becomes slow at around 50,000 rows. The article notes the Visualization query endpoint can read a single column cheaply but is only suited to queries, not synchronization. The recommended alternative inverts the flow: the sheet pushes row edits to n8n via an installable Apps Script trigger, and n8n maintains a projection of the data. Row numbers are used only for diagnostics because they shift when rows are sorted or deleted, while identity is keyed on an ID column. Invalid payloads are logged and rejected with a 422 response, since the script caller fails silently by default.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.
Discussion (0)
Log in to join the discussion and vote.
Log in